Data processing method and device based on block chain, equipment and medium

By using block Merkel information and Merkel proof sets to verify cross-chain messages in the blockchain, the problems of large data storage occupancy and low verification efficiency in cross-chain services are solved, and efficient cross-chain message verification is achieved.

CN119067658APending Publication Date: 2024-12-03TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 3 Cited by

Patent Information

Application Number
CN202310631214.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-30
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In cross-chain business, blockchain nodes need to maintain a large amount of data, resulting in large data storage usage and low verification efficiency, especially when the amount of data increases.

Method used

By obtaining the chain identifier of cross-chain messages, obtaining the block Merkel information and Merkel proof set of the first blockchain, verifying the validity of the message in the block Merkel tree, reducing data storage requirements and improving verification efficiency .

Benefits of technology

The data storage usage of consensus nodes is reduced, the verification efficiency of cross-chain messages is improved, and cross-chain messages are realized quickly verifying cross-chain messages at the height of blocks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119067658A_ABST
    Figure CN119067658A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a data processing method and device based on a block chain, equipment and a medium, and the method comprises the steps: obtaining a cross-chain message submitted by forwarding service equipment, and obtaining a chain identifier carried by the cross-chain message; the cross-chain message is associated with cross-chain transaction data stored in the first block chain; obtaining block Merkel information corresponding to the first block chain in a second block chain corresponding to the chain identifier, and obtaining a Merkel proof set corresponding to the cross-chain message in a block Merkel tree corresponding to the block Merkel information; the block Merkel tree comprises a plurality of Merkel sub-trees; obtaining a cross-chain verification result corresponding to the cross-chain message according to the Merkel proof set and the block Merkel information; and if the cross-chain verification result indicates that verification succeeds, obtaining a transaction execution result corresponding to the cross-chain message, and storing the transaction execution result to the second block chain. According to the embodiment of the invention, the verification efficiency of the cross-chain message can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a blockchain-based data processing method, device, equipment and medium. Background Art

[0002] Blockchain is a decentralized distributed ledger system with the characteristics of data immutability, decentralization, and openness. The consensus mechanism, as the core of blockchain technology, is the basis for ensuring the normal operation of the blockchain system. The consensus process of the blockchain system can be understood as the process of keeping the distributed ledgers between each blockchain node consistent. With the development and application of blockchain technology, the application of cross-chain business between different blockchains is becoming more and more extensive, such as asset transfer between different blockchains, or asset custody authorization between different blockchains; in the application scenarios of cross-chain business, in order to ensure the security of data in different blockchains, cross-chain business needs to be verified.

[0003] At present, in the verification process of cross-chain services, each blockchain node needs to maintain a large amount of data on another or multiple blockchains (block headers of all blocks on the chain, etc.) and verify the block chain structure. When the amount of chain data increases, the data storage space occupied by the blockchain nodes is too large, and the verification efficiency of cross-chain services will be too low. Summary of the invention

[0004] The embodiments of the present application provide a blockchain-based data processing method, apparatus, device, and medium, which can reduce the data storage usage of consensus nodes in cross-chain interactions and improve the verification efficiency of cross-chain messages.

[0005] On the one hand, an embodiment of the present application provides a data processing method based on blockchain, including:

[0006] Obtaining a cross-chain message submitted by the forwarding service device, and obtaining a chain identifier carried by the cross-chain message; the cross-chain message is associated with the cross-chain transaction data stored in the first blockchain;

[0007] Obtain the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and obtain the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information; the verifiable height H1 of the block Merkle information in the first blockchain is greater than or equal to the block height H2 of the cross-chain message in the first blockchain, and the block Merkle tree includes multiple Merkle subtrees;

[0008] According to the Merkle proof set and block Merkle information, the validity of the cross-chain message is verified to obtain the cross-chain verification result corresponding to the cross-chain message;

[0009] If the cross-chain verification result indicates that the verification is successful, the transaction execution result corresponding to the cross-chain message is obtained, and the transaction execution result is stored in the second blockchain.

[0010] On the one hand, an embodiment of the present application provides a data processing method based on blockchain, including:

[0011] Obtain a cross-chain message initiated by the first blockchain, and obtain the block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain; the cross-chain message carries a chain identifier;

[0012] If it is detected in the second blockchain corresponding to the chain identifier that the verifiable height H1 corresponding to the first blockchain is greater than or equal to the block height H2, the cross-chain message is forwarded to the consensus node of the second blockchain, so that the consensus node of the second blockchain verifies the validity of the cross-chain message according to the Merkle proof set corresponding to the cross-chain message and the block Merkle information of the verifiable height H1 in the first blockchain, and obtains the cross-chain verification result corresponding to the cross-chain message;

[0013] Among them, the block Merkle information is stored in the second blockchain, the Merkle proof set is obtained in the block Merkle tree corresponding to the block Merkle information, and the block Merkle tree includes multiple Merkle subtrees; when the cross-chain verification result indicates that the verification is successful, the consensus node of the second blockchain is used to store the transaction execution result corresponding to the cross-chain message to the second blockchain.

[0014] On the one hand, an embodiment of the present application provides a data processing device based on blockchain, including:

[0015] A cross-chain message acquisition unit, used to acquire the cross-chain message submitted by the forwarding service device, and acquire the chain identifier carried by the cross-chain message; the cross-chain message is associated with the cross-chain transaction data stored in the first blockchain;

[0016] A proof set acquisition unit is used to acquire the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and acquire the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information; the verifiable height H1 of the block Merkle information in the first blockchain is greater than or equal to the block height H2 of the cross-chain message in the first blockchain, and the block Merkle tree includes multiple Merkle subtrees;

[0017] The cross-chain message verification unit is used to verify the validity of the cross-chain message according to the Merkle proof set and the block Merkle information, and obtain the cross-chain verification result corresponding to the cross-chain message;

[0018] The cross-chain message execution unit is used to obtain the transaction execution result corresponding to the cross-chain message if the cross-chain verification result indicates that the verification is successful, and store the transaction execution result in the second blockchain.

[0019] The proof set acquisition unit acquires the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and acquires the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information, including:

[0020] In the chain verification contract deployed by the second blockchain corresponding to the chain identifier, obtaining the block Merkle information corresponding to the first blockchain;

[0021] Determine in the first blockchain the first cross-chain transaction block to which the cross-chain transaction data indicated by the cross-chain message belongs, and obtain block path information of the first cross-chain transaction block in the block Merkle tree corresponding to the block Merkle information;

[0022] Get the subtree root information corresponding to multiple Merkle subtrees contained in the block Merkle tree, and combine the subtree root information and the node information contained in the block path information into a Merkle proof set corresponding to the cross-chain message.

[0023] The proof set acquisition unit acquires the block path information of the first cross-chain transaction block in the block Merkle tree corresponding to the block Merkle information, including:

[0024] Obtain the block hash value corresponding to the first cross-chain transaction block, and determine the Merkle subtree to which the block hash value belongs in the block Merkle tree corresponding to the block Merkle information;

[0025] Taking the block hash value as the starting node information, traverse the hierarchical node information in the Merkle subtree to which the block hash value belongs until traversing to the subtree root information in the Merkle subtree to which the block hash value belongs, and determine the block path information corresponding to the first cross-chain transaction block according to the traversed hierarchical node information.

[0026] Among them, the cross-chain message verification unit verifies the validity of the cross-chain message according to the Merkle proof set and the block Merkle information, and obtains the cross-chain verification result corresponding to the cross-chain message, including:

[0027] Perform hash operation on the Merkle proof set to obtain the first candidate Merkle information corresponding to the first cross-chain transaction block, and obtain the block verification result corresponding to the first cross-chain transaction block by comparing the block Merkle information with the first candidate Merkle information;

[0028] Obtain transaction Merkle information in the block header of the first cross-chain transaction block, and obtain transaction path information of the cross-chain transaction data in the transaction Merkle tree corresponding to the transaction Merkle information; the transaction Merkle tree is determined by the transaction data included in the first cross-chain transaction block;

[0029] According to the transaction path information and transaction Merkel information, the validity of the cross-chain transaction data is verified to obtain the transaction verification result corresponding to the cross-chain transaction data;

[0030] If both the block verification result and the transaction verification result are successful verification results, then the cross-chain verification result corresponding to the cross-chain message is determined to indicate successful verification.

[0031] The cross-chain message verification unit compares the block Merkle information with the first candidate Merkle information to obtain a block verification result corresponding to the first cross-chain transaction block, including:

[0032] If the block Merkle information is consistent with the first candidate Merkle information, the block verification result corresponding to the first cross-chain transaction block is determined to be a successful verification result;

[0033] If the block Merkle information is inconsistent with the first candidate Merkle information, the block verification result corresponding to the first cross-chain transaction block is determined to be a verification failure result.

[0034] Among them, the cross-chain message verification unit verifies the validity of the cross-chain transaction data according to the transaction path information and transaction Merkel information, and obtains the transaction verification result corresponding to the cross-chain transaction data, including:

[0035] Perform hash operation on the transaction path information to obtain the second candidate Merkle information corresponding to the cross-chain transaction data;

[0036] If the transaction Merkle information is consistent with the second candidate Merkle information, the transaction verification result corresponding to the cross-chain transaction data is determined to be a successful verification result;

[0037] If the transaction Merkle information is inconsistent with the second candidate Merkle information, the transaction verification result corresponding to the cross-chain transaction data is determined to be a verification failure result.

[0038] The cross-chain message execution unit is used to obtain the transaction execution result corresponding to the cross-chain message if the cross-chain verification result indicates that the verification is successful, and store the transaction execution result in the second blockchain, including:

[0039] If the cross-chain verification result indicates that the verification is successful, the cross-chain message is encapsulated into the second cross-chain transaction block, and in the consensus phase of the second cross-chain transaction block, the transaction type corresponding to the cross-chain message is obtained;

[0040] The cross-chain management contract in the second blockchain calls the asset processor contract that matches the transaction type, performs transaction execution processing on the cross-chain message according to the asset processor contract, and obtains the transaction execution result corresponding to the cross-chain message;

[0041] The transaction execution result is added to the second cross-chain transaction block. If the second cross-chain transaction block reaches a consensus, the second cross-chain transaction block is stored in the second blockchain.

[0042] The device further comprises:

[0043] The cross-chain message verification failure unit is used to generate error prompt information corresponding to the cross-chain message if the cross-chain verification result indicates verification failure, and send the error prompt information to the forwarding service device through the cross-chain management contract in the second blockchain, so that the forwarding service device forwards the error prompt information to the cross-chain management contract in the first blockchain; the error prompt information is used to instruct the first blockchain to re-initiate the cross-chain message.

[0044] On the one hand, an embodiment of the present application provides a data processing device based on blockchain, including:

[0045] A block height acquisition unit, used to acquire a cross-chain message initiated by the first blockchain, and acquire a block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain; the cross-chain message carries a chain identifier;

[0046] A cross-chain message forwarding unit is configured to forward the cross-chain message to the consensus node of the second blockchain if it is detected in the second blockchain corresponding to the chain identifier that the verifiable height H1 corresponding to the first blockchain is greater than or equal to the block height H2, so that the consensus node of the second blockchain verifies the validity of the cross-chain message according to the Merkel proof set corresponding to the cross-chain message and the block Merkel information of the verifiable height H1 in the first blockchain, and obtains a cross-chain verification result corresponding to the cross-chain message;

[0047] Among them, the block Merkle information is stored in the second blockchain, the Merkle proof set is obtained in the block Merkle tree corresponding to the block Merkle information, and the block Merkle tree includes multiple Merkle subtrees; when the cross-chain verification result indicates that the verification is successful, the consensus node of the second blockchain is used to store the transaction execution result corresponding to the cross-chain message to the second blockchain.

[0048] The block height acquisition unit acquires a cross-chain message initiated by the first blockchain, and acquires a block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain, including:

[0049] Obtain the contract status corresponding to the cross-chain management contract in the first blockchain. If the contract status is a transaction pending forwarding state, obtain the cross-chain message initiated by the cross-chain management contract in the first blockchain;

[0050] Determine in the first blockchain a first cross-chain transaction block to which the cross-chain transaction data indicated by the cross-chain message belongs, and obtain a block height H2 of the first cross-chain transaction block in the first blockchain.

[0051] The device further comprises:

[0052] A verifiable height acquisition unit, used to obtain the verifiable height H1 corresponding to the first blockchain in the chain verification contract deployed by the second blockchain;

[0053] A prompt information generating unit, configured to generate a height update prompt information corresponding to the first blockchain if the verifiable height H1 is less than the block height H2;

[0054] A prompt information sending unit, configured to send the height update prompt information to the trusted oracle device, so that the trusted oracle device submits the block Merkle information corresponding to the maximum block height in the first blockchain to the chain verification contract in the second blockchain according to the height update prompt information;

[0055] Among them, the block Merkel information corresponding to the maximum block height is used to cover the block Merkel information and verifiable height H1 stored in the chain verification contract deployed by the second blockchain.

[0056] On one hand, an embodiment of the present application provides a computer device, including a memory and a processor, wherein the memory is connected to the processor, the memory is used to store a computer program, and the processor is used to call the computer program so that the computer device executes the method provided in the above aspect of the embodiment of the present application.

[0057] On one hand, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. The computer program is suitable for being loaded and executed by a processor, so that a computer device with a processor executes the method provided in the above aspect of the embodiment of the present application.

[0058] According to one aspect of the present application, a computer program product or computer program is provided, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the method provided in the above aspect.

[0059] In an embodiment of the present application, after obtaining the cross-chain message submitted by the forwarding service device, the consensus node of the second blockchain obtains the block Merkle information corresponding to the first blockchain from the second blockchain corresponding to the chain identifier in the cross-chain message, and obtains the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information. In other words, in the interactive communication between the first blockchain and the second blockchain, only part of the data indicated by the Merkle proof set needs to be stored on the second blockchain, and there is no need to store the full block header data in the first blockchain, which can reduce the data storage occupancy and save storage space. Furthermore, the verification capability of the block Merkle information can be relied on, that is, the validity of the cross-chain message can be verified according to the block Merkle information and the Merkle proof set, so that the cross-chain message under the block height H2 can be quickly verified, and the verification efficiency of the cross-chain message can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0061] Figure 1 It is a schematic diagram of a blockchain network hierarchical structure provided by an embodiment of the present application;

[0062] Figure 2 It is a schematic diagram of a multi-chain structure of a blockchain network provided in an embodiment of the present application;

[0063] Figure 3 It is a flowchart of a data processing method based on blockchain provided in an embodiment of the present application;

[0064] Figure 4 This is a schematic diagram of creating a block Merkle tree provided in an embodiment of the present application;

[0065] Figure 5 It is a schematic diagram of a block structure provided in an embodiment of the present application;

