A method, apparatus, and equipment for generating a multi-source evidence chain for trademark ownership and use proof based on an account model blockchain.

By using a blockchain-based method for generating multi-source evidence chains for trademark ownership and use proofs, and leveraging Merkle Tree and smart contract technologies, this approach addresses the high costs and low efficiency issues caused by the large number of pieces of evidence in trademark ownership and use proof scenarios, achieving efficient and reliable evidence storage and verification.

CN123070971APending Publication Date: 2026-11-10SEEDLING PROMOTION CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611271728.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-20
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In existing technologies, the large number, variety, and sources of evidence in trademark ownership and use proof scenarios lead to high on-chain transaction costs, on-chain data redundancy, and low efficiency in batch verification.

Method used

A multi-source evidence chain generation method for trademark ownership and use proof based on an account model blockchain is adopted. Through evidence type identification, metadata extraction and standardization processing, standardized trademark evidence records are generated. The evidence record hash is constructed using Merkle Tree, and the batch identifier and Merkle Root are put on the chain by calling a smart contract to generate a trademark evidence package. The verification end completes the verification by comparing and recalculating the Merkle Root.

Benefits of technology

It enables batch, efficient, and reliable storage and verification of multi-source trademark evidence, reduces on-chain transaction costs, improves verification efficiency, and supports offline verification, thereby enhancing the judicial usability and convenience of evidence.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123070971A_ABST
    Figure CN123070971A_ABST
Patent Text Reader

Abstract

This invention provides a method, apparatus, and device for generating a multi-source evidence chain for trademark ownership and use proof based on an account model blockchain. The method includes: acquiring basic trademark information and evidence data; performing type identification, metadata extraction, and standardization processing on the evidence data to generate standardized evidence records; calculating the evidence record hash for each record, whereby the hash is generated from multiple elements such as file hash, metadata hash, and trademark identifier; constructing a Merkle Tree using the multi-record hashes as leaf nodes to generate a Merkle Root and Merkle Path; calling a smart contract to submit batch identifiers, Merkle Roots, etc., to the blockchain; generating an evidence package based on the evidence records, Merkle Paths, and on-chain information; and verifying the evidence by recalculating and comparing the Merkle Root. This invention achieves batch, efficient, and reliable storage and verification of multi-source trademark evidence.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the application of blockchain technology in the fields of electronic evidence storage and intellectual property protection, specifically to a method, apparatus, and equipment for generating a multi-source evidence chain for trademark ownership and use proof based on an account model blockchain. Background Technology

[0002] In the process of trademark application, registration, use, authorization, transfer, renewal, and rights protection, the rights holder needs to provide a large amount of evidence to prove facts such as trademark ownership, actual use, time of use, and user. These evidence sources are complex, including trademark registration certificates, official website pages, e-commerce platform product pages, advertising records, contracts, invoices, and authorization documents.

[0003] Traditional trademark evidence management methods typically preserve evidence through local files, databases, paper materials, or manual archiving. These methods suffer from problems such as scattered evidence sources, inconsistent evidence formats, difficulty in proving the time of evidence collection, difficulty in verifying the completeness of evidence, and difficulties in third-party verification.

[0004] To address the aforementioned issues, existing technologies have employed blockchain for evidence storage. The typical approach involves calculating the hash of each individual evidence document and writing it to the blockchain to prove that the document existed at a specific point in time and has not been tampered with. However, in trademark ownership and use verification scenarios, the amount, type, source, and frequency of evidence collection are numerous. If each piece of evidence is individually uploaded to the blockchain, it leads to high on-chain transaction costs, data redundancy, and low batch verification efficiency. Therefore, a multi-source evidence chain generation method is needed for trademark ownership and use verification scenarios, which can effectively reduce on-chain costs and improve verification efficiency. Summary of the Invention

[0005] The main purpose of this application is to provide a method, apparatus and equipment for generating a multi-source evidence chain for trademark ownership and use proof based on an account model blockchain, so as to solve the technical problems of high on-chain transaction costs and low batch verification efficiency caused by uploading each piece of evidence to the chain individually in the prior art, and to achieve the technical effect of batch, efficient and reliable storage and verification of multi-source evidence for trademarks.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] According to the first aspect of this application, a method for generating a multi-source evidence chain for trademark ownership and use proof based on an account model blockchain is provided, including:

[0008] Obtain basic trademark information and trademark-related evidence data;

[0009] The trademark-related evidence data is subjected to evidence type identification, metadata extraction and standardization processing to generate multiple standardized trademark evidence records that are bound to the basic trademark information, rights holder information and collection entity information.

[0010] Calculate the evidence record hash corresponding to each of the standardized trademark evidence records. The evidence record hash is generated by the file hash, metadata hash, trademark identifier, rights holder identifier, goods or service category, evidence type, collection time, and collection entity identifier of the corresponding evidence.

[0011] Construct a Merkle Tree using the hashes of multiple evidence records as leaf nodes to generate a Merkle Root and a Merkle Path corresponding to each standardized trademark evidence record;

[0012] Invoke the smart contract deployed on the account model blockchain network, submit the batch identifier, the Merkle Root, the metadata set digest, and the trademark identifier digest to the smart contract, and obtain the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log generated by the smart contract;

[0013] A trademark evidence package is generated based on the standardized trademark evidence record, the corresponding Merkle Path, the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log;

[0014] The verification end recalculates the evidence record hash and Merkle Root based on the trademark evidence package, and completes the trademark evidence verification by comparing the recalculated Merkle Root with the Merkle Root anchored on the chain.

[0015] Furthermore, the process of identifying evidence types, extracting metadata, and standardizing the trademark-related evidence data generates multiple standardized trademark evidence records that are bound to the basic trademark information, rights holder information, and collection entity information, including:

[0016] The evidence types identified in the trademark-related evidence data include at least one of the following: official website webpage evidence, e-commerce platform evidence, advertising evidence, physical packaging evidence, contract evidence, invoice evidence, authorization evidence, trademark registration evidence, trademark transfer evidence, trademark renewal evidence, and trademark infringement evidence.

[0017] Extract the metadata for the corresponding evidence type, and standardize the metadata's time format, source address, and file format;

[0018] The standardized metadata is bound to the trademark basic information, rights holder information, goods or service category information, and collection entity information to generate the standardized trademark evidence record.

[0019] Further, calculating the evidence record hash corresponding to each of the standardized trademark evidence records includes: calculating the evidence record hash according to the following formula:

[0020] RecordHash=Hash(trademark_id,owner_id,class_no,evidence_type,file_hash,metadata_hash,capture_time,collector_id).

[0021] Among them, trademark_id is the trademark identifier, owner_id is the rights holder identifier, class_no is the product or service category number, evidence_type is the evidence type, file_hash is the hash value of the original evidence file, metadata_hash is the hash value of the standardized metadata, capture_time is the evidence collection time, collector_id is the collector identifier, and Hash is the cryptographic hash algorithm.