[0066] Figure 6 This is a timing diagram of a blockchain-based data processing method provided in an embodiment of the present application;

[0067] Figure 7 It is a block data verification schematic diagram based on the Merkel Mountains provided in an embodiment of the present application;

[0068] Figure 8 It is a schematic diagram of a cross-chain message verification process provided by an embodiment of the present application;

[0069] Fig. 9 This is a schematic diagram of the overall structure of a cross-chain technology between different blockchains provided in an embodiment of the present application;

[0070] Fig.10 It is a structural diagram of a trusted prediction device provided in an embodiment of the present application;

[0071] Fig.11 This is a system architecture diagram of a tax blockchain system provided by an embodiment of the present application;

[0072] Fig.12 This is a schematic diagram of a data processing device based on blockchain provided in an embodiment of the present application. Figure 1 ;

[0073] Fig.13 This is a schematic diagram of a data processing device based on blockchain provided in an embodiment of the present application. Figure 2 ;

[0074] Fig.14 It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0075] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0076] For ease of understanding, the basic technologies involved in the embodiments of the present application are described below:

[0077] Blockchain: Blockchain is a decentralized infrastructure with distributed storage characteristics. Specifically, it is a data structure that organizes data blocks in a time sequence in a linked list-like manner. It can safely store data that has a sequential relationship and can be verified within the system, and cryptographically ensure that the data has the characteristics of traceability, non-repudiation, non-tampering, non-forgeability, and decentralization. Blockchain can usually be composed of consensus, transaction blocks and state data storage, cryptographic identity security, etc. The underlying blockchain platform can include basic services, smart contracts, and operation management processing modules.

[0078] Among them, the basic service module is deployed on all blockchain nodes to verify the validity of business requests and record the valid requests to the storage after consensus is reached. For a new business request, the basic service first performs interface adaptation analysis and authentication processing (interface adaptation), and then encrypts the business information through the consensus algorithm (consensus management). After encryption, it is transmitted to the shared ledger in a complete and consistent manner (network communication) and recorded and stored; the smart contract module is responsible for the registration and release of contracts, as well as contract triggering and contract execution. Developers can define the contract logic in a certain programming language and publish it to the blockchain (contract registration). According to the logic of the contract terms, the key or other event triggers the execution to complete the contract logic. At the same time, it also provides the function of contract upgrade and cancellation; the operation management module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation and real-time status visualization output of the product during the product release process, such as alarms, management network conditions, management node equipment health status, etc. It can be understood that the embodiments of the present application may involve cross-chain transaction processing between different blockchains (for example, a first blockchain and a second blockchain), and different blockchains may be responsible for different business types. The interaction and communication between multiple blockchains are completed through cross-chain technology based on MMR (Merkle Mountain Range, which can be called the Merkle Mountain Range, or the range Merkle proof).

[0079] Smart contract: A computer protocol designed to disseminate, verify or execute contracts in an information-based manner. Smart contracts can be understood as computer programs that run on a distributed ledger (i.e., blockchain) with preset rules, states, and conditional responses, and can encapsulate, verify, and execute complex behaviors of distributed nodes to complete information exchange, value transfer, and asset management. Based on the distributed architecture and consensus algorithm of blockchain, smart contracts allow users who do not trust each other to complete transactions without the need for any third-party trusted intermediary or authority; at the same time, digital smart contracts can be flexibly embedded in various tangible or intangible assets, transactions, and data to achieve active or passive asset and information management and control, and gradually build programmable smart assets, systems, etc. Unlike ordinary programs, smart contracts can ensure that the results of each blockchain node in the blockchain network are exactly the same, so that any blockchain node can verify whether the results of the smart contract execution in the data block are correct. In the embodiments of the present application, different smart contracts can be deployed in the blockchain according to the demand types of specific application scenarios. That is to say, different smart contracts can have different functions. The embodiments of the present application can be named according to the functions of the smart contracts. For example, the smart contract for managing the permissions of lightweight nodes (Simplified Payment Verification, SPV) can be called an SPV permission contract, and the smart contract for clearing general tax data can be called a general data clearing contract, etc.

[0080] P2P (Peer-to-Peer) network: a peer-to-peer network based on a specific type of network protocol. Network nodes do not need a central node to maintain the network status. Instead, each network node can maintain the node status of the entire network or the connection status of its adjacent nodes through broadcast interactions with adjacent network nodes.

[0081] Digital certificate: In the Public Key Infrastructure (PKI), a digital certificate is an identity certificate of a public key holder. The digital certificate can be issued by an authority, which is called a Certificate Authority (CA). Asymmetric encryption and digital signatures for information can be implemented based on the public key certificate system.

[0082] Alliance chain: A blockchain with an access mechanism, including consensus nodes and non-consensus nodes (for ease of understanding, the non-consensus nodes in the embodiments of this application can be called business nodes). Generally speaking, any smart contract on the blockchain requires all consensus nodes to execute. If the execution results are consistent, it can be determined that the consensus nodes on the blockchain have reached a consensus; business nodes usually do not execute smart contracts on the blockchain, but can synchronize the execution results of smart contracts from consensus nodes.

[0083] Subchain (or branch chain): a concept relative to the parent chain (or main chain), which can be simply understood as a blockchain built on the underlying parent chain. Subchains are representatives of various industries or vertical fields of blockchains, and are also a general term for various types of blockchains in various fields. When a subchain is created, the relevant information of the subchain can be recorded in the parent chain, that is, data added to the subchain must rely on the parent chain for storage, verification, and traceability.

[0084] Transaction: A form of blockchain execution. The transaction contains the private key signature of the initiator, which can ensure the authenticity, non-forgeability and non-repudiation of the transaction content.

[0085] See also Figure 1 , Figure 1 This is a schematic diagram of a blockchain network hierarchical structure provided in an embodiment of the present application. The blockchain network hierarchical structure in the embodiment of the present application can be Figure 1 The blockchain network 1 shown in FIG. 1 , the complete blockchain business system corresponding to the blockchain network 1 can be Figure 1 The business network (also referred to as a witness network), the core consensus network, and the routing proxy network shown are composed. Among them, the number of nodes of the proxy node in the routing proxy network can be one or more, which is not limited here. Taking the proxy node 10i as an example in the embodiment of the present application, the proxy node 10i can be used to isolate the business network and the core consensus network. The proxy node 10i can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services, which is not limited here. The proxy node 10i can layer the peer-to-peer (Peer To Peer, referred to as P2P) network to form a layered structure such as "business network-core consensus network", which can improve the confidentiality and security of data on the blockchain.

[0086] in, Figure 1The business network shown may include one or more blockchain nodes, and there is no limit on the number of nodes in the business network. For example, the business network may specifically include node 10a, node 10b, node 10c, ..., node 10h, etc.; the blockchain nodes in the business network may be referred to as business nodes in the embodiment of the present application. Business nodes do not need to participate in bookkeeping consensus and are mainly used to execute transaction services to obtain corresponding business transactions. Among them, the business node here can be a full node containing a complete blockchain database, or it can be a lightweight node that stores part of the data in the blockchain database, which will not be limited here. In order to reduce the waste of storage space of business nodes, the business node in the embodiment of the present application takes the SPV node as an example. The business node does not need to store complete transaction data, but uses the proxy node 10i to obtain the data from the proxy node 10i. Figure 1 In the core consensus network shown, block header data and partially authorized visible block data (e.g., business transactions associated with the business node itself) are obtained.

[0087] in, Figure 1 The core consensus network shown may also include one or more blockchain nodes, and the number of nodes in the core consensus network will not be limited here. For example, the core consensus network may specifically include node 10j, node 10k, node 10m, ..., node 10s, etc. In the embodiment of the present application, the blockchain nodes in the core consensus network may be referred to as consensus nodes (also referred to as accounting nodes), and these consensus nodes may run the blockchain consensus protocol.

[0088] It should be understood that the embodiments of the present application may collectively refer to proxy nodes, business nodes, and consensus nodes as blockchain nodes in the blockchain network 1. Among them, the blockchain node may be a server connected to the blockchain network 1, or a terminal device connected to the blockchain network 1. The specific form of the blockchain node is not limited here. For example, terminal devices may include but are not limited to: PC (Personal Computer), smart phones, tablet computers, laptops, PDAs, mobile Internet devices (mobile internet devices, MID), wearable devices (such as smart watches, smart bracelets, etc.), smart voice interaction devices, smart home appliances (such as smart TVs, etc.), vehicle-mounted devices, aircraft and other electronic devices. The server may be an independent physical server, or it may be a server cluster or distributed system composed of multiple physical servers, or it may be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and basic cloud computing services such as big data and artificial intelligence platforms. This application does not limit the type of server. It is understandable that, Figure 1 The business network and core consensus network shown can be in different network environments. For example, the business nodes can be deployed in the business network on the public network, while the consensus nodes running the blockchain consensus protocol are deployed in the private core consensus network. The two can interact through the routing boundary.

[0089] like Figure 1 As shown, the core consensus network may include blockchain 10t (the blockchain 10t may include the genesis block, block B1, block B2, block B3, block B4, block B5, etc.), and the blockchain 10t may set consensus permissions. When a node 10j in the core consensus network has consensus permissions for blockchain 10t, it means that the node 10j can independently reach consensus on blockchain 10t, that is, it can participate in the consensus process of the blocks contained in blockchain 10t. The consensus nodes in the core consensus network that have consensus permissions for blockchain 10t may constitute an independent blockchain consensus network, which may include all or part of the consensus nodes in the core consensus network. The number of consensus nodes in the independent blockchain consensus network is not limited here. For example, if Figure 1The blockchain network 1 shown is a tax blockchain system used in tax business. The consensus node that independently reaches consensus on the blockchain 10t can be a terminal device used by the tax management agency (e.g., the State Administration of Taxation, local tax bureau, etc.) in the tax blockchain system. The consensus node can be used to submit business transaction data in the tax business to the blockchain 10t. Among them, the tax business here can specifically include different types of transaction businesses such as bill business, credit business, loss business, enterprise qualification business, and tax refund business. It should be understood that in a composite environment of multiple types of transaction businesses, the embodiments of the present application can Figure 1 The two-layer structure of the blockchain network shown is expanded into a multi-chain structure. Different blockchains can be responsible for different business directions, and different blockchains can interact and communicate with each other through cross-chain technology based on MMR.

[0090] In other words, the blockchain included in the core consensus network Figure 1 In addition to the blockchain 10t shown, it can also include blockchains corresponding to various types of transaction services. The blockchain 10t and the blockchains corresponding to the various types of transaction services can be independent blockchains in the core consensus network; or, the various types of transaction services can be transaction services derived from the blockchain 10t in the core consensus network, that is, the blockchains corresponding to the various types of transaction services can be branch chains (child chains) of the blockchain 10t, and the blockchain 10t at this time can be called the main chain (parent chain). The embodiment of the present application does not limit the relationship between the blockchains included in the core consensus network.

[0091] Optionally, if multiple blockchains in the core consensus network are independent blockchains, then the consensus nodes in the core consensus network that have consensus authority for each blockchain can submit business transaction data to the corresponding blockchain. For example, the core consensus network contains two independent blockchains (for ease of understanding, the two blockchains here can be recorded as blockchain A and blockchain B), all consensus nodes with consensus authority for blockchain A can constitute an independent consensus network of blockchain A, and all consensus nodes with consensus authority for blockchain B can constitute an independent consensus network of blockchain B. The independent consensus network of blockchain A and the independent consensus network of blockchain B can include the same consensus nodes or different consensus nodes, and this application does not limit this. For example, if blockchain A is the blockchain corresponding to the bill business, then the consensus nodes in the independent consensus network of blockchain A can be used to add business transaction data in the bill business to blockchain A; if blockchain B is the blockchain corresponding to the loss-in and loss-out business, then the consensus nodes in the independent consensus network of blockchain B can be used to add business transaction data in the loss-in and loss-out business to blockchain B. It can be understood that the independent consensus network of blockchain A corresponding to blockchain A and the independent consensus network of blockchain B corresponding to blockchain B can be collectively referred to as independent consensus networks.

[0092] Optionally, if the multiple blockchains in the core consensus network include a main chain (e.g., blockchain 10t) and multiple branch chains corresponding to multiple transaction services derived from the main chain. Blockchain 10t (main chain) may include registration information of branch chains corresponding to each transaction service, and the registration information of branch chains corresponding to each transaction service may include the chain identifier of the branch chain, the business configuration information of the transaction service, the derivation conditions corresponding to the chain identifier, etc. Among them, the business configuration information of the transaction service (e.g., bill service) may include basic information of the transaction service (i.e., description of the bill service) and node configuration information (business node configuration information and consensus node configuration information). The business node configuration information may include business nodes for executing transaction services (e.g., bill services), that is, the business nodes included in the business node configuration information may constitute a branch chain independent business network; the consensus node configuration information may include consensus nodes for participating in the independent consensus of the branch chain, that is, the consensus nodes included in the consensus node configuration information all have the consensus authority for the branch chain, and may constitute a branch chain independent consensus network. The derived conditions corresponding to each branch chain can determine the genesis block of the corresponding branch chain on the blockchain 10t (main chain), and each branch chain is obtained by the derived conditions on the main chain. Among them, a branch chain corresponds to a transaction business, and a branch chain corresponds to a chain identifier, which can effectively distinguish different transaction businesses to maintain the specificity of the data stored in a single branch chain. It can be understood that the main chain independent business network corresponding to the main chain and the branch chain independent business network corresponding to each branch chain can be collectively referred to as independent business networks; the main chain independent consensus network and the branch chain independent consensus network can also be referred to as independent consensus networks.

[0093] It is understandable that in the embodiments of the present application, whether multiple independent blockchains or the main chain and its corresponding branch chains, can be collectively referred to as blockchains, and all blockchains involved in the embodiments of the present application can be alliance chains. In the multi-layer structure of the blockchain network, each blockchain can have its corresponding independent consensus network and corresponding independent business network; among them, the independent consensus network can be composed of Figure 1 The blockchain independent business network can be composed of some or all of the consensus nodes in the core consensus network shown in the figure. Figure 1 The business network shown is composed of some or all business nodes. Different blockchains can interact and communicate through cross-chain technology based on MMR, but independent business networks corresponding to different blockchains cannot interact directly.

[0094] For further understanding, please refer to Figure 2 , Figure 2 Schematic diagram of a multi-chain structure of a blockchain network provided in an embodiment of the present application. Figure 2As shown, the embodiment of the present application takes the electronic bill three-chain network as an example to describe the multi-chain structure of the blockchain network; the complete blockchain business system corresponding to the multi-chain structure of the blockchain network can be composed of business network participants (which can be considered as business nodes in the business network), electronic bill three-chain network and government intranet / alliance chain internal participants (which can be considered as consensus nodes in the core consensus network). Among them, business network participants can include but are not limited to: personal objects, corporate objects, local bill lightweight node 1 (SPV1), local bill SPV2, application X bill SPV and branch chain X bill SPV, etc.; the electronic bill three-chain network can include but are not limited to: management chain 20a, bill chain 20b, application contract chain 20c and branch chain 20d derived from the application contract chain 20c, etc.; the internal participants of the government intranet / alliance chain can include but are not limited to: management chain full SPV and its corresponding tax management agency, bill chain full SPV and its corresponding electronic bill data center, application contract chain full SPV and its corresponding government cooperation agency, business association agency, etc.

[0095] It is understandable that different blockchains can correspond to different business network participants and internal participants of the alliance chain. Figure 2 As shown, the business network participants corresponding to the management chain 20a may include personal objects and corporate objects, etc. Personal objects and corporate objects can obtain block header data and partially authorized visible block data (for example, business transactions associated with themselves) in the management chain 20a through the entrance of the tax management agency; the internal participants of the government intranet / alliance chain corresponding to the management chain 20a may include the tax management agency, and the tax management agency can hold the complete block data in the management chain 20a as the full SPV of the management chain.

[0096] The business network participants corresponding to the bill chain 20b may include local bill SPV1, local bill SPV2, application X bill SPV and branch chain X bill SPV, etc. Local bill SPV1, local bill SPV2, application X bill SPV and branch chain X bill SPV, etc. can obtain the block header data and partially authorized visible block data in the bill chain 20b through the electronic bill business entrance; the internal participants of the government intranet / alliance chain corresponding to the bill chain 20b may include the electronic bill data center, which can hold the complete block data in the bill chain 20b as the full SPV of the bill chain.

[0097] The business network participants corresponding to the application contract chain 20c may include the application X bill SPV, etc. The application X bill SPV may obtain the block header data and partially authorized visible block data in the application contract chain 20c through the tax derivative business entrance; the internal participants of the government intranet / alliance chain corresponding to the application contract chain 20c may include government cooperation agencies and business related agencies, etc. The government cooperation agencies and business related agencies may hold the complete block data in the application contract chain 20c as the full amount SPV of the application contract chain. Branch chain 20d is the business branch chain corresponding to the transaction business derived from the application contract chain 20c (any bill type in the electronic bill business, such as X bill type). The business network participants corresponding to the branch chain 20d may include the application X bill SPV and the branch chain X bill SPV, etc. The application X bill SPV and the branch chain X bill SPV may obtain the block header data and partially authorized visible block data in the branch chain 20d through the tax derivative business entrance; the branch chain 20d may have the same government intranet / alliance chain internal participants as the application contract chain 20c, and this embodiment of the application does not limit this. It is understandable that the tax administration agency entrance, electronic invoice business entrance and tax derivative business entrance can all be considered as Figure 1 Proxy nodes in the routing proxy network shown.

[0098] like Figure 2 As shown, a global management information contract can be deployed in the management chain 20a, which can be used to manage the full amount of management information in the tax business. The management chain 20a can be mainly responsible for tax metadata management. Smart contracts such as global information cross-chain contracts, electronic bill rights clearing contracts, electronic bill SPV rights contracts, and electronic bill business contracts can be deployed in the bill chain 20b. Smart contracts such as global information cross-chain contracts, application chain SPV rights contracts, various tax application contracts, and general data clearing contracts can be deployed in the application contract chain 20c. The branch chain 20d of the application contract chain 20c can be deployed with smart contracts such as global information cross-chain contracts, branch chain SPV rights contracts, dedicated tax application contracts, and general data clearing contracts.

[0099] Among them, the global information cross-chain contract can be responsible for the cross-chain processing of the complete data stored in the corresponding blockchain; the electronic bill SPV permission contract can be used to manage the business node corresponding to the bill chain 20b's read permission for the data stored in the bill chain 20b; the electronic bill permission clearing contract is responsible for synchronizing the business transaction data stored in the bill chain 20b to the business node with read permission; the electronic bill business contract is responsible for processing the business transaction data (for example, electronic bill transaction data) submitted to the bill chain 20b. Various tax application contracts and special tax application contracts can include a data clearing interface, through which the business transaction data stored in the corresponding blockchain can be synchronized to the business node with read permission; the general data clearing contract is responsible for synchronizing the general data stored in the corresponding blockchain to the business node with read permission; the application chain SPV permission contract can be used to manage the business node corresponding to the application contract chain 20c's read permission for the data stored in the application contract chain 20c; the branch chain SPV permission contract can be used to manage the business node corresponding to the branch chain 20d's read permission for the data stored in the branch chain 20d.

[0100] It is understandable that multiple blockchains in the electronic bill three-chain network can interact and communicate through cross-chain relays. The cross-chain relay can be understood as establishing a channel between two blockchains, creating a specific data structure in the channel, so that the two blockchains can interact with each other through the data structure in the channel. The channel established between the two blockchains can be called a cross-chain relay. In other words, different blockchains cannot interact and communicate directly, but need to interact and communicate through cross-chain technology. An important link in cross-chain technology is the verification process of cross-chain messages. In order to improve the verification efficiency of cross-chain messages, the embodiment of the present application proposes a cross-chain technology based on MMR (Merkel Mountains); in the cross-chain technology based on MMR, the verification capability of the MMR root can be relied on to quickly verify the cross-chain message at a certain block height; at the same time, in order to ensure the correctness of the MMR root information, the TEE (Trusted Execution Environment) trusted oracle can be introduced to maintain and submit the MMR root information. In other words, in the MMR-based cross-chain technology proposed in the embodiment of the present application, each blockchain only needs to store part of the MMR root information to complete the verification of the cross-chain message, which can reduce the data storage occupancy and improve the verification efficiency of the cross-chain message.

[0101] The specific implementation process of the MMR-based cross-chain technology provided in the embodiment of the present application can be found in the following Figures 3 to 11 The corresponding embodiment.

[0102] See also Figure 3 , Figure 3 It is a flowchart of a blockchain-based data processing method provided in an embodiment of the present application. It can be understood that the blockchain-based data processing method can be applied in a cross-chain communication scenario between a first blockchain and a second blockchain, and the blockchain-based data processing method here can be executed by any consensus node on the second blockchain; Figure 3 As shown, the blockchain-based data processing method may include at least the following steps S101 to S104:

[0103] Step S101, obtaining a cross-chain message submitted by a forwarding service device, and obtaining a chain identifier carried by the cross-chain message; the cross-chain message is associated with the cross-chain transaction data stored in the first blockchain.