[0022] Furthermore, constructing a Merkle Tree using multiple evidence record hashes as leaf nodes includes: grouping the standardized trademark evidence records according to at least one of the following rules: trademark number, rights holder, goods or service category, evidence type, collection date, and evidence storage batch; and constructing a Merkle Tree using multiple evidence record hashes within the same group as leaf nodes.

[0023] Furthermore, the invocation of the smart contract deployed on the account model blockchain network, submitting the batch identifier, the Merkle Root, the metadata set digest, and the trademark identifier digest to the smart contract, includes:

[0024] The smart contract verifies whether the batch identifier already exists;

[0025] If the batch identifier does not exist, the smart contract stores the mapping relationship between the batch identifier and the Merkle Root, and triggers the EvidenceBatchAnchored event. The parameters of the event include the batch identifier, Merkle Root, metadata set digest, trademark identifier digest, submitting entity address, and block timestamp.

[0026] If the batch identifier already exists, the smart contract rejects this submission request.

[0027] Furthermore, the trademark evidence package includes: basic trademark information, original evidence files, evidence metadata, standardized trademark evidence records, evidence record hashes, Merkle Path, Merkle Root, batch identifier, chain ID, contract address, transaction hash, block height, smart contract event logs, subject signature information, and verification rules.

[0028] Furthermore, the trademark evidence package is in at least one of the following formats: JSON file, PDF report, compressed file, and multi-file directory structure.

[0029] Furthermore, the verification end recalculates the evidence record hash and Merkle Root based on the trademark evidence package, and completes the trademark evidence verification by comparing the recalculated Merkle Root with the Merkle Root anchored on the chain, including:

[0030] The verification terminal reads the original evidence files and metadata from the trademark evidence package, and recalculates the file hash, metadata hash, and evidence record hash.

[0031] Based on the recalculated evidence record hash and the corresponding Merkle Path, recalculate the Merkle Root;

[0032] Based on the transaction hash, contract address, and chain ID in the trademark evidence package, query the smart contract event log on the blockchain network of the account model to obtain the on-chain anchored Merkle Root;

[0033] The recalculated Merkle Root is compared with the Merkle Root anchored on the chain. If they match, the verification passes; otherwise, the verification fails.

[0034] Furthermore, it also includes: obtaining multiple use evidence records corresponding to the same trademark in chronological order; calculating the current lifecycle record hash based on the hash of the previous lifecycle record, the hash of the current use evidence record, the trademark logo, the event type, the event time, and the signature of the operating entity, to form a linear trademark use lifecycle evidence chain.

[0035] Furthermore, the formula for calculating the hash of the current lifecycle record is as follows:

[0036] LifecycleHash=Hash(PreviousLifecycleHash,CurrentEvidenceRecordHash,trademark_id,event_type,event_time,operator_signature).

[0037] Among them, PreviousLifecycleHash is the hash value of the previous lifecycle record, CurrentEvidenceRecordHash is the hash of the evidence record of the current evidence record, trademark_id is the trademark identifier, event_type is the event type, event_time is the event occurrence time, operator_signature is the digital signature of the operator, and Hash is the cryptographic hash algorithm.

[0038] Furthermore, it also includes: encrypting the original evidence files, evidence metadata, standardized trademark evidence records, and MerklePath and storing them in an off-chain encrypted storage system. The account model blockchain network only stores various hash digest data and does not store the original evidence plaintext.

[0039] Furthermore, the off-chain encrypted storage system adopts at least one of object storage system, private file system, distributed file system, and trusted electronic evidence storage system, and is configured with a role-based evidence access control mechanism.

[0040] Furthermore, the verification operation of the verification terminal includes offline verification, which does not require access to the evidence storage business system and can complete the entire verification process based solely on the trademark evidence package.

[0041] Furthermore, the offline verification steps include:

[0042] Read all contents of the trademark evidence package;

[0043] Recalculate the hash values ​​of the original evidence files, metadata, and evidence records;

[0044] Recalculate the Merkle Root based on the Merkle Path;

[0045] Verify the validity of the signatures of the collecting entity, the submitting entity, and the overall signature of the evidence package in the trademark evidence package;

[0046] The recalculated Merkle Root is compared with the on-chain anchored Merkle Root recorded in the trademark evidence package. If they match and all signatures are valid, the offline verification passes and an offline verification report is generated.

[0047] Furthermore, the account model blockchain network is at least one of the following: the Ethereum mainnet, the Ethereum testnet, the Ethereum Layer 2 network, and an EVM-compatible public blockchain network.

[0048] Furthermore, the cryptographic hash algorithm is at least one of SHA-256, Keccak-256, SHA-3, Blake2, and Blake3.

[0049] According to a second aspect of this application, a device for generating and storing multi-source evidence chains for trademark ownership and use proof based on an account model blockchain is provided, comprising:

[0050] The information acquisition module is used to acquire basic trademark information and trademark-related evidence data.

[0051] The standardization processing module is used to identify the evidence type, extract metadata and standardize the trademark-related evidence data to generate multiple standardized trademark evidence records that are bound to the basic trademark information, rights holder information and collection subject information.

[0052] The hash calculation module is used to calculate the evidence record hash corresponding to each of the standardized trademark evidence records. The evidence record hash is generated by the file hash, metadata hash, trademark identifier, rights holder identifier, goods or service category, evidence type, collection time, and collection entity identifier of the corresponding evidence.

[0053] The Merkle Tree construction module is used to construct a Merkle Tree by using the hashes of multiple evidence records as leaf nodes, and to generate a Merkle Root and a Merkle Path corresponding to each standardized trademark evidence record.

[0054] The on-chain anchoring module is used to call the smart contract deployed on the account model blockchain network, submit the batch identifier, the Merkle Root, the metadata set digest, and the trademark identifier digest to the smart contract, and obtain the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log generated by the smart contract;

[0055] The evidence package generation module is used to generate a trademark evidence package based on the standardized trademark evidence record, the corresponding Merkle Path, the on-chain transaction hash, the block height, the contract address, the chain ID, and the smart contract event log;

[0056] The verification module is used to recalculate the evidence record hash and Merkle Root based on the trademark evidence package, and to complete the trademark evidence verification by comparing the recalculated Merkle Root with the Merkle Root anchored on the chain.

[0057] According to a third aspect of this application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method described in the first aspect of this application.

[0058] According to a fourth aspect of this application, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect of this application.

[0059] According to a fifth aspect of this application, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method described in the first aspect of this application.

[0060] In the method, apparatus, and equipment for generating a multi-source evidence chain for trademark ownership and use proof based on an account model blockchain provided in this application, trademark-related evidence data from different sources and formats are first processed through evidence type identification, metadata extraction, and standardization to generate standardized trademark evidence records that bind basic trademark information, rights holder information, and collection entity information. This process unifies scattered and heterogeneous evidence into structured data, laying the foundation for subsequent processing. Then, for each standardized trademark evidence record, key information such as its evidence file hash, metadata hash, trademark identifier, rights holder identifier, goods or service category, evidence type, collection time, and collection entity identifier are used in the calculation to generate a unique and strongly bound evidence record hash. This hash not only proves the integrity of the evidence file but also closely links the evidence to a specific trademark, rights holder, and collection behavior, enhancing the credibility and relevance of the evidence. Subsequently, multiple evidence record hashes are used as leaf nodes to construct a Merkle Tree, generating a root hash (Merkle Root) representing the entire batch and a verification path (Merkle Path) corresponding to each leaf node. This step transforms the process of storing large amounts of evidence into simply submitting a single Merkle Root to the blockchain, significantly reducing the transaction costs associated with uploading each piece of evidence individually. By invoking a smart contract deployed on the account model blockchain network, the batch identifier, Merkle Root, and related summary information are submitted and recorded on the blockchain by the smart contract's event log. Leveraging the blockchain's immutability and timestamping characteristics, this provides public, verifiable, and reliable on-chain proof for the storage of evidence batches. Finally, the original evidence, metadata, Merkle Path, and on-chain anchoring information are integrated to generate a trademark evidence package. The verification end can then verify whether individual pieces of evidence belong to an anchored batch and have not been tampered with by recalculating and comparing the data. This mechanism solves the problem of high on-chain transaction costs caused by uploading each piece of evidence individually in existing technologies. By utilizing Merkle Tree batch anchoring and the reliable storage characteristics of the blockchain, it achieves efficient, low-cost, reliable storage and convenient verification of multi-source trademark evidence.

[0061] Furthermore, by grouping evidence records according to dimensions such as trademarks and rights holders to construct Merkle Trees, batch management and archiving of evidence are achieved, improving verification efficiency. By generating evidence containing a linear lifecycle hash chain, the continuous use of a trademark over a period of time can be proven, meeting the need for proof of continuous trademark use. By encrypting and storing the original evidence off-chain, and only storing the hash digest on-chain, a balance is achieved between evidence privacy protection and public verifiability. By supporting offline verification entirely based on evidence packages, third parties can independently complete evidence verification without relying on a storage system, enhancing the judicial usability and convenience of evidence. Attached Figure Description

[0062] The accompanying drawings are provided to further understand this application, making other features, objectives, and advantages of this application more apparent. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0063] Figure 1 A flowchart illustrating a method for generating a multi-source evidence chain for trademark ownership and use proof based on an account model blockchain, provided for embodiments of this application;

[0064] Figure 2 A schematic diagram illustrating the standardized processing flow of multi-source evidence for trademarks provided in this application embodiment;

[0065] Figure 3 A schematic diagram illustrating the evidence record hash generation process provided in this application embodiment;

[0066] Figure 4 A schematic diagram of the Merkle Tree batch evidence anchoring process provided in the embodiments of this application;

[0067] Figure 5 A schematic diagram illustrating the smart contract anchoring process provided in this application embodiment;

[0068] Figure 6 A schematic diagram illustrating the on-chain transaction monitoring and event parsing process provided in this application embodiment;

[0069] Figure 7 A schematic diagram illustrating the trademark use lifecycle linear evidence chain generation process provided in this application embodiment;

[0070] Figure 8 This is a schematic diagram illustrating the trademark evidence package generation and verification process provided in this application embodiment. Detailed Implementation

[0071] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0072] The proposed solution is applied to scenarios such as trademark ownership verification, proof of genuine trademark use, proof of authorized trademark use, proof of continuous trademark use, and evidence collection for trademark infringement. By standardizing trademark-related evidence data from different sources and in different formats, and using Merkle Tree technology to generate evidence summaries in batches, the data is submitted to an account model blockchain network for anchoring, thereby generating a trademark evidence package that can be subsequently verified.

[0073] To facilitate understanding of the technical solution of this application, several key terms that will appear in the subsequent embodiments are explained here.

[0074] 1. Account-based blockchain network: refers to a blockchain network that adopts an account balance model, supports the deployment and execution of smart contracts, and allows querying of contract event logs through transaction receipts.

[0075] 2. Trademark-related evidence data: refers to various digital or digitizable supporting materials related to trademark business activities, including but not limited to official website pages, e-commerce platform product pages, advertising records, product packaging images, contracts, invoices, authorization documents, and infringement evidence web pages.

[0076] 3. Standardized Trademark Evidence Records: These are structured data records generated after identifying the evidence type, extracting metadata, and standardizing trademark-related evidence data from different sources and of different types, and then binding them with basic trademark information, rights holder information, and data collection entity information.

[0077] 4. Evidence Record Hash: This refers to the unique digest value obtained by performing hash calculations on multiple core fields in a standardized trademark evidence record, such as trademark identifier, rights holder identifier, goods or service category, evidence type, file hash, metadata hash, collection time, and collection entity identifier.

[0078] 5. Merkle Root: This refers to the unique root hash value obtained by using the hashes of multiple evidence records as the bottom leaf nodes and calculating upwards layer by layer through pairwise hashes.

[0079] 6. On-chain anchoring information: refers to the on-chain record information generated by the blockchain after submitting evidence batch summary information to a smart contract on the account model blockchain network. This information is publicly queryable and verifiable, including but not limited to chain transaction hashes, block heights, contract addresses, chain IDs, and event logs.

[0080] 7. Trademark Evidence Package: This refers to a data set that packages original evidence documents, standardized trademark evidence records, Merkle Path, on-chain anchoring information, digital signatures, and other data into a specific structure for subsequent evidence verification and judicial submission.

[0081] Figure 1 This is a flowchart illustrating a method for generating a multi-source evidence chain for trademark ownership and use proof based on an account model blockchain, as provided in an embodiment of this application. Figure 1 As shown, this application provides a method for generating a multi-source evidence chain for trademark ownership and use proof based on an account model blockchain. The method includes:

[0082] S101, Obtain basic trademark information and trademark-related evidence data;

[0083] S102, perform evidence type identification, metadata extraction and standardization processing on the trademark-related evidence data to generate multiple standardized trademark evidence records that are bound to the basic information of the trademark, the information of the right holder and the information of the collecting entity;

[0084] S103, calculate the evidence record hash corresponding to each standardized trademark evidence record. The evidence record hash is generated by the file hash, metadata hash, trademark logo, rights holder logo, goods or service category, evidence type, collection time, and collection entity logo of the corresponding evidence.

[0085] S104, construct a Merkle Tree using the hashes of multiple evidence records as leaf nodes, and generate a Merkle Root and the corresponding Merkle Path for each standardized trademark evidence record;