[0104] Among them, in the multi-chain structure of the blockchain network (for example, Figure 2 In the electronic bill network in the corresponding embodiment, the interaction and communication between different blockchains can be maintained by adopting cross-chain technology. The embodiment of the present application takes the interaction between the first blockchain and the second blockchain as an example to describe. The first blockchain and the second blockchain can jointly execute the same transaction, such as asset custody authorization, cross-chain transfer request and other transactions. At this time, the first blockchain can be understood as the blockchain that initiates the cross-chain message, and the second blockchain can be understood as the blockchain that receives and executes the cross-chain message. In one or more embodiments, the object can use its own resource client to initiate cross-chain transaction data through the cross-chain service end, and the cross-chain service end submits the cross-chain transaction data to the first blockchain. When the cross-chain transaction data is successfully stored in the first blockchain, the cross-chain management contract deployed in the first blockchain can initiate a cross-chain message corresponding to the cross-chain transaction data.

[0105] Among them, the resource client used by the object can be used to implement the resource management business function, and based on the resource management business function, realize the communication connection with the cross-chain server (a decentralized application). The resource client is a tool for managing and storing user digital resources; for example, digital resources can be transferred to other accounts based on the resource client, and digital resources transferred from other accounts can be received based on the resource client. The resource client can be a hardware device or a software program. In the embodiment of the present application, the resource client used by the object can establish a communication connection with the cross-chain server to implement related operations such as authorized login of the object. It can be understood that with the widespread deployment of various decentralized applications on the blockchain, the activities of objects on the blockchain have increased. When using decentralized applications, general objects can use the resource client to log in. The address in the resource client corresponds to an object on the blockchain. The decentralized application can obtain the object address from the resource client through some interfaces, solving the problem that the decentralized application cannot trust the object address used when logging in.

[0106] The cross-chain service end may refer to a service platform that interacts with the object that initiates the cross-chain business. The cross-chain service end may include a cross-chain service front end and a cross-chain service back end. The cross-chain service front end may include but is not limited to web pages, applications, subprograms embedded in applications (for example, they may be called mini-programs), etc.; the cross-chain service back end may be a background service corresponding to the cross-chain service front end, such as a web page background service, an application background service, etc. The cross-chain service back end may be used to provide data and blockchain transaction functions for the cross-chain service front end.

[0107] Cross-chain transaction data may refer to a transaction encapsulated by a cross-chain transaction initiated by an object through its own resource client on a cross-chain server. The cross-chain transaction data may be a transaction encapsulated by an asset custody authorization request, or a transaction encapsulated by a cross-chain transfer request, etc. A cross-chain message may refer to the cross-chain transaction part initiated by the first blockchain to the second blockchain after completing the cross-chain transaction part for which it is responsible; that is, a cross-chain message may be understood as a cross-chain transaction initiated by the first blockchain for cross-chain transaction data. A cross-chain management contract may be pre-deployed in both the first blockchain and the second blockchain. The cross-chain management contract may be used as a submission entry for cross-chain transactions to manage cross-chain transactions received by the blockchain. The cross-chain management contract involved in the embodiment of the present application may specifically be a cross-chain bridge contract. It can be understood that a cross-chain bridge may refer to a system for transmitting information between two or more blockchains. That is, information transmission between two or more blockchains may be achieved through a cross-chain bridge. The information here may include but is not limited to digital assets, contract calls, proofs or status, etc.

[0108] In the embodiment of the present application, the forwarding service device can detect the cross-chain management contracts in each blockchain in real time. If the forwarding service device detects that the cross-chain management contract deployed in the first blockchain initiates a cross-chain message, the cross-chain message can be obtained from the cross-chain management contract deployed in the first blockchain, and the cross-chain message is submitted to the cross-chain management contract in the second blockchain. Among them, the premise that the forwarding service device forwards the cross-chain message initiated by the cross-chain management contract in the first blockchain to the second blockchain is that the block height H2 where the cross-chain message is located in the first blockchain is less than or equal to the verifiable height H1 corresponding to the first blockchain stored in the second blockchain. The forwarding service device can be used to forward cross-chain messages between different blockchains, that is, the forwarding service device can be used to provide cross-chain message forwarding services; the forwarding service device does not need to ensure the correctness of the cross-chain message, it only needs to submit the cross-chain message initiated by the first blockchain it detects to the second blockchain as it is.

[0109] The consensus node of the second blockchain (i.e., any consensus node with consensus authority for the first blockchain, such as any consensus node in the independent consensus network corresponding to the second blockchain) can obtain the cross-chain message submitted by the forwarding service device through the cross-chain management contract in the second blockchain. The cross-chain message may include a chain identifier corresponding to the blockchain for receiving the cross-chain message, and the consensus node of the second blockchain can obtain the chain identifier carried by the cross-chain message, and the blockchain corresponding to the chain identifier can be called the second blockchain.

[0110] Step S102, obtaining the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and obtaining the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information; the verifiable height H1 of the block Merkle information in the first blockchain is greater than or equal to the block height H2 of the cross-chain message in the first blockchain, and the block Merkle tree includes multiple Merkle subtrees.

[0111] Among them, the block Merkle information may refer to the MMRR (Merkle Mountain Range Root) information corresponding to the maximum block height in the first blockchain. The block Merkle tree may refer to the MMR tree composed of all blocks contained in the first blockchain, and the leaf nodes in the MMR tree at this time are the blocks in the first blockchain (specifically, the hash values ​​corresponding to the blocks); or, the block Merkle tree may also refer to the MMR tree composed of the block headers of all blocks contained in the first blockchain, and the leaf nodes in the MMR tree at this time are the block headers of all blocks in the first blockchain (specifically, the hash values ​​corresponding to the block headers), which is not limited in this application. The Merkle proof set (or MMR proof set) refers to the partial node information in the MMR tree that the second blockchain needs to use when verifying the validity of the cross-chain message. In other words, when verifying the validity of the cross-chain message, it is not necessary to store all the node information in the block Merkle tree, but only the node information in the Merkle proof set needs to be stored, which can save storage space and reduce the amount of data storage occupied.

[0112] For further information, see Figure 4 , Figure 4It is a schematic diagram of creating a block Merkle tree provided in an embodiment of the present application; the block Merkle tree in the embodiment of the present application is an MMR tree, and the following is an example of a first blockchain containing three data blocks (for example, block 1, block 2, and block 3, where block 0 is a genesis block). When block 1 is generated in the first blockchain, and block 1 reaches a consensus in the independent consensus network corresponding to the first blockchain, block 1 can be added to the first blockchain. At this time, block 0 (genesis block) and block 1 can form an MMR tree. At this time, the MMR tree can include two levels of node information (including block 0, block 1, and parent node information 1 generated by block 0 and block 2). At this time, the MMR root corresponding to the MMR tree can be recorded as Merkle Mountain Root 1 (can be recorded as MMRR1).

[0113] Next, if block 2 is added to the first blockchain, MMRR1 can be included in block 2. Since there is no leaf node at the same level as block 2 in the MMR tree, block 2 can be added to the MMR tree as a Merkle subtree, and block 0 and block 1 constitute another Merkle subtree in the MMR tree. At this time, the subtree roots of the two Merkle subtrees (i.e. block 2 and MMRR1) can be merged into Merkle mountain root 2 (which can be recorded as MMRR2).

[0114] Furthermore, if the first blockchain continues to add block 3, then block 3 can include MMRR2. Since there is block 2 at the same level as block 3 in the MMR tree, parent node information 2 corresponding to block 2 and block 3 can be generated. The parent node information 2 is at the same level as the aforementioned parent node information 1, so parent node information 3 corresponding to parent node information 1 and parent node information 2 can be generated, thereby obtaining the MMR tree corresponding to the maximum block height (the maximum block height here is 3). At this time, the MMR root corresponding to the MMR tree can be recorded as Merkel mountain root 3 (can be recorded as MMRR3).

[0115] Depend on Figure 4 From the construction process of the MMR tree shown, it can be seen that when a new block is added to the first blockchain (it can refer to the leaf node information in the MMR tree, and all blocks in the first blockchain can be used as leaf node information in the MMR tree), the intermediate node information in the MMR tree (for example, the aforementioned parent node information 1, parent node information 2, and parent node information 3, etc.) will not change, and the data is always added to the MMR tree in an appended form. No additional data structure support is required in the process of building the MMR tree. You only need to add the previous MMR root to each block, such as adding MMRR1 (Merkel range root 1) to block 2, and MMRR2 (Merkel range root 2) to block 3, and so on. It should be noted that Figure 4MMRR1, MMRR2, and MMRR3 in the MMR tree are different root information. It seems that MMRR2 replaces MMRR1, and MMRR3 replaces MMRR2. In fact, they are not replacement relationships. It is just that the Merkle Mountain root corresponding to the time point when block 1 joins the MMR tree is MMRR1, and the Merkle Mountain root corresponding to the time point when block 2 joins the MMR tree is MMRR2, etc. In other words, MMRR1, MMRR2, and MMRR3 are the Merkle Mountain roots of the MMR tree at different time points. Based on this feature of the MMR tree, one Merkle Mountain root (MMRR) can cover all nodes. At the same time, after each block is established, the corresponding Merkle Mountain root does not need to be changed. It only needs to add a field in the block header of each block to store the previous Merkle Mountain root, which can avoid hard forks or soft forks. Optionally, when constructing the MMR tree corresponding to the first blockchain, the block headers of all blocks contained in the first blockchain can be used to construct it, or the full data of all blocks contained in the first blockchain can be used to construct it. This application is not limited to this. Through the construction principle of MMR, the consensus node of the second blockchain only needs a small amount of proof data (that is, the node information in the MMR tree contained in the Merkel proof set), that is, it can verify whether block 3 and block 0 are in the same blockchain, which can save storage space.

[0116] Specifically, the block Merkle information corresponding to the first blockchain can be obtained in the chain verification contract deployed by the second blockchain corresponding to the chain identifier (the chain verification contract here can specifically be the first blockchain verification contract, and one blockchain can correspond to one chain verification contract); determine in the first blockchain the first cross-chain transaction block to which the cross-chain transaction data indicated by the cross-chain message belongs, and obtain the block path information of the first cross-chain transaction block in the block Merkle tree corresponding to the block Merkle information; obtain the subtree root information corresponding to multiple Merkle subtrees contained in the block Merkle tree, and combine the subtree root information and the node information contained in the block path information into a Merkle proof set corresponding to the cross-chain message.

[0117] Optionally, the process of obtaining the block path information may include: obtaining the block hash value corresponding to the first cross-chain transaction block, determining the Merkle subtree to which the block hash value belongs in the block Merkle tree corresponding to the block Merkle information; using the block hash value as the starting node information, traversing the hierarchical node information in the Merkle subtree to which the block hash value belongs, until traversing to the subtree root information in the Merkle subtree to which the block hash value belongs, and determining the block path information corresponding to the first cross-chain transaction block according to the traversed hierarchical node information. In other words, starting from the leaf node information (block hash value) corresponding to the first cross-chain transaction block, searching for the upper parent node information in the block Merkle tree (MMR tree) until the first cross-chain transaction block ends at the subtree root information (Merkle TreeRoot, MTR) of the Merkle subtree to which the block Merkle tree belongs, the set of node information searched through may be referred to as the block path information corresponding to the first cross-chain transaction block.

[0118] Among them, in the multi-chain structure of the blockchain network, verification contracts of multiple blockchains can be deployed in each blockchain. For example, assuming that the multi-chain structure of the blockchain network contains four blockchains, which are respectively recorded as the first blockchain, the second blockchain, the third blockchain and the fourth blockchain; the second blockchain verification contract, the third blockchain verification contract and the third blockchain verification contract can be deployed in the first blockchain; the first blockchain verification contract, the third blockchain verification contract and the fourth blockchain verification contract can be deployed in the second blockchain; and so on; a chain verification contract deployed in a blockchain corresponds to one blockchain. Each chain verification contract can be used to store the latest block Merkle information (MMR root information) on the corresponding blockchain and update the corresponding verifiable height H1.

[0119] For further information, see Figure 5 , Figure 5 It is a block structure schematic diagram provided in an embodiment of the present application. Figure 5 The blockchain shown may be a first blockchain (specifically may include a genesis block, block 1, block 2, block 3, block 4, and block 5), Figure 5 The block 4 shown may be the first cross-chain transaction block to which the cross-chain transaction data belongs in the first blockchain. Block 4 may be composed of a block header and a block body, the block body may be used to store the transaction data (including cross-chain transaction data) encapsulated in the block 4, and the block header may include a version number, a timestamp, a difficulty value, a target hash, a block header hash value of the previous block (i.e., a block header hash value of block 3), a Merkle tree root (transaction Merkle information), and a Merkle mountain root (block Merkle information).

[0120] The Merkle tree root in the block header may refer to the root information corresponding to the Merkle tree obtained by performing hash operations on multiple transaction data stored in block 4 (specifically, transaction tx1, transaction tx2, transaction tx3, and transaction tx4). The hash value corresponding to transaction tx1 may be recorded as Hash1, the hash value corresponding to transaction tx2 may be recorded as Hash2, and so on; by performing hash operations on Hash1 and Hash2, a hash value Hash(1&2) may be obtained, and by performing hash operations on Hash3 and Hash4, a hash value Hash(3&4) may be obtained; by performing hash operations on Hash(1&2) and Hash(3&4), a hash value Hash((1&2)&(3&4)) may be obtained, thereby constructing a Merkle tree corresponding to all transaction data stored in block 4. The Merkle Mountain root in the block header may refer to the MMR tree obtained by hashing the three block headers before block 4, that is, the Merkle Mountain root in the block header of block 4 may be the Merkle Mountain root corresponding to block 3. The hash value corresponding to the block header of block 1 is recorded as Hash5, the hash value corresponding to the block header of block 2 is recorded as Hash6, and the hash value corresponding to the block header of block 3 is recorded as Hash7; the hash value Hash(5&6) is obtained by hashing Hash5 and Hash6, and the Merkle Mountain root in the block header can be obtained by merging Hash7 and Hash(5&6).

[0121] It should be noted that the hash algorithm used in the hash operation involved in the embodiments of the present application may include but is not limited to: SHA-1, SHA-224, SHA-256, SHA-384 and SHA-512, and this application does not limit this.

[0122] Step S103: Verify the validity of the cross-chain message according to the Merkle proof set and the block Merkle information to obtain the cross-chain verification result corresponding to the cross-chain message.

[0123] Specifically, in an embodiment of the present application, the verification capability of the block Merkle information (MMR root information) can be relied upon, and the first blockchain verification contract in the second blockchain can be called by the cross-chain management contract in the second blockchain to quickly verify the validity of the cross-chain message. For example, the validity of the cross-chain message can be verified based on a Merkle proof set (such as a Merkle mountain proof set) and block Merkle information (such as MMR root information) to obtain a cross-chain verification result corresponding to the cross-chain message.

[0124] Among them, the validity verification process of the cross-chain message can include the verification of the first cross-chain transaction block to which the cross-chain transaction data indicated by the cross-chain message belongs and the verification of the cross-chain transaction data, wherein the verification of the first cross-chain transaction block is based on the block Merkel information (MMR root information) and its corresponding block Merkel tree (MMR tree), and the verification of the cross-chain transaction data is based on the transaction Merkel information (the Merkel tree root in the block header of the first cross-chain transaction block) and its corresponding transaction Merkel tree (the Merkel tree corresponding to all transaction data in the block body of the first cross-chain transaction block).

[0125] If the cross-chain verification result indicates that the verification is successful, it means that the cross-chain message is stored in the first blockchain and the cross-chain message is intact and not tampered with. If the cross-chain verification result indicates that the verification fails, it means that the cross-chain message is not stored in the first blockchain or the cross-chain message is tampered with, and an error prompt message corresponding to the cross-chain message can be generated, and the error prompt message is sent to the forwarding service device through the cross-chain management contract in the second blockchain, so that the forwarding service device forwards the error prompt message to the cross-chain management contract in the first blockchain; the error prompt message is used to instruct the first blockchain to re-initiate the cross-chain message.

[0126] Step S104: If the cross-chain verification result indicates that the verification is successful, the transaction execution result corresponding to the cross-chain message is obtained, and the transaction execution result is stored in the second blockchain.

[0127] Specifically, if the cross-chain verification result indicates that the verification is successful, it means that the cross-chain transaction data contained in the cross-chain message has been stored in the first blockchain and the cross-chain message is complete and untampered. Then, the cross-chain message (whose essence can be the aforementioned cross-chain transaction data) can be encapsulated together with other transaction data into the second cross-chain transaction block, and the second cross-chain transaction block can be broadcast in the independent consensus network corresponding to the second blockchain, so that all consensus nodes in the independent consensus network corresponding to the second blockchain (i.e., the consensus nodes of the second blockchain) can perform consensus processing on the second cross-chain transaction block. Among them, the structure of the second cross-chain transaction block can be as mentioned above Figure 5 The corresponding block 4 in the embodiment is shown and will not be described in detail here.

[0128] In the consensus phase of the second cross-chain transaction block, the consensus nodes participating in the consensus of the second cross-chain transaction block can obtain the transaction type corresponding to the cross-chain message, call the asset processor contract matching the transaction type through the cross-chain management contract (e.g., the cross-chain bridge contract) in the second blockchain, perform transaction execution processing on the cross-chain message according to the asset processor contract, and obtain the transaction execution result corresponding to the cross-chain message. The transaction execution result can be added to the second cross-chain transaction block. If the second cross-chain transaction block reaches a consensus in the independent consensus network corresponding to the second blockchain, the second cross-chain transaction block can be stored in the second blockchain. Among them, the consensus algorithm adopted by the second cross-chain transaction block in the consensus phase can be any consensus mechanism in the current blockchain technology, and the embodiment of the present application does not limit the type of consensus algorithm adopted.

[0129] It can be understood that the cross-chain transaction data stored in the first blockchain and the cross-chain message stored in the second blockchain involved in the embodiment of the present application are essentially the same cross-chain transaction, but this cross-chain transaction requires the first blockchain and the second blockchain to be executed in coordination, that is, the first blockchain and the second blockchain collaborate to execute the cross-chain transaction. For example, the cross-chain transaction is a digital asset cross-chain transfer request, which can be used to indicate the transfer of a specific amount of digital assets from the first chain address of object S (the account address of object S on the first blockchain) to the second chain address (the account address of object S on the second blockchain). Then object S can use its own resource client to send cross-chain transaction data to the first blockchain through the cross-chain service end. At this time, the cross-chain transaction data can refer to the transaction data encapsulated by the digital asset cross-chain transfer request initiated by object S in the cross-chain service end. The cross-chain transaction can be encapsulated into the first cross-chain transaction block. When the first cross-chain transaction block is successfully stored in the first blockchain, it indicates that a specific amount of digital assets has been deducted from the address on the first chain. At this time, the first blockchain can initiate a cross-chain message through the cross-chain management contract (cross-chain bridge contract); that is, the cross-chain transaction data stored in the first blockchain can be used to indicate the deduction of a specific amount of digital assets from the address on the first chain corresponding to the object S. The cross-chain message initiated by the first blockchain can be submitted by the forwarding service device to the cross-chain management contract in the second blockchain. At this time, the cross-chain message is essentially the aforementioned cross-chain transaction data. The cross-chain message and the transaction execution result corresponding to the cross-chain message can be stored in the second blockchain; wherein, the cross-chain message stored in the second blockchain (which can also be considered as the cross-chain transaction data stored in the second blockchain) can be used to indicate the addition of a specific amount of digital assets to the address on the second chain corresponding to the object S.

[0130] In an embodiment of the present application, after obtaining the cross-chain message submitted by the forwarding service device, the consensus node of the second blockchain obtains the block Merkle information corresponding to the first blockchain from the second blockchain corresponding to the chain identifier in the cross-chain message, and obtains the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information. In other words, in the interactive communication between the first blockchain and the second blockchain, only part of the data indicated by the Merkle proof set needs to be stored on the second blockchain, and there is no need to store the full block header data in the first blockchain, which can reduce the data storage occupancy and save storage space. Furthermore, the verification capability of the block Merkle information can be relied on, that is, the validity of the cross-chain message can be verified according to the block Merkle information and the Merkle proof set, so that the cross-chain message under the block height H2 can be quickly verified, and the verification efficiency of the cross-chain message can be improved.

[0131] See also Figure 6 , Figure 6 : is a timing diagram of a data processing method based on blockchain provided by an embodiment of the present application. It can be understood that the data processing method based on blockchain can be interactively executed by the first blockchain (which can be understood as the consensus node of the first blockchain), the second blockchain (which can be understood as the consensus node of the second blockchain) and the forwarding service device; Figure 6 As shown, the blockchain-based data processing method may include at least the following steps S201 to S209:

[0132] Step S201, receiving the cross-chain transaction data sent by the cross-chain server, encapsulating the cross-chain transaction data into a first cross-chain transaction block, and if a consensus is reached on the first cross-chain transaction block, storing the first cross-chain transaction block in the first blockchain.

[0133] Among them, in the multi-chain structure of the blockchain network, if the object S wants to process cross-chain transactions in the multi-chain structure of the blockchain network, then the object S can use its own resource client to initiate cross-chain transaction data through the cross-chain server, and the cross-chain server submits the cross-chain transaction data to the first blockchain. The consensus node of the first blockchain can obtain the cross-chain transaction data sent by the cross-chain server. Furthermore, after obtaining the cross-chain transaction data, the digital signature in the cross-chain transaction data can be verified, such as the validity of the digital signature in the cross-chain transaction data can be verified according to the object public key corresponding to the object S, and the signature verification result corresponding to the cross-chain transaction data can be obtained; if the signature verification result indicates that the digital signature verification is passed, the cross-chain transaction data is encapsulated into the first cross-chain transaction block, and in the consensus stage of the first cross-chain transaction block, the transaction type corresponding to the cross-chain transaction data can be obtained, and then the asset processor contract matching the transaction type can be called through the cross-chain management contract in the first blockchain to execute the cross-chain transaction data; if the signature verification result indicates that the digital signature verification is not passed, the cross-chain transaction data can be marked as an invalid transaction, the cross-chain transaction data can be discarded, and the cross-chain server can be notified to resubmit the cross-chain transaction data.

[0134] Among them, the verification process of the digital signature in the cross-chain transaction data may include: using the object public key corresponding to the object S to decrypt the digital signature in the cross-chain transaction data, and obtain the first summary information (hash value) corresponding to the cross-chain transaction data; using the hash algorithm to perform a hash operation on the cross-chain transaction data, and the second summary information corresponding to the cross-chain transaction data can be obtained; if the first summary information is the same as the second summary information, it means that the cross-chain transaction data is a valid transaction, that is, the signature verification result corresponding to the cross-chain transaction data indicates that the verification is passed; if the first summary information is different from the second summary information, it means that the cross-chain transaction data is an invalid transaction (the cross-chain transaction data may be maliciously tampered with during the transmission process), that is, the signature verification result corresponding to the cross-chain transaction data indicates that the verification is not passed, and then the cross-chain transaction data can be discarded. It should be noted that the hash algorithm used by the consensus node of the first blockchain may refer to the hash algorithm used when the object signs the cross-chain transaction data.

[0135] It is understandable that after the consensus node of the first blockchain receives the cross-chain transaction data, it is necessary to synchronize the cross-chain transaction data in the independent consensus network corresponding to the first blockchain, such as broadcasting the cross-chain transaction data to other consensus nodes in the independent consensus network corresponding to the first blockchain. It is understandable that cross-chain transaction data may be lost during the transmission process. In order to allow the cross-chain transaction data to reach all consensus nodes in the independent consensus network corresponding to the first blockchain as much as possible, the consensus node that receives the cross-chain transaction data through broadcasting can select one or more adjacent consensus nodes according to its own network topology and network traffic strategy for relay broadcasting, which provides a basis for packaging the cross-chain transaction data into the first cross-chain transaction block during the consensus process.

[0136] Furthermore, the consensus node of the first blockchain can package the transactions in the transaction pool to generate a first cross-chain transaction block (assuming that the first cross-chain transaction block contains cross-chain transaction data). During the consensus process of the first cross-chain transaction block, the consensus node can execute all transactions in the first cross-chain transaction block, including the cross-chain transaction data contained in the block. After the first cross-chain transaction block reaches a consensus in the independent consensus network, the first cross-chain transaction block can be stored in the first blockchain.

[0137] Step S202: Initiate a cross-chain message corresponding to the cross-chain transaction data through the cross-chain management contract in the first blockchain.

[0138] Specifically, when the first cross-chain transaction block is successfully stored in the first blockchain, a cross-chain message corresponding to the cross-chain transaction data can be initiated through the cross-chain management contract in the first blockchain, and the cross-chain message can be submitted to the second blockchain by the forwarding service device.

[0139] Step S203, obtaining a cross-chain message initiated by the first blockchain, and obtaining the block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain.

[0140] Specifically, the forwarding service device can obtain the contract status corresponding to the cross-chain management contract in the first blockchain. If the contract status is a transaction pending forwarding status (the transaction pending forwarding status is used to indicate that a new cross-chain message is initiated in the cross-chain bridge contract in the first blockchain), then obtain the cross-chain message initiated by the cross-chain management contract in the first blockchain; determine in the first blockchain the first cross-chain transaction block to which the cross-chain transaction data indicated by the cross-chain message belongs (i.e., the block in the first blockchain that stores the cross-chain transaction data), and obtain the block height H2 of the first cross-chain transaction block in the first blockchain, that is, the block height of the first cross-chain transaction block in the first blockchain can be recorded as H2.

[0141] It can be understood that in the multi-chain architecture of the blockchain network, the forwarding service device can be used to forward cross-chain messages between different blockchains. The forwarding service device can simultaneously detect the contract status of the cross-chain management contracts in multiple blockchains. If a cross-chain message is detected in the cross-chain management contract of any blockchain, the cross-chain message can be forwarded to the blockchain that receives the cross-chain message.

[0142] Step S204: If it is detected in the second blockchain corresponding to the chain identifier that the verifiable height H1 corresponding to the first blockchain is greater than or equal to the block height H2, the cross-chain message is forwarded.

[0143] Specifically, after the forwarding service device obtains the cross-chain message from the cross-chain management contract of the first blockchain, before forwarding the cross-chain message, the blockchain (i.e., the second blockchain) used to receive the cross-chain message can be determined according to the chain identifier carried by the cross-chain message, and then the verifiable height H1 corresponding to the first blockchain can be obtained in the chain verification contract deployed by the second blockchain (specifically, the first blockchain verification contract), that is, the block height corresponding to the block Merkel information (such as MMR root information) stored in the contract verified by the first blockchain can be called the verifiable height H1. If it is detected in the second blockchain corresponding to the chain identifier that the verifiable height H1 corresponding to the first blockchain is greater than or equal to the block height H2, the cross-chain message can be forwarded to the second blockchain.

[0144] Optionally, if the verifiable height H1 is less than the block height H2, a height update prompt message corresponding to the first blockchain is generated, and the height update prompt message is sent to a trusted oracle device (for example, it can be a trusted MMR root oracle, or it can be a TEE trusted oracle), so that the trusted oracle device submits the block Merkel information corresponding to the maximum block height in the first blockchain to the chain verification contract in the second blockchain (specifically, it can be the first blockchain verification contract) according to the height update prompt message; wherein, the block Merkel information corresponding to the maximum block height is used to overwrite the block Merkel information and the verifiable height H1 stored in the chain verification contract deployed by the second blockchain. If the updated verifiable height H1 is still less than the block height H2 where the cross-chain message is located in the first blockchain, the forwarding service device does not need to forward the cross-chain message, that is, the cross-chain message submission fails.

[0145] Step S205, obtain the chain identifier carried by the cross-chain message, obtain the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and obtain the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information.

[0146] Among them, the consensus node of the second blockchain can obtain the cross-chain message initiated by the cross-chain management contract in the first blockchain through the cross-chain management contract deployed in the second blockchain, and then call the first blockchain verification contract in the second blockchain through the cross-chain management contract in the first blockchain, and verify the validity of the cross-chain message through the block Merkle information (MMR root information) in the first blockchain verification contract. Among them, the specific implementation process of step S205 can be referred to the aforementioned Figure 3 The relevant descriptions in step S101 and step S102 of the corresponding embodiment are not repeated here.

[0147] Step S206, perform a hash operation on the Merkle proof set to obtain the first candidate Merkle information corresponding to the first cross-chain transaction block, and obtain the block verification result corresponding to the first cross-chain transaction block by comparing the block Merkle information with the first candidate Merkle information.

[0148] Specifically, the consensus node of the second blockchain can perform a hash operation on the Merkle proof set (specifically, the MMR proof set) to obtain the first candidate Merkle information corresponding to the first cross-chain transaction block. The first candidate Merkle information at this time can refer to the block Merkle information obtained by re-hashing the Merkle proof set (that is, the recalculated MMR root information, the first candidate Merkle information here can be recorded as MMRR'). If the block Merkle information (that is, the MMR root information stored in the first blockchain verification contract, which can be recorded as MMRR) is consistent with the first candidate Merkle information, that is, MMRR'=MMRR, then the block verification result corresponding to the first cross-chain transaction block is determined to be a successful verification result, indicating that the data in the first cross-chain transaction block is authentic and has not been tampered with; if the block Merkle information is inconsistent with the first candidate Merkle information, that is, MMRR'≠MMRR, then the block verification result corresponding to the first cross-chain transaction block is determined to be a failed verification result, based on the irreversibility of the hash operation, indicating that the data in the first cross-chain transaction block has been maliciously tampered with. In an embodiment of the present application, the data stored in the leaf node (first cross-chain transaction block) in the MMR tree (block Merkle tree) can be verified to ensure that the data has not been tampered with and is authentic. The process here can be called an MMR certification process.

[0149] See also Figure 7 , Figure 7 This is a block data verification schematic diagram based on the Merkel Mountains provided in an embodiment of the present application; Figure 7 The leaf node B8 shown in the figure (the leaf node B8 here can be regarded as the first cross-chain transaction block mentioned above) is used as an example to describe the MMR (Merkle Mountain Root) certification process. Figure 7The MMR tree shown may include three Merkle subtrees, namely Merkle subtree 30a (a perfect binary subtree), Merkle subtree 30b (a perfect binary subtree), and a Merkle subtree containing only leaf node B12. Leaf nodes B0 to B12 in the MMR tree may be represented as block headers of all blocks contained in the first blockchain.

[0150] If you want to prove whether the leaf node B8 belongs to the MMR tree, you can get the Merkle proof set of the leaf node B8 in the MMR tree. The Merkle proof set can be the hash values ​​of the leaf node B9, leaf node B12, intermediate node Hash(10&11), and intermediate node Hash(((0&1)&(2&3))&((4&5)&(6&7))) in the MMR tree; where Hash() means taking the hash value. The proof process of the leaf node B8 may include:

[0151] ① Calculate the hash value H'(8) of leaf node B8, where H'(8) = Hash(B8), and obtain the hash value H(9) of leaf node B9 and the hash value H(12) of leaf node B12 in the Merkle Mountain path (the aforementioned block path information), where H(9) = Hash(B9) and H(12) = Hash(B12).

[0152] ② Obtain a right subroot H(10&11) in the Merkle subtree 30b where the leaf node B8 in the MMR tree is located, where H(10&11)=Hash(H(10)&H(11)).

[0153] ③ Perform a hash operation on the hash value H'(8) of the leaf node B8 and the hash value H(9) of the leaf node B9 to obtain H'(8&9)=Hash(H'(8)&H(9)).

[0154] ④ Perform a hash operation on H'(8&9) calculated in step ③ and H(10&11) obtained in step ② to obtain H'(H'(8&9)&H(10&11)), H'(H'(8&9)&H(10&11))=Hash(H'(8&9)&H(10&11)).

[0155] ⑤In Figure 7 The subtree root of the Merkle subtree 30a is obtained from the MMR tree shown. The subtree root at this time can be expressed as H(((0&1)&(2&3))&((4&5)&(6&7))).

[0156] ⑥Hash H(12), H(((0&1)&(2&3))&((4&5)&(6&7))), and H'(H'(8&9)&H(10&11)) to obtain MMRR'(the first candidate Merkle information); where MMRR'=Hash(H(((0&1)&(2&3))&((4&5)&(6&7)))&H'(H'(8&9)&H(10&11))&H(12)).

[0157] ⑦ Compare the calculated MMRR' with the MMRR (block Merkle information) stored in the first blockchain verification contract deployed on the second blockchain. If MMRR'=MMRR, it proves that the data of leaf node B8 has not been tampered with, that is, the verification of leaf node B8 is successful.

[0158] It should be noted that Figure 7 H'(8), H'(8&9) and H'(H'(8&9)&H(10&11)) shown are all the results obtained by re-hashing the first blockchain verification contract in the second blockchain during the process of verifying the leaf node B8; Figure 7 H(9), H(12), H(((0&1)&(2&3))&((4&5)&(6&7))) etc. shown are directly obtained node hash values ​​in the MMR tree, and no hash operation is required. It can be seen that the first blockchain verification contract in the second blockchain only needs to store H(9), H(12), H(10&11) and H(((0&1)&(2&3))&((4&5)&(6&7))) to realize the verification process of the data stored in the leaf node B8, which can save the storage space of the first blockchain verification contract in the second blockchain and reduce the data storage occupancy.

[0159] Step S207, obtaining transaction Merkel information in the block header of the first cross-chain transaction block, and obtaining transaction path information of the cross-chain transaction data in the transaction Merkel tree corresponding to the transaction Merkel information.

[0160] Step S208: Verify the validity of the cross-chain transaction data based on the transaction path information and the transaction Merkel information to obtain a transaction verification result corresponding to the cross-chain transaction data.

[0161] For details, see Figure 8 , Figure 8 Schematic diagram of a cross-chain message verification process provided by an embodiment of the present application. Figure 8As shown, the verification process of the cross-chain message may include the data authenticity verification in the first cross-chain transaction block (which may be referred to as block verification), and the storage location verification of the cross-chain transaction data indicated by the cross-chain message (which may be referred to as transaction verification). Among them, the data authenticity verification in the first cross-chain transaction block can be understood as verifying whether the data stored in the first cross-chain transaction block is authentic and has not been tampered with (which can be implemented by the aforementioned steps S205 and S206), and specifically can be performed in the form of log2 (#blocks.) Merkle proof, where blocks refers to blocks in the first blockchain; the storage location verification of the cross-chain transaction data can be understood as verifying whether the cross-chain transaction data is stored in the first blockchain, and specifically can be performed in the form of log2 (#trans.) Merkle proof, where trans refers to the transaction data stored in the first cross-chain transaction block. The embodiment of the present application describes the verification process of cross-chain transaction data through steps S207 and S208.

[0162] The transaction Merkle information can be obtained in the block header of the first cross-chain transaction block through the first blockchain verification contract in the second blockchain (for example, Figure 5 The Merkle tree root in the block header of block 4 in the corresponding embodiment) can obtain the transaction Merkle tree corresponding to the cross-chain transaction data in the transaction Merkle information (for example, Figure 5 The transaction path information in the Merkle tree corresponding to the Merkle tree root in block 4 shown in the figure) is such as the Merkle path information of the cross-chain transaction data in the Merkle tree. By performing a hash operation on the transaction path information, the second candidate Merkle information corresponding to the cross-chain transaction data is obtained (which can be the Merkle tree root obtained by re-hashing); wherein, the second candidate Merkle information can be obtained by performing multiple hash operations on the node information (node ​​hash values) of different levels contained in the transaction path information, such as performing a hash operation on the node information of the same level, and continuing to perform a hash operation on the node information of the previous level in turn (such as the process from π1 to π2), and finally calculating the second candidate Merkle information. If the transaction Merkel information is consistent with the second candidate Merkel information, that is, the Merkel tree root in the block header of the first cross-chain transaction block is the same as the Merkel tree root obtained by rehashing the second blockchain, then the transaction verification result corresponding to the cross-chain transaction data is determined to be a successful verification result, indicating that the cross-chain transaction data is stored in the first cross-chain transaction block of the first blockchain; if the transaction Merkel information is inconsistent with the second candidate Merkel information, then the transaction verification result corresponding to the cross-chain transaction data is determined to be a failed verification result, indicating that the cross-chain transaction data is not stored in the first blockchain.

[0163] It is understandable that if both the block verification result and the transaction verification result are successful verification results, it indicates that the cross-chain message verification is successful (transaction verification is successful), that is, the cross-chain transaction data indicated by the cross-chain message is stored in the first blockchain and the cross-chain transaction data is intact and has not been tampered with. If either the block verification result or the transaction verification result is a verification failure result, or both are verification failure results, it indicates that the cross-chain message verification has failed, that is, the cross-chain transaction data indicated by the cross-chain message is not stored in the first blockchain or the cross-chain transaction data has been maliciously tampered with.

[0164] Step S209: If both the block verification result and the transaction verification result are successful verification results, it is determined that the cross-chain verification result corresponding to the cross-chain message indicates successful verification, the transaction execution result corresponding to the cross-chain message is obtained, and the transaction execution result is stored in the second blockchain.

[0165] The specific implementation process of step S209 can be found in Figure 3 Step S104 in the corresponding embodiment will not be described in detail here.

[0166] See also Fig. 9 , Fig. 9 This is a schematic diagram of the overall structure of a cross-chain technology between different blockchains provided in the embodiment of this application. Fig. 9 As shown, the overall structure of the cross-chain technology proposed in the embodiment of the present application may include but is not limited to: a cross-chain service end, a cross-chain message forwarding service (forwarding service device), a trusted Merkle Mountain root oracle (trusted oracle device), and multiple blockchains for cross-chain communication (such as Fig. 9 Blockchain A and blockchain B shown).

[0167] Cross-chain service end: may include a cross-chain service front end and a cross-chain service back end. The cross-chain service front end may include but is not limited to web pages, applications, subprograms embedded in applications (e.g., applet), etc. The cross-chain service front end may be responsible for interacting with objects, and objects may use their own resource clients to initiate cross-chain requests through the cross-chain service front end, which may encapsulate the cross-chain request as cross-chain transaction data; wherein the above cross-chain request may include but is not limited to asset custody authorization and cross-chain transfer requests, etc. After the cross-chain task is completed, the task completion status and the relevant data of the cross-chain task may be displayed in the cross-chain service front end, that is, an extraction request may be initiated to the blockchain to obtain the cross-chain task completion status and its relevant data. The cross-chain service back end may be a background service, mainly used to provide data and blockchain transaction function support for the cross-chain service front end. It is understandable that the cross-chain service end may register its identity in multiple blockchains to obtain authorization from multiple blockchains, that is, obtain the authority to submit transaction data to multiple blockchains.

[0168] Cross-chain message forwarding service: may include but is not limited to multi-chain interface detection, cross-chain message forwarding, cross-chain historical tasks and status management services. The multi-chain interface detection service can be used to detect the cross-chain messages issued by the cross-chain bridge contract (cross-chain management contract) on each blockchain; after the cross-chain message is detected by the multi-chain interface detection service, the cross-chain message forwarding service can be used to check the cross-chain message and forward it to the cross-chain bridge contract of the blockchain used to execute the cross-chain message (for ease of understanding, the blockchain that issues the cross-chain message can be called the original chain, and the blockchain that executes the cross-chain message can be called the target chain, for example, the aforementioned first blockchain can be called the original chain, and the second blockchain can be called the target chain); the cross-chain historical tasks and status management service can be used to manage the cross-chain tasks and their task status that have been forwarded by the cross-chain message forwarding service. It should be noted that the cross-chain message will be verified by the MMR technology in the chain verification contract on the blockchain, so the cross-chain message forwarding service does not need to guarantee the correctness of the cross-chain message it forwards, and only needs to detect the cross-chain message on the original chain and submit it to the target chain as it is. In other words, the cross-chain message forwarding service does not need to perform identity authentication in multiple blockchains, that is, there is no need to set trust in the cross-chain message forwarding service in the on-chain contract of the blockchain. It can be understood that before forwarding the cross-chain message it detects, the cross-chain message forwarding service can obtain the block height H2 of the block to which the cross-chain message belongs in the original chain, and then detect whether there is MMR root information greater than or equal to the block height H2 on the target chain. The block height of the MMR root information stored on the target chain can be called the verifiable height, recorded as H1; if the verifiable height H1 is less than the block height H2, the trusted MMR root oracle service is triggered to submit the MMR root information of the latest height (maximum block height) to the target chain. If the verifiable height H1 on the target chain becomes greater than or equal to the block height H2 after the submission is completed, the cross-chain message forwarding service will forward the cross-chain message to the target chain at this time; if the verifiable height H1 on the target chain is still less than the block height H2 after the submission is completed, the cross-chain message submission fails.

[0169] Trusted MMR root oracle: The trusted MMR root oracle can run in a trusted execution environment (TEE), and can also be called a TEE trusted oracle. The trusted MMR root oracle can include but is not limited to multi-chain detection and verification, MMR root submission and other services; the multi-chain detection and verification service can be used to detect the ledgers of each blockchain and verify the detected ledgers; the MMR root submission service can submit the MMR root information corresponding to the maximum block height on the original chain to the cross-chain bridge contract in the target chain after receiving the trigger prompt of the cross-chain message forwarding service. Please refer to Fig.10 , Fig.10 is a schematic diagram of the structure of a trusted prediction device provided in an embodiment of the present application; Fig.10As shown, the multi-chain detection and verification service in the trusted MMR root oracle can include multiple detection and verification services. One blockchain corresponds to a detection and verification service running in the TEE. Each detection and verification service can detect the ledger on a blockchain and verify the detected ledger by synchronizing each block to the local verification method. At the same time, the MMR root information of each block height can be stored. For example, the trusted MMR root oracle can include the blockchain A ledger detection and verification service (used to detect and verify the ledger of blockchain A), the blockchain B ledger detection and verification service (used to detect and verify the ledger of blockchain B), and the blockchain C ledger detection and verification service (used to detect and verify the ledger of blockchain C). The MMR root submission service can be connected to each detection and verification service. For example, the MMR root submission service can be connected to the blockchain A ledger detection and verification service, the blockchain B ledger detection and verification service, and the blockchain C ledger detection and verification service at the same time. When the cross-chain message forwarding service triggers the MMR root submission service to submit the MMR root information of blockchain A to blockchain B, the MMR root submission service can obtain the MMR root information corresponding to the latest height from the blockchain A ledger detection and verification service, and submit it to the blockchain A verification contract on blockchain B.

[0170] Cross-chain bridge contract: The cross-chain bridge contract is the submission entry for cross-chain transactions (cross-chain messages). The cross-chain bridge contract can include but is not limited to the following functions:

[0171] ① Manage cross-chain relays: manage the addition, deletion, modification, and query of relay objects to which cross-chain messages can be forwarded. The relay objects managed here (for example, forwarding service devices) only forward cross-chain messages and do not include confirmation of cross-chain messages.

[0172] ② Manage cross-chain transactions: The cross-chain bridge contract in the original chain can record the submission information of each cross-chain transaction (cross-chain message), and the cross-chain bridge contract in the target chain can record the execution status of each cross-chain transaction after submission and its corresponding state changes (for example, inactivated-activated-passed-executed-cancelled, etc.); for example, when the cross-chain transaction is a cross-chain transfer message, the cross-chain bridge contract in the original chain can record the object submitting the cross-chain transfer, the amount of data transferred, the type of digital assets, the chain identification (ID) of the target chain, the object address for receiving digital assets in the target chain, the transaction sequence number, etc. It should be noted that if the cross-chain bridge contract in the target chain receives a cross-chain message from blockchain A submitted by the forwarding service device, then the blockchain A verification contract can be called through the cross-chain management contract, and based on the MMR verification technology in the blockchain A verification contract, it can be determined whether the cross-chain message from blockchain A is stored in blockchain A and the cross-chain message is complete and untampered.

[0173] ③After the cross-chain message is completed, the cross-chain bridge contract can be responsible for calling the message processors corresponding to various cross-chain transaction types. For example, a cross-chain transaction of the Token type is submitted to the asset processor contract, which can then execute the cross-chain transaction. Specifically, the asset contract where the digital asset corresponding to the cross-chain transaction is located can be operated to complete the cross-chain execution.

[0174] Chain verification contract: Fig. 9 The blockchain B verification contract in blockchain A, the blockchain A verification contract in blockchain B, etc., a blockchain can include multiple chain verification contracts, and one chain verification contract corresponds to one blockchain. The chain verification contract can include but is not limited to the following functions:

[0175] ① Used to receive the latest MMR root information on each blockchain submitted by the MMR root submission service in the trusted MMR root oracle, and update the corresponding verifiable height.

[0176] ② It is used to receive and verify the cross-chain messages transmitted by the cross-chain bridge contract. For each cross-chain message, the chain verification contract can obtain the transaction information (cross-chain transaction data) corresponding to the cross-chain message, the Merkel path information (transaction path information) of the cross-chain transaction data, the block header information of the block where the cross-chain transaction data is located (the first cross-chain transaction block), and the Merkel path information (block path information) of the MMR tree corresponding to the block header of the block where the cross-chain transaction data is located. Based on the above information and the MMR root information stored in the chain verification contract, the correctness verification result (cross-chain verification result) of the cross-chain message can be obtained through the calculation of the Merkel tree. The verification principle of MMR technology can be found in the above Figure 6 The descriptions of steps S205 to S208 of the corresponding embodiment will not be repeated here; verifying cross-chain messages through MMR technology can improve the verification efficiency of cross-chain messages.

[0177] See also Fig.11 , Fig.11 This is a system architecture diagram of a tax blockchain system provided by an embodiment of the present application. Fig.11 As shown in FIG. 1 , the business network, routing proxy network and core consensus network in the embodiment of the present application constitute the entire complete blockchain business system. Among them, the number of blockchains maintained by the core consensus network can be multiple, which can be as follows: Fig.11 The core chain 1 and core chain 2 shown in the figure, where core chain 1 and core chain 2 can be blockchains containing full data. It should be noted that Fig.11 The core consensus network shown may include multiple independent consensus networks. Specifically, a core chain may be maintained for an independent consensus network. The consensus nodes in the independent consensus network may be responsible for consensus and recording business transaction data in the corresponding core chain. Fig.11 The business network shown may include multiple independent business networks, specifically one independent business network corresponds to one core chain, and the business nodes in the independent business network are responsible for the transaction data for tax business on the chain and the data clearing associated with the tax business (for example, transaction clearing). Among them, transaction clearing means that after the consensus node receives the request for synchronization of transactions from the business node, the business node synchronizes the transaction data that the business node has the authority to read to the business node. In short, a core chain can correspond to an independent consensus network and an independent business network, and different core chains can correspond to different independent consensus networks and independent business networks.

[0178] It is understandable that when blockchain is used in some scenarios of management agencies (for example, tax systems) or commercial organizations, in order to improve the confidentiality and security of data, when personal privacy and other related data are involved in the blockchain system, the layered blockchain structure of "business network-core consensus network" in the embodiment of this application can be adopted; in other words, the layered blockchain structure of "business network-core consensus network" can be formed between the independent consensus network and the independent business network corresponding to each core chain. Among them, the system architecture diagram can be applied to multiple transaction businesses associated with tax business, such as invoice business, loss business, legal person business, credit business and tax refund business, etc. One transaction business can correspond to one core chain, so that different transaction businesses can be effectively distinguished to maintain the specificity of the relevant data of a single transaction business for on-chain storage.

[0179] Since the entire tax business will involve regulatory agencies, invoicing parties, reimbursement parties and tax payers, etc. Fig.11 The business nodes in the business network shown can be business terminal devices used by business objects, or can have a network connection relationship with terminal devices used by business objects. The business objects here can include tax bureau objects, enterprise objects, and consumer objects, etc. Among them, the tax bureau object can refer to the regulatory agency in the regulatory network (for example, the computer equipment corresponding to the provincial, municipal, district, etc. tax bureaus), the enterprise object can be the invoicing service provider, reimbursement service provider or retail enterprise in the public cloud (for example, KA enterprise, i.e. large retail customers and key retail customer enterprises), etc., and the consumer object can be the payment service provider, circulation service provider or retail enterprise in the private cloud, etc.

[0180] Among them, the proxy nodes in the routing proxy network can be used to isolate the business network and the core consensus network; it should be understood that the independent consensus network and independent business network corresponding to each core chain can be isolated through the proxy nodes in the routing proxy network. The proxy nodes in the routing proxy network can have point-to-point services (i.e., P2P services), routing services, certificate caches, authentication services, etc. Among them, the routing service is a basic function of the blockchain node and can be used for communication between blockchain nodes to isolate the business network and the core consensus network. The certificate cache is used to cache the digital certificates of each blockchain node. The digital certificate is an identity certificate of a public key holder in the public key certificate system (PKI); the public key certificate system (PKI) here can include public and private key passwords, x509 certificates, CA certificate issuance centers, etc. The authentication service can be used to authenticate the identity of the business nodes in the business network.

[0181] It can be understood that in the embodiment of the present application, the proxy node can be used to forward the business transaction data (for example, specifically cross-chain transaction data, in which case the business node sending the business transaction data can be a cross-chain service end) sent by the business node to the consensus node of the core chain 1 (in which case the core chain 1 can be the aforementioned first blockchain) so that the consensus node can chain the cross-chain transaction data; when the cross-chain transaction data is stored on the core chain 1, the cross-chain bridge contract deployed in the core chain 1 can initiate a cross-chain message to the consensus node of the core chain 2 (in which case the core chain 2 can be the aforementioned second blockchain). After the forwarding service device detects the cross-chain message initiated by the cross-chain bridge contract in the core chain 1, the cross-chain message can be submitted to the cross-chain bridge contract deployed in the core chain 2. The consensus node of the core chain 2 obtains the cross-chain message sent by the consensus node of the core chain 1 through the cross-chain bridge contract, and then can call the core chain 1 verification contract deployed in the core chain 2, and judges whether the cross-chain transaction data indicated by the cross-chain message exists on the core chain 1 and the cross-chain message is complete and untampered according to the MMR root of the latest block height stored in the core chain 1 verification contract. After completing the verification process of the cross-chain message, the consensus node of core chain 2 can call the asset processor contract corresponding to the cross-chain message, and the asset processor contract will execute the cross-chain message, and store the cross-chain message and the transaction execution result of the cross-chain message to core chain 2. It should be understood that the proxy node can also be used to forward the transaction execution result (i.e., the execution result of the cross-chain message) sent by the consensus node of core chain 2 to the business node (such as the cross-chain server). This means that the proxy node can be used to provide communication services to the business nodes in the business network and the consensus nodes in the core consensus network; the forwarding service device can be used to provide cross-chain message forwarding services to different core chains.

[0182] like Fig.11As shown in the figure, the consensus nodes (i.e., accounting nodes) in the core consensus network can be trusted nodes in the tax-specific network, and can determine their own consensus responsibilities by calling permission contracts (e.g., smart contracts). The permission contracts here also store the circulation logic of the entire life cycle of electronic bills, such as the bill status of electronic bills, circulation process, data access rights, electronic bill application conditions, electronic bill issuance conditions, and cross-chain transactions. For example, after the consensus node in the core consensus network receives the business transaction data forwarded by the proxy node, it can store the business transaction data in Fig.11 The cache shown (i.e., the transaction pool corresponding to the consensus node in the core consensus network) can then encapsulate the cached business transaction data into a new block. After the new block reaches a consensus in the independent consensus network corresponding to the core chain 1, the block can be stored in the core chain 1, that is, the aforementioned business transaction data is successfully stored in the core chain 1. It can be understood that in order to achieve interaction and communication between different core chains, a contract set can be deployed in multiple core chains in the core consensus network. The contract set can refer to a set of smart contracts associated with multiple cross-chain transactions deployed on each core chain, which may include but is not limited to cross-chain bridge contracts, asset processor contracts, verification contracts for each blockchain (for example, core chain 1 verification contract, core chain 2 verification contract), cross-chain application contracts, cross-chain asset contracts, etc. Of course, smart contracts associated with other transactions (non-cross-chain transactions) can also be deployed in each core chain, such as on-chain asset transfer contracts, data storage contracts, etc. The embodiment of this application does not limit the type of smart contracts deployed in the core chain.

[0183] It is understandable that the smart contract involved in the embodiment of the present application can be a piece of business code, which can be run at the bottom of the blockchain. After it is successfully deployed to the blockchain, when the transaction data that needs to call the smart contract is subsequently obtained, the consensus nodes participating in the consensus in the blockchain network can execute the business code in the smart contract, and each consensus node can get the same result. In other words, the smart contract can be a computer program code, and the developer can use the smart contract high-level language to write it. The contract written in the high-level language can be compiled into the bytecode in the virtual machine of the blockchain node through the compiler, and the virtual machine can be used to interpret and execute the bytecode in the smart contract. The smart contract high-level language may include but is not limited to Solidity (a smart contract programming language), Serpent (a smart contract programming language), LLL (a smart contract programming language), such as developers can use Solidity to write smart contracts, and use the compiler to compile the smart contract written in Solidity into virtual machine bytecode, and then compile it into virtual machine bytecode and deploy it in the blockchain. It should be noted that the object of submitting the smart contract to the blockchain network can be any object that completes identity registration in the cross-chain server (or other decentralized applications).

[0184] In an embodiment of the present application, after obtaining the cross-chain message submitted by the forwarding service device, the consensus node of the second blockchain obtains the block Merkle information corresponding to the first blockchain from the second blockchain corresponding to the chain identifier in the cross-chain message, and obtains the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information. In other words, in the interactive communication between the first blockchain and the second blockchain, only part of the data indicated by the Merkle proof set needs to be stored on the second blockchain, and there is no need to store the full block header data in the first blockchain, which can reduce the data storage occupancy and save storage space. Furthermore, the verification capability of the block Merkle information can be relied on, that is, the validity of the cross-chain message can be verified according to the block Merkle information and the Merkle proof set, so that the cross-chain message under the block height H2 can be quickly verified, and the verification efficiency of the cross-chain message can be improved.

[0185] It is understandable that in the specific implementation of this application, cross-chain messages may involve users' account addresses, assets and other personal information. When the above embodiments of this application are applied to specific products or technologies, the user's permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0186] See also Fig.12 , Fig.12 This is a schematic diagram of a data processing device based on blockchain provided in an embodiment of the present application. Figure 1It can be understood that the blockchain-based data processing device 1 can be applied to any consensus node on the aforementioned second blockchain, such as Figure 1 Any consensus node in the independent consensus network corresponding to the second blockchain included in the core consensus network shown; Fig.12 As shown, the blockchain-based data processing device 1 may include: a cross-chain message acquisition unit 11, a proof set acquisition unit 12, a cross-chain message verification unit 13, and a cross-chain message execution unit 14;

[0187] The cross-chain message acquisition unit 11 is used to acquire the cross-chain message submitted by the forwarding service device and acquire the chain identifier carried by the cross-chain message; the cross-chain message is associated with the cross-chain transaction data stored in the first blockchain;

[0188] The proof set acquisition unit 12 is used to acquire the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and acquire the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information; the verifiable height H1 of the block Merkle information in the first blockchain is greater than or equal to the block height H2 of the cross-chain message in the first blockchain, and the block Merkle tree includes multiple Merkle subtrees;

[0189] The cross-chain message verification unit 13 is used to verify the validity of the cross-chain message according to the Merkel proof set and the block Merkel information, and obtain the cross-chain verification result corresponding to the cross-chain message;

[0190] The cross-chain message execution unit 14 is used to obtain the transaction execution result corresponding to the cross-chain message if the cross-chain verification result indicates that the verification is successful, and store the transaction execution result in the second blockchain.

[0191] In one or more embodiments, the proof set acquisition unit 12 acquires the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and acquires the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information, including:

[0192] In the chain verification contract deployed by the second blockchain corresponding to the chain identifier, obtaining the block Merkle information corresponding to the first blockchain;

[0193] Determine in the first blockchain the first cross-chain transaction block to which the cross-chain transaction data indicated by the cross-chain message belongs, and obtain block path information of the first cross-chain transaction block in the block Merkle tree corresponding to the block Merkle information;

[0194] Get the subtree root information corresponding to multiple Merkle subtrees contained in the block Merkle tree, and combine the subtree root information and the node information contained in the block path information into a Merkle proof set corresponding to the cross-chain message.

[0195] In one or more embodiments, the proof set acquisition unit 12 acquires the block path information of the first cross-chain transaction block in the block Merkle tree corresponding to the block Merkle information, including:

[0196] Obtain the block hash value corresponding to the first cross-chain transaction block, and determine the Merkle subtree to which the block hash value belongs in the block Merkle tree corresponding to the block Merkle information;

[0197] Taking the block hash value as the starting node information, traverse the hierarchical node information in the Merkle subtree to which the block hash value belongs until traversing to the subtree root information in the Merkle subtree to which the block hash value belongs, and determine the block path information corresponding to the first cross-chain transaction block according to the traversed hierarchical node information.

[0198] In one or more embodiments, the cross-chain message verification unit 13 verifies the validity of the cross-chain message according to the Merkle proof set and the block Merkle information, and obtains the cross-chain verification result corresponding to the cross-chain message, including:

[0199] Perform hash operation on the Merkle proof set to obtain the first candidate Merkle information corresponding to the first cross-chain transaction block, and obtain the block verification result corresponding to the first cross-chain transaction block by comparing the block Merkle information with the first candidate Merkle information;

[0200] Obtain transaction Merkle information in the block header of the first cross-chain transaction block, and obtain transaction path information of the cross-chain transaction data in the transaction Merkle tree corresponding to the transaction Merkle information; the transaction Merkle tree is determined by the transaction data included in the first cross-chain transaction block;

[0201] According to the transaction path information and transaction Merkel information, the validity of the cross-chain transaction data is verified to obtain the transaction verification result corresponding to the cross-chain transaction data;

[0202] If both the block verification result and the transaction verification result are successful verification results, then the cross-chain verification result corresponding to the cross-chain message is determined to indicate successful verification.

[0203] In one or more embodiments, the cross-chain message verification unit 13 obtains a block verification result corresponding to the first cross-chain transaction block by comparing the block Merkle information with the first candidate Merkle information, including:

[0204] If the block Merkle information is consistent with the first candidate Merkle information, the block verification result corresponding to the first cross-chain transaction block is determined to be a successful verification result;

[0205] If the block Merkle information is inconsistent with the first candidate Merkle information, the block verification result corresponding to the first cross-chain transaction block is determined to be a verification failure result.

[0206] In one or more embodiments, the cross-chain message verification unit 13 verifies the validity of the cross-chain transaction data according to the transaction path information and the transaction Merkel information, and obtains the transaction verification result corresponding to the cross-chain transaction data, including:

[0207] Perform hash operation on the transaction path information to obtain the second candidate Merkle information corresponding to the cross-chain transaction data;

[0208] If the transaction Merkle information is consistent with the second candidate Merkle information, the transaction verification result corresponding to the cross-chain transaction data is determined to be a successful verification result;

[0209] If the transaction Merkle information is inconsistent with the second candidate Merkle information, the transaction verification result corresponding to the cross-chain transaction data is determined to be a verification failure result.

[0210] In one or more embodiments, the cross-chain message execution unit 14 is used to obtain the transaction execution result corresponding to the cross-chain message if the cross-chain verification result indicates that the verification is successful, and store the transaction execution result in the second blockchain, including:

[0211] If the cross-chain verification result indicates that the verification is successful, the cross-chain message is encapsulated into the second cross-chain transaction block, and in the consensus phase of the second cross-chain transaction block, the transaction type corresponding to the cross-chain message is obtained;

[0212] The cross-chain management contract in the second blockchain calls the asset processor contract that matches the transaction type, performs transaction execution processing on the cross-chain message according to the asset processor contract, and obtains the transaction execution result corresponding to the cross-chain message;

[0213] The transaction execution result is added to the second cross-chain transaction block. If the second cross-chain transaction block reaches a consensus, the second cross-chain transaction block is stored in the second blockchain.

[0214] In one or more embodiments, the blockchain-based data processing device 1 further includes: a cross-chain message verification failure unit 15;

[0215] The cross-chain message verification failure unit 15 is used to generate error prompt information corresponding to the cross-chain message if the cross-chain verification result indicates verification failure, and send the error prompt information to the forwarding service device through the cross-chain management contract in the second blockchain, so that the forwarding service device forwards the error prompt information to the cross-chain management contract in the first blockchain; the error prompt information is used to instruct the first blockchain to re-initiate the cross-chain message.

[0216] According to an embodiment of the present application, the steps involved in the blockchain-based data processing method shown above can be Fig.12 The data processing device 1 shown in the figure is based on the blockchain and is executed by each unit. For example, Figure 3 Step S101 shown can be performed by Fig.12 The cross-chain message acquisition unit 11 shown is used to execute, Figure 3 Step S102 shown can be performed by Fig.12 The proof set acquisition unit 12 shown is executed, Figure 3 Step S103 shown can be performed by Fig.12 The cross-chain message verification unit 13 shown is used to execute, Figure 3 Step S104 shown can be performed by Fig.12 The cross-chain message execution unit 14 shown is used to execute, etc.

[0217] According to one embodiment of the present application, Fig.12 The various units in the blockchain-based data processing device 1 shown can be combined into one or several units separately or in whole, or one (some) of the units can be further divided into at least two functionally smaller sub-units, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the functions of one unit can also be implemented by at least two units, or the functions of at least two units can be implemented by one unit. In other embodiments of the present application, the blockchain-based data processing device 1 may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by at least two units in collaboration.

[0218] In the embodiment of the present application, after obtaining the cross-chain message submitted by the forwarding service device, the consensus node of the second blockchain obtains the block Merkel information corresponding to the first blockchain from the second blockchain corresponding to the chain identifier in the cross-chain message, and obtains the Merkel proof set corresponding to the cross-chain message in the block Merkel tree corresponding to the block Merkel information. In other words, in the interactive communication between the first blockchain and the second blockchain, only part of the data indicated by the Merkel proof set needs to be stored on the second blockchain, and the full block header data in the first blockchain does not need to be stored, which can reduce the data storage occupancy and save storage space. Further, the verification capability of the block Merkel information can be relied on, that is, the validity of the cross-chain message can be verified according to the block Merkel information and the Merkel proof set, and the cross-chain message under the block height H2 can be quickly verified, which can improve the verification efficiency of the cross-chain message. In addition, in order to ensure the correctness of the block Merkel information (MMR root information), the TEE trusted oracle is introduced to maintain and submit the block Merkel information, which can improve the accuracy of the block Merkel information stored in the second blockchain.

[0219] See also Fig.13 , Fig.13 This is a schematic diagram of a data processing device based on blockchain provided in an embodiment of the present application. Figure 2It can be understood that the blockchain-based data processing device 2 can be in a forwarding service device, such as Fig. 9 The cross-chain message forwarding service shown; Fig.13 As shown, the blockchain-based data processing device 2 may include: a block height acquisition unit 21, a cross-chain message forwarding unit 22;

[0220] The block height acquisition unit 21 is used to acquire a cross-chain message initiated by the first blockchain, and acquire a block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain; the cross-chain message carries a chain identifier;

[0221] The cross-chain message forwarding unit 22 is used to forward the cross-chain message to the consensus node of the second blockchain if it is detected in the second blockchain corresponding to the chain identifier that the verifiable height H1 corresponding to the first blockchain is greater than or equal to the block height H2, so that the consensus node of the second blockchain verifies the validity of the cross-chain message according to the Merkel proof set corresponding to the cross-chain message and the block Merkel information of the verifiable height H1 in the first blockchain, and obtains the cross-chain verification result corresponding to the cross-chain message;

[0222] Among them, the block Merkle information is stored in the second blockchain, the Merkle proof set is obtained in the block Merkle tree corresponding to the block Merkle information, and the block Merkle tree includes multiple Merkle subtrees; when the cross-chain verification result indicates that the verification is successful, the consensus node of the second blockchain is used to store the transaction execution result corresponding to the cross-chain message to the second blockchain.

[0223] In one or more embodiments, the block height acquisition unit 21 acquires a cross-chain message initiated by the first blockchain, and acquires a block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain, including:

[0224] Obtain the contract status corresponding to the cross-chain management contract in the first blockchain. If the contract status is a transaction pending forwarding state, obtain the cross-chain message initiated by the cross-chain management contract in the first blockchain;

[0225] Determine in the first blockchain a first cross-chain transaction block to which the cross-chain transaction data indicated by the cross-chain message belongs, and obtain a block height H2 of the first cross-chain transaction block in the first blockchain.

[0226] In one or more embodiments, the blockchain-based data processing device 2 further includes: a verifiable height acquisition unit 23, a prompt information generation unit 24, and a prompt information sending unit 25;

[0227] A verifiable height acquisition unit 23 is used to obtain the verifiable height H1 corresponding to the first blockchain in the chain verification contract deployed by the second blockchain;

[0228] A prompt information generating unit 24, configured to generate a height update prompt information corresponding to the first blockchain if the verifiable height H1 is less than the block height H2;

[0229] The prompt information sending unit 25 is used to send the height update prompt information to the trusted oracle device, so that the trusted oracle device submits the block Merkle information corresponding to the maximum block height in the first blockchain to the chain verification contract in the second blockchain according to the height update prompt information;

[0230] Among them, the block Merkel information corresponding to the maximum block height is used to cover the block Merkel information and verifiable height H1 stored in the chain verification contract deployed by the second blockchain.

[0231] According to an embodiment of the present application, the steps involved in the blockchain-based data processing method shown above can be Fig.13 The data processing device 2 shown in the figure is based on the blockchain and is executed by each unit. For example, Figure 6 Step S203 shown can be performed by Fig.13 The block height acquisition unit 21 shown is used to execute, Figure 6 Step S204 shown can be performed by Fig.13 The cross-chain message forwarding unit 22 shown is used to execute the following.

[0232] According to one embodiment of the present application, Fig.13 The various units in the blockchain-based data processing device 2 shown can be separately or completely combined into one or several units to constitute, or one (some) of the units can be further divided into at least two functionally smaller sub-units, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the functions of one unit can also be implemented by at least two units, or the functions of at least two units can be implemented by one unit. In other embodiments of the present application, the blockchain-based data processing device 2 may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by the collaboration of at least two units.

[0233] In the embodiment of the present application, the cross-chain message between the first blockchain and the second blockchain can be forwarded by the forwarding service device. The forwarding service device does not need to verify the correctness of the cross-chain message. It only needs to detect the cross-chain message initiated by the cross-chain management contract (cross-chain bridge contract) in multiple blockchains in real time, and directly forward the cross-chain message to the corresponding blockchain (for example, the second blockchain), which can improve the transmission speed of cross-chain messages between different blockchains. In addition, the forwarding service device will only submit the cross-chain information when there is a block Merkle information (MMR root information) corresponding to the block height H2 greater than or equal to the cross-chain message in the second blockchain. Otherwise, it can trigger the trusted oracle device (TEE trusted oracle) to submit the latest MMR root information on the first blockchain to the second blockchain. That is to say, in order to ensure the correctness of the MMR root information, the embodiment of the present application introduces a TEE trusted oracle to maintain and submit the MMR root information, which can improve the accuracy of the MMR root information stored in the second blockchain.

[0234] See also Fig.14 , Fig.14 Schematic diagram of the structure of a computer device provided in an embodiment of the present application. Fig.14 As shown, the computer device 1000 can be a terminal device or a server, which will not be limited here. For ease of understanding, this application takes the computer device as a terminal device as an example. The computer device 1000 may include: a processor 1001, a network interface 1004 and a memory 1005. In addition, the computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. Among them, the user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 1005 may optionally also be at least one storage device located away from the aforementioned processor 1001. As Fig.14 As shown, the memory 1005 as a computer-readable storage medium may include an operating system, a network communication module, a user interface module, and a device control application program.

[0235] The network interface 1004 in the computer device 1000 can also provide a network communication function, and the optional user interface 1003 can also include a display screen (Display) and a keyboard (Keyboard). Fig.14In the computer device 1000 shown, the network interface 1004 can provide a network communication function; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to achieve:

[0236] Obtaining a cross-chain message submitted by the forwarding service device, and obtaining a chain identifier carried by the cross-chain message; the cross-chain message is associated with the cross-chain transaction data stored in the first blockchain;

[0237] Obtain the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and obtain the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information; the verifiable height H1 of the block Merkle information in the first blockchain is greater than or equal to the block height H2 of the cross-chain message in the first blockchain, and the block Merkle tree includes multiple Merkle subtrees;

[0238] According to the Merkle proof set and block Merkle information, the validity of the cross-chain message is verified to obtain the cross-chain verification result corresponding to the cross-chain message;

[0239] If the cross-chain verification result indicates that the verification is successful, the transaction execution result corresponding to the cross-chain message is obtained, and the transaction execution result is stored in the second blockchain.

[0240] Alternatively, the processor 1001 may implement:

[0241] Obtain a cross-chain message initiated by the first blockchain, and obtain the block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain; the cross-chain message carries a chain identifier;

[0242] If it is detected in the second blockchain corresponding to the chain identifier that the verifiable height H1 corresponding to the first blockchain is greater than or equal to the block height H2, the cross-chain message is forwarded to the consensus node of the second blockchain, so that the consensus node of the second blockchain verifies the validity of the cross-chain message according to the Merkle proof set corresponding to the cross-chain message and the block Merkle information of the verifiable height H1 in the first blockchain, and obtains the cross-chain verification result corresponding to the cross-chain message;

[0243] Among them, the block Merkle information is stored in the second blockchain, the Merkle proof set is obtained in the block Merkle tree corresponding to the block Merkle information, and the block Merkle tree includes multiple Merkle subtrees; when the cross-chain verification result indicates that the verification is successful, the consensus node of the second blockchain is used to store the transaction execution result corresponding to the cross-chain message to the second blockchain.

[0244] It should be understood that the computer device 1000 described in the embodiment of the present application can execute the above Figure 3 and Figure 6 The description of the data processing method based on blockchain in any corresponding embodiment can also be performed as described above. Fig.12 The description of the blockchain-based data processing device 1 in the corresponding embodiment, or the execution of the above Fig.13 The description of the blockchain-based data processing device 2 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated here.

[0245] In addition, it should be pointed out here that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the blockchain-based data processing device 1 or the blockchain-based data processing device 2 mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the above Figure 3 and Figure 6 The description of the data processing method based on blockchain in any corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application. As an example, program instructions can be deployed on a computing device for execution, or on multiple computing devices located at one location, or on multiple computing devices distributed at multiple locations and interconnected by a communication network. Multiple computing devices distributed at multiple locations and interconnected by a communication network can constitute a blockchain system.

[0246] In addition, it should be noted that: the embodiment of the present application also provides a computer program product or a computer program, which may include computer instructions, and the computer instructions may be stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor may execute the computer instructions, so that the computer device executes the above Figure 3 and Figure 6 The description of the data processing method based on blockchain in any corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer program product or computer program embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0247] It should be noted that, for the above-mentioned various method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0248] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0249] The modules in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0250] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