[0086] S105, invoke the smart contract deployed on the account model blockchain network, submit the batch identifier, the MerkleRoot, the metadata set summary, and the trademark identifier summary to the smart contract, and obtain the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log generated by the smart contract;

[0087] S106. Generate a trademark evidence package based on the standardized trademark evidence record, the corresponding Merkle Path, the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log;

[0088] S107, the verification end recalculates the evidence record hash and Merkle Root based on the trademark evidence package, and completes the trademark evidence verification by comparing the recalculated Merkle Root with the Merkle Root anchored on the chain.

[0089] In this embodiment, the above steps work collaboratively. In step S101, basic trademark information and multi-source trademark-related evidence data are first acquired as foundational data. Then, in step S102, these multi-source heterogeneous evidence data undergo standardization processing, including evidence type identification and metadata extraction, and are strongly bound to the main information such as registered trademarks, rights holders, and collectors, successfully generating standardized trademark evidence records with unified structure and comparability. In step S103, the file hash representing the integrity of the evidence file, the metadata hash representing the consistency of the evidence description information, and core fields such as specific trademark identifiers, rights holders, categories, and collection times are jointly used in hash calculation to generate a high-strength evidence record hash tightly coupled with the business entity. Subsequently, in step S104, a large number of such evidence record hashes are used as leaf nodes of a Merkle Tree, and the hashes are calculated layer by layer upwards by merging hashes in pairs, finally obtaining a Merkle Root representing the unique state of all evidence records in this batch. In step S105, by invoking a smart contract deployed on the account model blockchain network, the aforementioned Merkle Root is submitted to the chain, compressing the batch evidence storage operations into a single on-chain transaction, and obtaining immutable timestamp anchoring information such as the transaction hash and block height generated by the chain. Finally, in steps S106 and S107, by packaging offline data with on-chain anchoring information to generate a trademark evidence package, the verification end can recalculate the evidence record hash and Merkle Root based solely on the evidence package, without relying on the original evidence storage system, and compare it with the Merkle Root retrieved on the chain to complete independent and reliable verification.

[0090] Let's take a specific application scenario to prove the actual use of a trademark on an e-commerce platform as an example. A brand owner wants to prove that its trademark "TrademarkA" was actually used on "e-commerce platform X" in June 2026. The system first executes S101 to obtain basic trademark information such as the trademark registration number and the name of the rights holder, and obtains the product page data of the product on "e-commerce platform X" through multi-source evidence collection methods as trademark-related evidence data. Then, S102 is executed. The system automatically identifies this evidence type as "e-commerce platform evidence" and extracts metadata such as product title, store entity, product SKU, and collection time from the page data. The time format and source URL are standardized, and the extracted metadata is bound with the trademark logo of "TrademarkA", the rights holder logo, the product category, and the operator logo that collected the evidence to generate a standardized trademark evidence record. Following S103, the system calculates the file hash of the original document and the metadata hash of the standardized metadata field string. Then, it concatenates the values ​​of the trademark identifier, rights holder identifier, product category, evidence type, file hash, metadata hash, collection time, and collection entity identifier in a preset order, and uses the SHA-256 algorithm to generate a unique evidence record hash. For batch evidence storage, the system accumulates a certain number of such evidence records. Next, in S104, the system constructs a Merkle Tree using the hashes of multiple evidence records, including this e-commerce platform evidence, as leaf nodes. After layer-by-layer hash calculation, it obtains the Merkle Root for this batch and generates a Merkle Path for verifying the ownership of the e-commerce platform evidence. Finally, in S105, the system packages the summary information, including the Merkle Root, into a transaction, calls the evidence storage smart contract deployed on Ethereum, stores it after successful contract verification, and triggers the event log. This operation then obtains a unique on-chain transaction hash and block height. Finally, in step S106, the system packages the standardized trademark evidence record, the corresponding Merkle Path, and on-chain anchoring information such as transaction hash and contract address into a JSON-formatted trademark evidence package. When verification is required, the verification end in step S107 opens this evidence package, recalculates the evidence record hash based on the original files and metadata within the package, recalculates the Merkle Root using the Merkle Path, and finally queries the Ethereum blockchain using the contract address and transaction hash to find the originally anchored Merkle Root. The two are compared, and if they match, it irrefutably proves the authenticity and completeness of the evidence used by the e-commerce platform at the time of its storage.

[0091] In one embodiment, regarding step S102 mentioned above, the trademark-related evidence data undergoes evidence type identification, metadata extraction, and standardization processing to generate multiple standardized trademark evidence records bound to the trademark's basic information, rights holder information, and collection entity information. Specifically, this includes: identifying the evidence type of the trademark-related evidence data, which includes at least one of the following: official website webpage evidence, e-commerce platform evidence, advertising evidence, physical packaging evidence, contract evidence, invoice evidence, authorization evidence, trademark registration evidence, trademark transfer evidence, trademark renewal evidence, and trademark infringement evidence; extracting metadata for the corresponding evidence type and standardizing the metadata's time format, source address, and file format; and binding the standardized metadata with the trademark's basic information, rights holder information, goods or service category information, and collection entity information to generate the standardized trademark evidence record. In this way, this embodiment achieves unified processing of evidence from different sources, with different physical forms and data structures, such as official websites, e-commerce platforms, advertising backends, and financial systems. When the evidence type is identified as "official website webpage evidence," the system will specifically extract the webpage title, URL, HTML source code, page screenshot, and collection time as metadata. When identified as "contract evidence," the contract number, the signing parties, the amount, the product category, and the signing date are extracted as metadata, and the time is standardized to ISO 8601 format. This process of mapping heterogeneous data into a unified field structure solves the problems of traditional trademark evidence data being unable to be correlated, difficult to manage uniformly, and difficult to verify in batches. It provides consistent input data for subsequent calculation of evidence record hashes and construction of Merkle Trees.

[0092] In one embodiment, for step S103 mentioned above, calculating the evidence record hash corresponding to each standardized trademark evidence record specifically includes: calculating the evidence record hash according to the following formula:

[0093] RecordHash=Hash(trademark_id,owner_id,class_no,evidence_type,file_hash,metadata_hash,capture_time,collector_id).

[0094] In this dataset, `trademark_id` represents the trademark identifier, `owner_id` represents the rights holder identifier, `class_no` represents the product or service category number, `evidence_type` represents the evidence type, `file_hash` represents the hash value of the original evidence file, `metadata_hash` represents the hash value of standardized metadata, `capture_time` represents the evidence collection time, `collector_id` represents the collector identifier, and `Hash` represents the cryptographic hash algorithm. It is evident that the evidence record hash generated in this embodiment is strictly different from traditional single-file hashes. It no longer simply digests an isolated file, but rather combines the hash of the file itself, the hash of the metadata describing the external characteristics of the evidence, and the three core elements of the evidence's legal and commercial ownership—which trademark (`trademark_id`), who it belongs to (`owner_id`), and which category it is used in (`class_no`)—along with information about when and by whom it was collected, all as a hash preimage for mixed calculation. The beneficial effect of this calculation method is that it greatly strengthens the binding strength between evidence data and its business context. Any change to the information at any stage—for example, attempting to tamper with evidence for the clothing category (class_no: 25) to the advertising service category (class_no: 35)—will cause a catastrophic change in the hash of the altered record, as the class_no field directly participates in the final record hash calculation. This change will result in the hash of the altered record becoming completely incompatible with the original record hash and Merkle Root anchored on the blockchain. Therefore, it technically eliminates the possibility of tampering with the ownership and collection of evidence.