[0251] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A data processing method based on blockchain, characterized in that: include: Obtaining a cross-chain message submitted by the forwarding service device, and obtaining a chain identifier carried by the cross-chain message; the cross-chain message is associated with the cross-chain transaction data stored in the first blockchain; Obtaining the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and obtaining the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information; the verifiable height H1 of the block Merkle information in the first blockchain is greater than or equal to the block height H2 of the cross-chain message in the first blockchain, and the block Merkle tree includes multiple Merkle subtrees; According to the Merkle proof set and the block Merkle information, the validity of the cross-chain message is verified to obtain a cross-chain verification result corresponding to the cross-chain message; If the cross-chain verification result indicates that the verification is successful, the transaction execution result corresponding to the cross-chain message is obtained, and the transaction execution result is stored in the second blockchain.

2. The method according to claim 1, characterized in that The obtaining, in the second blockchain corresponding to the chain identifier, the block Merkle information corresponding to the first blockchain, and obtaining, in the block Merkle tree corresponding to the block Merkle information, the Merkle proof set corresponding to the cross-chain message, includes: In the chain verification contract deployed by the second blockchain corresponding to the chain identifier, obtaining the block Merkle information corresponding to the first blockchain; Determine in the first blockchain the first cross-chain transaction block to which the cross-chain transaction data indicated by the cross-chain message belongs, and obtain block path information of the first cross-chain transaction block in the block Merkle tree corresponding to the block Merkle information; Obtain subtree root information corresponding to multiple Merkle subtrees contained in the block Merkle tree, and combine the subtree root information and the node information contained in the block path information into a Merkle proof set corresponding to the cross-chain message.