[0095] In one embodiment, regarding step S104 mentioned above, constructing a Merkle Tree using multiple evidence record hashes as leaf nodes specifically includes: grouping the standardized trademark evidence records according to at least one of the following rules: trademark number, rights holder, goods or service category, evidence type, collection date, and evidence batch; and constructing a Merkle Tree using multiple evidence record hashes within the same group as leaf nodes. This embodiment further defines the batch processing logic for constructing the Merkle Tree. In specific application scenarios, users can group by a single dimension or a combination of multiple dimensions. For example, they can select the combination of "trademark number" and "goods category" to group evidence records. When organizing evidence for Class 35 services of a specific trademark, all contract usage evidence, advertising placement evidence, and official website usage evidence belonging to that trademark and marked as Class 35 will have their corresponding multiple evidence record hashes grouped into the same group. The system uses these multiple evidence record hashes in the same group as leaf nodes to construct a Merkle Tree specifically for Class 35 services of that trademark. The advantage of this grouping approach is that the generated Merkle Root has a clear business meaning; it represents the overall anchoring status of all usage evidence for a specific trademark within a specific service category and over a given time period. This not only facilitates evidence archiving and management according to business logic but also enables third-party verification agencies to clearly identify which business dimension's batch of evidence a particular piece of evidence belongs to, improving the targeting and management efficiency of verification.

[0096] In one embodiment, regarding step S105 mentioned above, a smart contract deployed on the account model blockchain network is invoked to submit the batch identifier, the Merkle Root, the metadata set digest, and the trademark identifier digest to the smart contract. Specifically, this includes: the smart contract verifying whether the batch identifier already exists; if the batch identifier does not exist, the smart contract stores the mapping relationship between the batch identifier and the Merkle Root and triggers the EvidenceBatchAnchored event. The parameters of this event include the batch identifier, the Merkle Root, the metadata set digest, the trademark identifier digest, the submitting entity address, and the block timestamp; if the batch identifier already exists, the smart contract rejects this submission request. This embodiment limits the security and determinism of the on-chain anchoring process. In specific implementation, the smart contract internally maintains a mapping table from the batch identifier to the Merkle Root. When a submission request is received, the contract code first checks whether the value corresponding to the batch identifier in the mapping table is zero (i.e., does not exist). If the Merkle Root does not exist, it means this is a completely new batch of evidence. The contract will permanently store the received Merkle Root in the mapping table and publicly and transparently record all parameters crucial to this evidence storage operation in the blockchain's event log as a smart contract event. This event log, as immutable on-chain data, can be independently queried and verified by anyone in the future. Conversely, if the batch identifier already exists in the mapping table, the smart contract will determine that this is a duplicate submission or replay attack, and immediately suspend execution and roll back the transaction. This verification mechanism ensures that the anchoring of each batch of evidence data on the blockchain is unique and cannot be overwritten, preventing malicious acts of subsequently tampering with and resubmitting the same batch of evidence.

[0097] In one embodiment, the trademark evidence package in step S106 mentioned above includes: basic trademark information, original evidence files, evidence metadata, standardized trademark evidence records, evidence record hashes, MerklePath, Merkle Root, batch identifier, chain ID, contract address, transaction hash, block height, smart contract event log, subject signature information, and verification rules. This embodiment clearly defines the complete data structure of the final product of the evidence storage system. The purpose of this structure is to generate a self-contained, complete data unit that can be used for judicial evidence issuance. The original evidence files are the direct objects of proof; the evidence metadata and standardized trademark evidence records are the structured facts of the proof; the Merkle Path provides the mathematical proof of the logical connection between this single fact and the entire batch of facts; and the Merkle Root, contract address, transaction hash, block height, and smart contract event log constitute a solid bridge from mathematical truth to legal consensus, namely, an immutable on-chain timestamp and evidence storage record. The subject signature information is used to verify the source and integrity of the evidence package. The verification rules embed the verification logic of the evidence package, guiding the verifier on how to operate. This structural design, which integrates physical evidence, mathematical proof, on-chain credible evidence, and operational guidelines, allows the recipient to initiate and complete the verification process of the authenticity and completeness of the evidence solely based on the trademark evidence package itself, without relying on any external system or complex context. This greatly facilitates independent review in judicial, administrative, and arbitration scenarios.

[0098] In one embodiment, regarding step S107 mentioned above, the verification end recalculates the evidence record hash and Merkle Root based on the trademark evidence package. The trademark evidence verification is completed by comparing the recalculated Merkle Root with the on-chain anchored Merkle Root. Specifically, this includes: the verification end reading the original evidence file and metadata in the trademark evidence package, recalculating the file hash, metadata hash, and evidence record hash; recalculating the Merkle Root based on the recalculated evidence record hash and the corresponding Merkle Path; querying the smart contract event log on the account model blockchain network according to the transaction hash, contract address, and chain ID in the trademark evidence package to obtain the on-chain anchored Merkle Root; comparing the recalculated Merkle Root with the on-chain anchored Merkle Root; if they match, the verification passes; otherwise, the verification fails. This embodiment describes the specific calculation logic of the verification. The verification process is a deterministic re-calculation process. First, the verification end will recalculate an independent evidence record hash based on the original file and metadata in the package, strictly following the same algorithm and field concatenation order as when the evidence was stored. Subsequently, using the recorded hash and the Merkle Path provided within the packet, pairing hash operations are performed upwards step by step according to the sibling node hashes specified by the Merkle Path, ultimately recalculating a MerkleRoot. Simultaneously, the verification end utilizes the on-chain anchoring information provided within the packet to directly query the corresponding EvidenceBatchAnchored event log based on the transaction hash and contract address via the API provided by the blockchain node or browser, without needing to traverse all blocks, and parses the MerkleRoot recorded on the chain at the time of evidence storage. Finally, this offline recalculated Merkle Root is compared with the Merkle Root retrieved on the chain. The consistency between the two establishes an irrefutable logical loop: to recalculate the same Merkle Root, it is necessary to rely on the currently provided tamper-proof original evidence files; and this same Merkle Root already existed on the immutable blockchain at some historical block time. This proves, through mathematical and cryptographic means rather than subjective human guarantees, that the evidence has remained unchanged from the time it was collected and stored until the moment of verification, and that its content and ownership remain consistent with those at the time.

[0099] In one embodiment, based on steps S101 to S107 above, the method further includes: obtaining multiple use evidence records corresponding to the same trademark arranged in chronological order; calculating the current lifecycle record hash based on the hash of the previous lifecycle record, the hash of the current use evidence record, the trademark identifier, the event type, the event time, and the signature of the operating entity, forming a linear trademark use lifecycle evidence chain. This embodiment introduces a linear hash chain mechanism for proving "continuous use of a trademark." In trademark law practice, proving that a trademark is used continuously rather than intermittently within a specific time period is of decisive significance. In specific implementation, the system periodically collects and records various types of use evidence for the same trademark and sorts these records according to the time of event occurrence. This mechanism starts from the first use evidence of the trademark and generates the first lifecycle record hash, the calculation basis of which is the record hash of the first evidence. When the second use evidence is generated, the generated second lifecycle record hash will use the "hash of the previous lifecycle record" and the "hash of the current evidence" as the core input for calculation. And so on, forming a hash chain that is connected end to end and interlocked. Because each subsequent lifecycle record hash contains the hash information of all previous lifecycle records, any attempt to delete, replace, or insert a piece of historical usage evidence from the middle of the chain will disrupt the continuity of that hash chain. Therefore, this linear lifecycle evidence chain structurally guarantees the integrity and immutability of the trademark use timeline, providing strong technical evidence to prove the trademark's continued use over a long period.

[0100] In one embodiment, the lifecycle evidence chain is used for the aforementioned trademark, and the formula for calculating the hash of the current lifecycle record is as follows:

[0101] LifecycleHash=Hash(PreviousLifecycleHash,CurrentEvidenceRecordHash,trademark_id,event_type,event_time,operator_signature).

[0102] In this implementation, PreviousLifecycleHash is the hash value of the previous lifecycle record, CurrentEvidenceRecordHash is the hash of the current usage evidence record, trademark_id is the trademark identifier, event_type is the usage event type, event_time is the event occurrence time, operator_signature is the digital signature of the operating entity, and Hash is the cryptographic hash algorithm. This embodiment details the atomic calculation formula for generating this hash chain. This formula not only achieves a strict link with historical records through PreviousLifecycleHash, but also directly binds each continuous usage record to the trademark itself, the specific usage behavior type, and the occurrence time by simultaneously taking fields such as trademark_id, event_type, and event_time as input. In particular, the introduction of operator_signature adds proof of authorization and responsibility for each lifecycle advancement. This signature is generated by the operating entity using its private key, and the verifier can use the public key to verify that the lifecycle record was indeed generated by this entity and has not been tampered with. Through this nested and multi-bound calculation formula, the resulting linear hash chain not only proves the continuity of time, but also the authenticity and authorization of each step of the operation, forming a strong chain of evidence for the continuous use of a trademark.

[0103] In one embodiment, based on the above embodiments, the method further includes: encrypting the original evidence files, evidence metadata, standardized trademark evidence records, and Merkle Path and storing them in an off-chain encrypted storage system. This account model blockchain network only stores various hash digest data and does not store the original plaintext evidence. This embodiment clarifies the privacy protection strategy for evidence data, namely, storing entity data off-chain and only storing the hash digest of the data on-chain. This hybrid architecture of "off-chain encrypted storage and on-chain digest anchoring" achieves a delicate balance between privacy protection and public verifiability. The plaintext content of the original evidence, due to its involvement of trade secrets or personal privacy, must never be publicly disclosed on the blockchain. By encrypting and storing it on a local off-chain server or a trusted storage system, data confidentiality and access control can be guaranteed. Simultaneously, anchoring the hash value of the original evidence, the hash value of the metadata, and the final Merkle Root on the blockchain utilizes the blockchain's open, transparent, and tamper-proof technical characteristics, providing a credible and independent third-party witness to the integrity and temporal existence of this private data. When verifying evidence, the verifier only needs to obtain the encrypted evidence data and its corresponding digest to complete the verification to the blockchain. The verifier does not need to access the possible plaintext content throughout the process, thus protecting privacy without losing its probative value.

[0104] In one embodiment, the off-chain encrypted storage system described above employs at least one of an object storage system, a private file system, a distributed file system, and a trusted electronic evidence storage system, and is configured with a role-based evidence access control mechanism. This embodiment provides a specific implementation method and access management strategy for the off-chain storage system. In specific implementation, a low-cost object storage service can be selected to store large-scale evidence files, or a highly secure private file system can be used. The role-based access control mechanism ensures that only explicitly authorized patent agents, lawyers, judges, or verifiers can obtain decryption keys or access specific evidence files within a specific time period, further enhancing the security and compliance of evidence data.

[0105] In one embodiment, regarding step S107 mentioned above, the verification operation of the verification terminal includes offline verification. This offline verification does not require access to the evidence storage business system; the entire verification process can be completed solely based on the trademark evidence package. This embodiment emphasizes the independence and convenience of the verification operation. "Offline" refers to the evidence storage business system, not network disconnection. The core concept is that the verification process is completely independent of the evidence storage party's own server, database, or API. The verification terminal only needs to obtain the self-contained trademark evidence package and general, publicly available blockchain network access capabilities (such as public RPC nodes or block explorers) to independently perform the entire verification. This means that even if the evidence storage service provider ceases operation or becomes untrustworthy, the authenticity of the generated evidence package can still be independently verified, greatly enhancing the long-term availability of the evidence and its ability to withstand single points of failure, meeting the requirements of independent and objective review by judicial appraisal institutions.

[0106] In one embodiment, the specific steps for the aforementioned offline verification include: reading the entire contents of the trademark evidence package; recalculating the hash values ​​of the original evidence files, metadata, and evidence records; recalculating the Merkle Root based on the Merkle Path; verifying the validity of the signatures of the collecting entity, the submitting entity, and the overall signature of the evidence package in the trademark evidence package; comparing the recalculated Merkle Root with the on-chain anchored Merkle Root recorded in the trademark evidence package; if they match and all signatures are valid, the offline verification passes, and an offline verification report is generated. This embodiment provides a more rigorous explanation of the complete offline verification process. Its verification not only includes Merkle Root comparison at the data integrity level but also adds a multi-signature verification step at the data source authenticity level. The verification end uses the public key of the collecting entity, the public key of the submitting entity, and the public key of the issuing party of the evidence package attached to the evidence package to decrypt and compare their respective original signature data. The verification process is considered fully passed only when the Merkle Roots match and all relevant digital signatures are verified as valid. This design simultaneously meets the dual judicial evidence requirements of "evidence not being tampered with" and "traceable source and accountability," making the final offline verification report highly credible and usable directly as courtroom materials.