3. The method according to claim 2, characterized in that The obtaining the block path information of the first cross-chain transaction block in the block Merkle tree corresponding to the block Merkle information includes: Obtaining a block hash value corresponding to the first cross-chain transaction block, and determining a Merkle subtree to which the block hash value belongs in a block Merkle tree corresponding to the block Merkle information; Taking the block hash value as the starting node information, traverse the hierarchical node information in the Merkle subtree to which the block hash value belongs until traversing to the subtree root information in the Merkle subtree to which the block hash value belongs, and determine the block path information corresponding to the first cross-chain transaction block according to the traversed hierarchical node information.

4. The method according to claim 2, characterized in that: The validating the cross-chain message according to the Merkel proof set and the block Merkel information to obtain a cross-chain verification result corresponding to the cross-chain message includes: Performing a hash operation on the Merkle proof set to obtain first candidate Merkle information corresponding to the first cross-chain transaction block, and obtaining a block verification result corresponding to the first cross-chain transaction block by comparing the block Merkle information with the first candidate Merkle information; Acquire transaction Merkle information in the block header of the first cross-chain transaction block, and acquire transaction path information of the cross-chain transaction data in a transaction Merkle tree corresponding to the transaction Merkle information; the transaction Merkle tree is determined by the transaction data included in the first cross-chain transaction block; According to the transaction path information and the transaction Merkel information, the validity of the cross-chain transaction data is verified to obtain a transaction verification result corresponding to the cross-chain transaction data; If the block verification result and the transaction verification result are both successful verification results, it is determined that the cross-chain verification result corresponding to the cross-chain message indicates successful verification.