[0107] In one embodiment, the account model blockchain network is at least one of the following: the Ethereum mainnet, the Ethereum testnet, the Ethereum Layer 2 network, and a public blockchain network compatible with the Ethereum Virtual Machine (EVM). The advantages of using this type of network include a mature ecosystem, powerful smart contract functionality, support for event logs, and transparent on-chain data. It also features a large number of nodes and block explorers globally, facilitating independent on-chain data querying and verification by third parties.

[0108] In one embodiment, the cryptographic hash algorithm mentioned in the foregoing embodiments is at least one of SHA-256, Keccak-256, SHA-3, Blake2, and Blake3. These hash algorithms all have strong collision resistance, ensuring the uniqueness and security of the hash value, which is the core of the evidence storage system.

[0109] In one embodiment, the trademark evidence package mentioned in the foregoing embodiments is in at least one of the following formats: JSON file, PDF report, compressed file, and multi-file directory structure. JSON file facilitates automatic parsing and verification by the program; PDF report is suitable for manual reading and judicial archiving; compressed file structure is suitable for the aggregation and transmission of large amounts of data, which can meet the practical needs of different receiving scenarios.

[0110] It should be noted that, in some optional implementations, the account model blockchain network in this application's technical solution can specifically use the Ethereum mainnet to obtain the strongest security, or use Ethereum Layer 2 networks such as Arbitrum or Optimism to further reduce on-chain transaction fees. The preferred development language for smart contracts is Solidity, but EVM-compatible languages ​​such as Vyper can also be used. The off-chain encrypted storage system can be built using a distributed file system based on IPFS or similar methods as the backend. After a user uploads evidence files through a client, the system frontend can call the Web CryptoAPI to encrypt the files using the AES algorithm on the browser side. The encrypted file fragments are stored on IPFS, and the content's CID (Content Identifier) ​​and the metadata required for decryption are stored in the business database. For permissions and signatures, collectors and submitters can use Ethereum wallets such as MetaMask for transaction and message signatures. For the Merkle Tree, a Spase Merkle Tree or a binary Merkle Tree using Keccak-256 as the hash function is supported, and a complete Merkle Path is generated for each leaf node for verification. In actual operation, the on-chain transaction monitoring module continuously polls or establishes a WebSocket connection to subscribe to the "EvidenceBatchAnchored" event of the contract. Once a new event log is received, the module updates the status of the evidence batch in the background and persists information such as transaction hash, block height, and block timestamp to the local relational database, associating it with the original evidence batch data to achieve automated synchronization of on-chain anchoring information.

[0111] It should be noted that in some alternative implementations, if the number of evidence records in a single batch is insufficient to construct an efficient Merkle Tree, the system can directly use the hashes of a small number of evidence records as a set in the calculation of the upper-layer business hash, or set a threshold for the number of evidence records in a batch, and then perform the Merkle Tree construction operation when the threshold is reached. Furthermore, for the lifecycle evidence chain, the PreviousLifecycleHash field of its starting node (i.e., the first piece of evidence used) is filled with zero or a null value by default. For on-chain verification and offline verification processes, they can be automated by developing dedicated verification clients or providing online verification SDKs to lower the barrier to entry for non-technical users.

[0112] This application embodiment also provides a device for generating and storing multi-source evidence chains for trademark ownership and use proof based on an account model blockchain. The device includes: an information acquisition module 10, used to acquire basic trademark information and trademark-related evidence data; a standardization processing module 20, used to identify the evidence type, extract metadata, and standardize the trademark-related evidence data to generate multiple standardized trademark evidence records bound to the basic trademark information, rights holder information, and collection entity information; a hash calculation module 30, used to calculate the evidence record hash corresponding to each standardized trademark evidence record, where the evidence record hash is generated by the file hash, metadata hash, trademark identifier, rights holder identifier, goods or service category, evidence type, collection time, and collection entity identifier of the corresponding evidence; a Merkle Tree construction module 40, used to construct a Merkle Tree using the multiple evidence record hashes as leaf nodes, generating a Merkle Root and a Merkle Path corresponding to each standardized trademark evidence record; and an on-chain anchoring module 50, used to call a smart contract deployed on the account model blockchain network to anchor the batch identifier, the Merkle... The Root, metadata set summary, and trademark identifier summary are submitted to the smart contract to obtain the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log generated by the smart contract. The evidence package generation module 60 generates a trademark evidence package based on the standardized trademark evidence record, the corresponding Merkle Path, the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log. The verification module 70 recalculates the evidence record hash and Merkle Root based on the trademark evidence package and verifies the trademark evidence by comparing the recalculated Merkle Root with the on-chain anchored Merkle Root. The device embodiment of this application is based on the same inventive concept as the above method embodiment, and its technical effects are the same as the method embodiment. For the sake of brevity, it will not be repeated here.

[0113] This application also provides an electronic device, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the methods described in any of the above embodiments. This electronic device can be a server or a terminal device, which, by running the program, automatically performs the entire process of trademark evidence collection, standardization, hash calculation, Merkle Tree construction, smart contract interaction, evidence package generation, and verification.

[0114] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the method described in any of the above embodiments. This storage medium, as a carrier of software, enables the method to be flexibly deployed in different hardware environments.

[0115] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the methods described in any of the above embodiments. This product form allows the software to be distributed and applied as a standalone product.

[0116] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for generating a multi-source evidence chain for trademark ownership and use proof based on an account-model blockchain, characterized in that, include: Obtain basic trademark information and trademark-related evidence data; The trademark-related evidence data is subjected to evidence type identification, metadata extraction and standardization processing to generate multiple standardized trademark evidence records that are bound to the basic trademark information, rights holder information and collection entity information. Calculate the evidence record hash corresponding to each of the standardized trademark evidence records. The evidence record hash is generated by the file hash, metadata hash, trademark identifier, rights holder identifier, goods or service category, evidence type, collection time, and collection entity identifier of the corresponding evidence. Construct a Merkle Tree using the hashes of multiple evidence records as leaf nodes to generate a Merkle Root and a Merkle Path corresponding to each standardized trademark evidence record; Invoke the smart contract deployed on the account model blockchain network, submit the batch identifier, the Merkle Root, the metadata set digest, and the trademark identifier digest to the smart contract, and obtain the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log generated by the smart contract; A trademark evidence package is generated based on the standardized trademark evidence record, the corresponding Merkle Path, the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log; The verification end recalculates the evidence record hash and Merkle Root based on the trademark evidence package, and completes the trademark evidence verification by comparing the recalculated Merkle Root with the Merkle Root anchored on the chain.

2. The method according to claim 1, characterized in that, The process involves identifying the evidence type, extracting metadata, and standardizing the trademark-related evidence data to generate multiple standardized trademark evidence records that are bound to the basic trademark information, rights holder information, and data collection entity information. These records include: The evidence types identified in the trademark-related evidence data include at least one of the following: official website webpage evidence, e-commerce platform evidence, advertising evidence, physical packaging evidence, contract evidence, invoice evidence, authorization evidence, trademark registration evidence, trademark transfer evidence, trademark renewal evidence, and trademark infringement evidence. Extract the metadata for the corresponding evidence type, and standardize the metadata's time format, source address, and file format; The standardized metadata is bound to the trademark basic information, rights holder information, goods or service category information, and collection entity information to generate the standardized trademark evidence record.