5. The method according to claim 4, characterized in that The obtaining of a block verification result corresponding to the first cross-chain transaction block by comparing the block Merkle information with the first candidate Merkle information includes: If the block Merkle information is consistent with the first candidate Merkle information, determining that the block verification result corresponding to the first cross-chain transaction block is a successful verification result; If the block Merkle information is inconsistent with the first candidate Merkle information, it is determined that the block verification result corresponding to the first cross-chain transaction block is a verification failure result.

6. The method according to claim 4, characterized in that The validating the cross-chain transaction data according to the transaction path information and the transaction Merkel information to obtain a transaction verification result corresponding to the cross-chain transaction data includes: Performing a hash operation on the transaction path information to obtain second candidate Merkle information corresponding to the cross-chain transaction data; If the transaction Merkle information is consistent with the second candidate Merkle information, determining that the transaction verification result corresponding to the cross-chain transaction data is a successful verification result; If the transaction Merkel information is inconsistent with the second candidate Merkel information, it is determined that the transaction verification result corresponding to the cross-chain transaction data is a verification failure result.

7. The method according to claim 1, characterized in that If the cross-chain verification result indicates that the verification is successful, obtaining the transaction execution result corresponding to the cross-chain message, and storing the transaction execution result in the second blockchain, including: If the cross-chain verification result indicates that the verification is successful, encapsulating the cross-chain message into a second cross-chain transaction block, and obtaining the transaction type corresponding to the cross-chain message in the consensus phase of the second cross-chain transaction block; The cross-chain management contract in the second blockchain calls the asset processor contract that matches the transaction type, performs transaction execution processing on the cross-chain message according to the asset processor contract, and obtains the transaction execution result corresponding to the cross-chain message; The transaction execution result is added to the second cross-chain transaction block. If the second cross-chain transaction block reaches a consensus, the second cross-chain transaction block is stored in the second blockchain.