3. The method according to claim 2, characterized in that, The step of calculating the evidence record hash corresponding to each of the standardized trademark evidence records includes: The hash of the evidence record is calculated using the following formula: in, For trademarks, For the identification of the rights holder, For the category number of goods or services, As a type of evidence, The hash value of the original evidence file. The hash value of standardized metadata, For the time of evidence collection, For the identification of the data collection subject, It is a cryptographic hash algorithm.

4. The method according to claim 1, characterized in that, The step of constructing a Merkle Tree using the hashes of multiple evidence records as leaf nodes includes: The standardized trademark evidence records are grouped according to at least one of the following rules: trademark number, rights holder, goods or services category, evidence type, collection date, and batch of evidence storage. Construct a Merkle Tree by using the hashes of multiple evidence records within the same group as leaf nodes.

5. The method according to claim 1, characterized in that, The invocation of a smart contract deployed on the account model blockchain network submits the batch identifier, the Merkle Root, the metadata set digest, and the trademark identifier digest to the smart contract, including: The smart contract verifies whether the batch identifier already exists; If the batch identifier does not exist, the smart contract stores the mapping relationship between the batch identifier and the Merkle Root, and triggers the EvidenceBatchAnchored event. The parameters of the event include the batch identifier, Merkle Root, metadata set digest, trademark identifier digest, submitting entity address, and block timestamp. If the batch identifier already exists, the smart contract rejects this submission request.

6. The method according to claim 1, characterized in that, The trademark evidence package includes: basic trademark information, original evidence files, evidence metadata, standardized trademark evidence records, evidence record hashes, Merkle Path, Merkle Root, batch identifier, chain ID, contract address, transaction hash, block height, smart contract event log, subject signature information, and verification rules; And / or, the trademark evidence package may be in the format of at least one of the following: JSON file, PDF report, compressed file, or multi-file directory structure.

7. The method according to claim 1, characterized in that, The verification terminal recalculates the evidence record hash and Merkle Root based on the trademark evidence package, and completes the trademark evidence verification by comparing the recalculated Merkle Root with the Merkle Root anchored on the chain, including: The verification terminal reads the original evidence files and metadata from the trademark evidence package, and recalculates the file hash, metadata hash, and evidence record hash. Based on the recalculated evidence record hash and the corresponding Merkle Path, the Merkle Root is recalculated; the smart contract event log on the blockchain network of the account model is queried according to the transaction hash, contract address, and chain ID in the trademark evidence package to obtain the on-chain anchored Merkle Root; The recalculated Merkle Root is compared with the Merkle Root anchored on the chain. If they match, the verification passes; otherwise, the verification fails.

8. The method according to claim 1, characterized in that, Also includes: Obtain multiple records of use evidence corresponding to the same trademark, arranged in chronological order; Based on the hash of the previous lifecycle record, the hash of the current use evidence record, the trademark logo, the event type, the event time, and the signature of the operating entity, the hash of the current lifecycle record is calculated to form a linear chain of trademark use lifecycle evidence.

9. The method according to claim 8, characterized in that, The formula for calculating the hash of the current lifecycle record is as follows: in, The hash value of the previous lifecycle record. The hash of the evidence record currently in use. For trademarks, To use event types, The time when the event occurred. For the digital signature of the operating entity, It is a cryptographic hash algorithm.

10. The method according to claim 1, characterized in that, Also includes: The original evidence files, evidence metadata, standardized trademark evidence records, and Merkle Path are encrypted and stored in an off-chain encrypted storage system. The account model blockchain network only stores various hash digest data and does not store the original evidence plaintext.

11. The method according to claim 10, characterized in that, The off-chain encrypted storage system adopts at least one of object storage system, private file system, distributed file system, and trusted electronic evidence storage system, and is configured with a role-based evidence access control mechanism.

12. The method according to claim 1, characterized in that, The verification operation of the verification terminal includes offline verification, which does not require access to the evidence storage business system and can complete the entire verification process based solely on the trademark evidence package.

13. The method according to claim 12, characterized in that, The offline verification steps include: reading all the contents of the trademark evidence package; Recalculate the hash values ​​of the original evidence files, metadata, and evidence records; Recalculate the Merkle Root based on the Merkle Path; Verify the validity of the signatures of the collecting entity, the submitting entity, and the overall signature of the evidence package in the trademark evidence package; The recalculated Merkle Root is compared with the on-chain anchored Merkle Root recorded in the trademark evidence package. If they match and all signatures are valid, the offline verification passes and an offline verification report is generated.

14. The method according to claim 3, characterized in that, The account model blockchain network is at least one of the following: Ethereum mainnet, Ethereum testnet, Ethereum Layer 2 network, and EVM-compatible public chain network; And / or, the cryptographic hash algorithm is at least one of SHA-256, Keccak-256, SHA-3, Blake2, and Blake3.

15. A device for generating and storing multi-source evidence chains for trademark ownership and use proof based on an account model blockchain, characterized in that, include: The information acquisition module is used to acquire basic trademark information and trademark-related evidence data. The standardization processing module is used to identify the evidence type, extract metadata and standardize the trademark-related evidence data to generate multiple standardized trademark evidence records that are bound to the basic trademark information, rights holder information and collection subject information. The hash calculation module is used to calculate the evidence record hash corresponding to each of the standardized trademark evidence records. The evidence record hash is generated by the file hash, metadata hash, trademark identifier, rights holder identifier, goods or service category, evidence type, collection time, and collection entity identifier of the corresponding evidence. The Merkle Tree construction module is used to construct a Merkle Tree by using the hashes of multiple evidence records as leaf nodes, and to generate a Merkle Root and a Merkle Path corresponding to each standardized trademark evidence record. The on-chain anchoring module is used to call the smart contract deployed on the account model blockchain network, submit the batch identifier, the Merkle Root, the metadata set digest, and the trademark identifier digest to the smart contract, and obtain the on-chain transaction hash, block height, contract address, chain ID, and smart contract event log generated by the smart contract; The evidence package generation module is used to generate a trademark evidence package based on the standardized trademark evidence record, the corresponding Merkle Path, the on-chain transaction hash, the block height, the contract address, the chain ID, and the smart contract event log; The verification module is used to recalculate the evidence record hash and Merkle Root based on the trademark evidence package, and to complete the trademark evidence verification by comparing the recalculated Merkle Root with the Merkle Root anchored on the chain.

16. An electronic device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method as described in any one of claims 1 to 14.

17. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 14.

18. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 14.