8. The method according to claim 1, characterized in that The method further comprises: If the cross-chain verification result indicates that the verification failed, an error prompt information corresponding to the cross-chain message is generated, and the error prompt information is sent to the forwarding service device through the cross-chain management contract in the second blockchain, so that the forwarding service device forwards the error prompt information to the cross-chain management contract in the first blockchain; the error prompt information is used to instruct the first blockchain to re-initiate the cross-chain message.

9. A data processing method based on blockchain, characterized in that: include: Obtain a cross-chain message initiated by the first blockchain, and obtain a block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain; the cross-chain message carries a chain identifier; If it is detected in the second blockchain corresponding to the chain identifier that the verifiable height H1 corresponding to the first blockchain is greater than or equal to the block height H2, the cross-chain message is forwarded to the consensus node of the second blockchain, so that the consensus node of the second blockchain verifies the validity of the cross-chain message according to the Merkle proof set corresponding to the cross-chain message and the block Merkle information of the verifiable height H1 in the first blockchain, and obtains the cross-chain verification result corresponding to the cross-chain message; Wherein, the block Merkle information is stored in the second blockchain, the Merkle proof set is obtained in the block Merkle tree corresponding to the block Merkle information, and the block Merkle tree includes multiple Merkle subtrees; when the cross-chain verification result indicates that the verification is successful, the consensus node of the second blockchain is used to store the transaction execution result corresponding to the cross-chain message to the second blockchain.

10. The method according to claim 9, characterized in that The obtaining of a cross-chain message initiated by the first blockchain, and obtaining a block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain, includes: Obtaining the contract status corresponding to the cross-chain management contract in the first blockchain, and if the contract status is a transaction pending forwarding state, obtaining a cross-chain message initiated by the cross-chain management contract in the first blockchain; Determine in the first blockchain a first cross-chain transaction block to which the cross-chain transaction data indicated by the cross-chain message belongs, and obtain a block height H2 of the first cross-chain transaction block in the first blockchain.

11. The method according to claim 9, characterized in that The method further comprises: In the chain verification contract deployed by the second blockchain, obtaining a verifiable height H1 corresponding to the first blockchain; If the verifiable height H1 is less than the block height H2, then generating height update prompt information corresponding to the first blockchain; Sending the height update prompt information to a trusted oracle device, so that the trusted oracle device submits the block Merkle information corresponding to the maximum block height in the first blockchain to the chain verification contract in the second blockchain according to the height update prompt information; Among them, the block Merkel information corresponding to the maximum block height is used to cover the block Merkel information and verifiable height H1 stored in the chain verification contract deployed by the second blockchain.

12. A data processing device based on blockchain, characterized in that: include: A cross-chain message acquisition unit, used to acquire a cross-chain message submitted by a forwarding service device, and to acquire a chain identifier carried by the cross-chain message; the cross-chain message is associated with the cross-chain transaction data stored in the first blockchain; A proof set acquisition unit, configured to acquire the block Merkle information corresponding to the first blockchain in the second blockchain corresponding to the chain identifier, and acquire the Merkle proof set corresponding to the cross-chain message in the block Merkle tree corresponding to the block Merkle information; the verifiable height H1 of the block Merkle information in the first blockchain is greater than or equal to the block height H2 of the cross-chain message in the first blockchain, and the block Merkle tree includes multiple Merkle subtrees; A cross-chain message verification unit, used to verify the validity of the cross-chain message according to the Merkel proof set and the block Merkel information, and obtain a cross-chain verification result corresponding to the cross-chain message; The cross-chain message execution unit is used to obtain the transaction execution result corresponding to the cross-chain message if the cross-chain verification result indicates that the verification is successful, and store the transaction execution result in the second blockchain.

13. A data processing device based on blockchain, characterized in that: include: A block height acquisition unit, configured to acquire a cross-chain message initiated by the first blockchain, and acquire a block height H2 of the cross-chain transaction data indicated by the cross-chain message in the first blockchain; the cross-chain message carries a chain identifier; A cross-chain message forwarding unit is configured to forward the cross-chain message to a consensus node of the second blockchain if it is detected in the second blockchain corresponding to the chain identifier that the verifiable height H1 corresponding to the first blockchain is greater than or equal to the block height H2, so that the consensus node of the second blockchain verifies the validity of the cross-chain message according to the Merkel proof set corresponding to the cross-chain message and the block Merkel information of the verifiable height H1 in the first blockchain, and obtains a cross-chain verification result corresponding to the cross-chain message; Wherein, the block Merkle information is stored in the second blockchain, the Merkle proof set is obtained in the block Merkle tree corresponding to the block Merkle information, and the block Merkle tree includes multiple Merkle subtrees; when the cross-chain verification result indicates that the verification is successful, the consensus node of the second blockchain is used to store the transaction execution result corresponding to the cross-chain message to the second blockchain.

14. A computer device, characterized in that: including memory and processor; The memory is connected to the processor, the memory is used to store a computer program, and the processor is used to call the computer program so that the computer device executes the method described in any one of claims 1 to 8, or executes the method described in any one of claims 9 to 11.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which is suitable for being loaded and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 8, or executes the method according to any one of claims 9 to 11.

16. A computer program product, characterized in that The method comprises a computer program / instruction, which, when executed by a processor, implements the method according to any one of claims 1 to 8, or implements the method according to any one of claims 9 to 11.

Citation Information

Cited By

  • Data processing method and device based on block chain, equipment, medium and product

    CN119766413A

  • Data processing method and apparatus based on blockchain, and device and medium

    EP4641465A1

  • Communication between networks

    EP4811201A1