WO2022205960A1 - Cross-chain data processing method and apparatus - Google Patents

Abstract

A cross-chain data processing method and apparatus. The method is executed by a data provider device, and comprises: obtaining first data from a first blockchain; generating second data, the second data having a predetermined data structure, and the second data comprising: a chain identifier of the first blockchain, the first data, and related information of the first data, wherein the related information of the first data comprises a chain type of the first blockchain; and providing the second data for a data receiver device.

Description

Cross-chain data processing method and device technical field

The embodiments of this specification relate to the field of blockchain technology, and more particularly, to a method and apparatus for processing cross-chain data.

Background technique

Blockchain technology, also known as distributed ledger technology, is a decentralized distributed database technology characterized by decentralization, openness, transparency, immutability, and trustworthiness. Each data of the blockchain will be broadcast to the blockchain nodes of the entire network, and each full node has a full amount of consistent data. With the popularity of blockchain technology, many different types of chains have emerged, which are applied in the fields of finance, health care, supply chain, asset management and traceability. However, most on-chain applications (encrypted currencies or smart contracts) cannot cross the boundary of the current chain and cannot cooperate with other chains to realize the circulation of value, thus limiting the development space of the blockchain. How to make different types of chains cooperate to realize the circulation of value has become the direction of exploration.

The data structure, data format, data semantics, on-chain proof and verification root of trust of the ledger data of different types of blockchains are different. Taking the Ethereum chain and the Hyperledger Fabric chain as examples, the field definitions in the data structures of the two are different. The data format of the Ethereum chain type blockchain is rlp encoding, the data format of the Fabric chain type blockchain is protobuf encoding, the proof data of the Ethereum chain is Spv proof data, and the proof data of the Fabric chain is more The signature of each endorsing node, the verification root of the Ethereum chain is the genesis block data, and the verification root of the Fabric chain is the respective public keys of multiple endorsing nodes. Therefore, it faces the problem of processing differentiated data in cross-chain and multi-chain applications.

Therefore, a more efficient cross-chain data processing scheme is needed.

SUMMARY OF THE INVENTION

The embodiments of this specification aim to provide a more effective cross-chain data processing solution to solve the deficiencies in the prior art.

To achieve the above purpose, one aspect of this specification provides a cross-chain data processing method. The method is executed by a data provider device, and includes: acquiring first data from a first blockchain; generating second data, the second The data has a predetermined data structure, and the second data includes: a chain identifier of the first blockchain, first data, and related information of the first data, wherein the related information of the first data includes the first data. A chain type of blockchain; providing the second data to the data recipient device.

In an implementation manner, the related information of the first data further includes a data structure type of the first data.

In one embodiment, the data structure type of the first data is one of the following types: block header type, transaction type, account status type, and receipt type.

In one embodiment, acquiring the first data from the first blockchain includes acquiring the first data and its certification data from the first blockchain, and the second data further includes the certification data.

In an embodiment, the second data further includes related information of the certification data, and the related information of the certification data includes at least one of the following: the type of the certification data, the data structure of the certification data Type, hash value of the attestation data, verification root of the attestation data.

In one embodiment, the type of the certification data is one of the following types: Spv certification data type, multi-issue certification data type.

In one embodiment, the type of the first blockchain is one of the following types: a Bitcoin chain type, an Ethereum chain type, and a Hyperledger Fabric chain type.

Another aspect of the present specification provides a cross-chain data processing method, the method being performed by a data receiver device, comprising: receiving second data from a data provider device, the second data having a predetermined data structure, and the first The second data includes: the chain identifier of the first blockchain, the first data, and the related information of the first data, wherein the related information of the first data includes the chain type of the first blockchain; The relevant information of the first data determines a data parser corresponding to the first data;

The first data is parsed by a data parser.

In an embodiment, the related information of the first data further includes a data structure type of the first data, wherein the data analysis corresponding to the first data is determined based on the related information of the first data The parser includes, based on the type of the first blockchain and the data structure type of the first data, determining a data parser corresponding to the first data.

In an embodiment, the data receiver device is preset with a corresponding relationship between the chain identifier of the first blockchain and the first verification root of the first blockchain, and the second data contains It also includes certification data of the first data, and the method further includes: determining a certification data parser and a verifier corresponding to the certification data; parsing the certification data through the certification data parser; passing the verification The device verifies the first data based on the first verification root and the certification data.

In one embodiment, determining the attestation data parser and verifier corresponding to the attestation data includes, based on the type of the first blockchain and the data structure type of the first data, determining the attestation data with the attestation data Corresponding proof data parser and validator.

In an embodiment, the second data further includes the type of the certification data and the data structure type of the certification data, wherein determining the certification data parser and verifier corresponding to the certification data includes: The attestation data parser and verifier corresponding to the attestation data are determined based on the type of attestation data and the data structure type of the attestation data.

In one embodiment, the second data further includes a second verification root of the first blockchain, wherein the verification is performed by the verifier based on the first verification root and the certification data. The first data is verified, and the second verification root is verified by the verifier based on the first verification root, and after the verification is passed, the verification is performed by the verifier based on the second verification root and the certification data. Verify the first data.

Another aspect of this specification provides a cross-chain data processing apparatus, the apparatus is deployed on a data provider device, and includes: an acquisition unit, configured to acquire first data from a first blockchain; a generation unit, configured to generate second data, the second data has a predetermined data structure, and the second data includes: a chain identifier of the first blockchain, first data, and related information of the first data, wherein the first data The related information includes the chain type of the first blockchain; the providing unit is configured to provide the second data to the data receiver device.

In one embodiment, the obtaining unit is further configured to obtain the first data and its certification data from the first blockchain, and the second data further includes the certification data.

Another aspect of the present specification provides a cross-chain data processing apparatus, the apparatus being deployed in a data receiver device, comprising: a receiving unit configured to receive second data from the data provider device, the second data having predetermined data structure, and the second data includes: the chain identifier of the first blockchain, the first data, and the related information of the first data, wherein the related information of the first data includes the first blockchain The first determining unit is configured to determine a data parser corresponding to the first data based on the relevant information of the first data; the first parsing unit is configured to analyze the first data parser through the data parser. a data.

In an embodiment, the related information of the first data further includes a data structure type of the first data, wherein the first determining unit is further configured to be based on the type of the first blockchain and the data structure type of the first data to determine a data parser corresponding to the first data.

In an embodiment, the data receiver device is preset with a corresponding relationship between the chain identifier of the first blockchain and the first verification root of the first blockchain, and the second data contains It also includes certification data of the first data, and the device further includes: a second determination unit, configured to determine a certification data parser and a validator corresponding to the certification data; a second parsing unit, configured to pass The certification data parser parses the certification data; the verification unit is configured to verify the first data based on the first verification root and the certification data through the verifier.

In one embodiment, the second determining unit is further configured to determine, based on the type of the first blockchain and the data structure type of the first data, a certification data parser and a certification data parser corresponding to the certification data. validator.

In an embodiment, the second data further includes the type of the certification data and the data structure type of the certification data, wherein the second determining unit is further configured to, based on the type of the certification data . The data structure type of the attestation data determines the attestation data parser and verifier corresponding to the attestation data.

In one embodiment, the second data further includes a second verification root of the first blockchain, wherein the verification unit includes a first verification sub-unit configured to pass the validator The second verification root is verified based on the first verification root, and the second verification subunit is configured to, after the verification is passed, the verification device based on the second verification root and the certification data. The first data is verified.

Another aspect of the present specification provides a computer-readable storage medium on which a computer program or instruction is stored, and when the computer program or instruction is executed in a computer, causes the computer to execute any one of the above methods.

Another aspect of the present specification provides a computing device, including a memory and a processor, where a computer program or instruction is stored in the memory, and the processor implements any one of the above methods when executing the computer program or instruction.

Through the data processing scheme for cross-chain data according to the embodiments of this specification, different cross-chain data can be converted into a unified data structure, so that the data receiver only needs to preset less data locally to realize the The analysis and proof process of different cross-chain data can realize multi-chain clients with a small amount of data, or multi-chain data processing smart contracts, etc., which improves the convenience of cross-chain communication.

Description of drawings

By describing the embodiments of the present specification in conjunction with the accompanying drawings, the embodiments of the present specification can be made clearer:

FIG. 1 shows a schematic diagram of a cross-chain system according to an embodiment of the present specification;

FIG. 2 shows a flowchart of a method for processing cross-chain data according to an embodiment of the present specification;

Figure 3 schematically shows a data structure of self-describing cross-chain data;

Figure 4 schematically shows a data structure of self-describing cross-chain data;

Figure 5 schematically shows a data structure of self-describing cross-chain data;

FIG. 6 schematically shows a data structure of self-describing cross-chain data;

FIG. 7 schematically shows a data structure of self-describing cross-chain data;

FIG. 8 shows a flowchart of a method for processing cross-chain data according to an embodiment of the present specification;

FIG. 9 shows a cross-chain data processing apparatus 900 according to an embodiment of the present specification;

FIG. 10 shows a cross-chain data processing apparatus 1000 according to an embodiment of the present specification.

Detailed ways

The embodiments of the present specification will be described below with reference to the accompanying drawings.

FIG. 1 shows a schematic diagram of a cross-chain system according to an embodiment of the present specification. As shown in FIG. 1 , the cross-chain system includes a first blockchain 11 , an off-chain network 12 and a second blockchain 13 . The first blockchain 11 and the second blockchain 13 are, for example, different types of blockchains, for example, the first blockchain 11 is an Ethereum chain, and the second blockchain 13 is a Fabric chain. The first blockchain 11 includes node 1, the second blockchain 13 includes node 2, and the off-chain network 12 includes a first relay device 121 and a second relay device 122. In this cross-chain system, node 1, node 2, the first relay device 121 and the second relay device 122 can all correspond to specific computing devices, each of which has its own connection address, so that they can pass The connection addresses are connected to each other, and send and receive data to each other. For example, as shown in FIG. 1, node 1 and node 2 can be connected to each other, node 1 can be connected to the first relay device 121, and node 2 can be connected to the second relay device. The device 122 is connected, and the first relay device 121 and the second relay device 122 can be directly or indirectly connected. Thus, for example, node 1 can locally read the ledger data in the first blockchain 11 and provide the data to the first relay device 121 or node 2, or the second relay device 122 can connect to node 2 And read the ledger data in the second blockchain 13 from the ledger data of the node 2, and provide the data to the first relay device 121 or the node 1, and so on.

Since the first blockchain 11 and the second blockchain 13 are different blockchains, when the first relay device 121 receives the ledger data from the first blockchain 11 and the second blockchain 13, respectively, The data will be parsed using different parsing methods and validated using different validation methods. For example, a multi-chain client is installed in the first relay device 121, and the multi-chain client is preset with the domain name and verification root of each blockchain, as well as the parsing algorithm and verification algorithm corresponding to various chain types, etc. . In order to parse and verify the received data by using the multi-chain client, the data provider needs to configure the self-describing data based on the blockchain ledger data in advance, and provide the self-describing data to the data receiver (for example, the first relay device 121). Therefore, after the first relay device 121 receives the above-mentioned self-describing data, the multi-chain client can read the blockchain domain name and data structure type corresponding to the ledger data included in the self-describing data from the self-describing data. and so on, so that the corresponding parsing algorithm and verification algorithm can be determined based on the read content, and finally the verified ledger data can be obtained.

It can be understood that the above description with reference to FIG. 1 is only an example description of the embodiments of this specification, and is not used to limit the scope of the embodiments of this specification. For example, in addition to a blockchain node and a repeater, the data provider can also It can be a blockchain proxy node. The data receiver can be a blockchain proxy node in addition to a blockchain node and a relay device. The data receiver is not limited to processing the received blocks through a multi-chain client. For example, the data receiver can also process the received blockchain data by executing a predetermined smart contract. Correspondingly, the domain name and verification root of each blockchain can be preset in the predetermined smart contract. Each chain type corresponds to the parsing algorithm, verification algorithm, etc.

The above data processing process at the data provider and the data receiver will be described in detail below.

2 shows a flowchart of a method for processing cross-chain data according to an embodiment of the present specification. The method is executed by a data provider device, including: step S202, obtaining first data from a first blockchain; step S204, generating second data, the second data has a predetermined data structure, and the second data includes: a chain identifier of the first blockchain, first data, and related information of the first data, wherein the first data The relevant information of the first blockchain includes the chain type of the first blockchain; step S206, the second data is provided to the data receiver device.

As mentioned above, the data provider here can be a blockchain node, a proxy node, an off-chain relay device, and so on. The data receiver can be a blockchain node, an agent node, an off-chain relay device, etc., which can receive data through a multi-chain client, or a blockchain node can receive data through a predetermined smart contract. Hereinafter, description will be given by taking the node 1 as the data provider and the first relay device 121 as the data receiver by way of example.

First, in step S202, the first data is obtained from the first blockchain.

In one embodiment, the first data can be any data in the first blockchain 11, and the node 1 can directly read the first data from the locally stored ledger data. The first data can be read locally in the node 1 by the client of the first blockchain 11 set therein.

In one embodiment, the node 1 can read the first data and its Spv proof data locally through its client. In this case, the first data can be block header data, transaction data, receipt data, and account status data, all of which can be verified by simple payment verification (Spv) proof data that they are indeed stored in the blockchain ledger data Consensus data. For example, if the first data is receipt 1 in block 1 in the first blockchain 11, the corresponding Spv proof data includes: the block header hash value of block 1, the receipt tree root hash value included in block 1 Hash value, the hash value of each other node in the tree path from receipt 1 to the root node in the receipt tree.

It can be understood that since the node 1 obtains the data of the first blockchain 11 locally, and the first blockchain 11 is an Ethereum chain type blockchain, the proof data of the first data is Spv data. Different types of blockchains have different types of proof data. For example, if the first data is the data in the second blockchain 13 and the second blockchain 13 is the Fabric chain, the proof data of the first data is the second The digital signature of the first data by each of the predetermined number of endorsing nodes in the blockchain 13 .

In step S204, second data is generated, the second data has a predetermined data structure, and the second data includes: the chain identifier of the first blockchain, the first data, and the related information of the first data, wherein, The relevant information of the first data includes the chain type of the first blockchain.

After node 1 reads the data locally, in order to facilitate cross-chain communication, it can configure self-describing cross-chain data based on the read data. The self-describing cross-chain data has a predetermined data structure, that is, it includes a predetermined field arrangement. , so that it can be read by the data receiver device.

FIG. 3 schematically shows a data structure of self-describing cross-chain data. As shown in Figure 3, the data structure includes three fields: chain identification, data element and data element information. Among them, the chain identifier is an identifier that uniquely identifies the blockchain instance, and uniquely corresponds to the blockchain instance. The chain identifier is, for example, the domain name of the blockchain. In order to uniquely identify each blockchain (that is, a blockchain instance) in the cross-chain field, for example, each blockchain can be assigned a unique chain domain name, which is readable and easy to identify, similar to a website domain name. , so as to have stronger operability. It can be understood that the chain identifier is not limited to the chain domain name, but can also be other unique identifiers of the blockchain instance, such as the verification root of the blockchain.

The data element field is the cross-chain data to be transmitted across the chain, such as the first data. The data element information is information used for parsing the first data. In one embodiment, the data metadata includes a chain type, and the chain type refers to the blockchain type of the blockchain instance, such as the Ethereum chain type, the Bitcoin chain type, the Hyperledger Fabric chain type, and so on. In one embodiment, the data element information includes a chain type and a data structure type of the data element. As described above, the first data may be block header data, transaction data, receipt data, and account data in the blockchain. Status data, etc. Correspondingly, the first data has different data structure types when it is different data. Therefore, the data structure types of the data elements include, for example, block header type, transaction type, account status type, receipt type, etc. .

FIG. 4 schematically shows a data structure of self-describing cross-chain data. In one embodiment, the metadata information includes the three fields shown in FIG. 4: chain type, data structure type, and hash value. The hash value field is the hash value of the cross-chain data, which is used to verify the hash value of the cross-chain data.

Figure 5 schematically shows a data structure of self-describing cross-chain data. Compared with the data structure shown in Figure 3, the data structure in Figure 5 also includes a proof meta field, which is the proof data used to verify the cross-chain data. The proof data has different forms according to the type of the specific chain. For example, in the blockchain type of Ethereum chain, the proof data is Spv proof data, and in the blockchain type of Fabric, the proof data is the endorsement node pair data element digital signature. Among them, in the blockchain of the Ethereum chain type, as mentioned above, the provable data includes block header data, receipt data, transaction data and account status data. Therefore, in the data structure shown in Figure 5, in The data metadata should include at least the chain type and the data structure type, so as to determine which provable data the self-describing cross-chain data corresponds to, so as to facilitate the parsing of the provable data by the data receiver.

FIG. 6 schematically shows a data structure of self-describing cross-chain data. Compared with the data structure shown in FIG. 5 , the data structure in FIG. 6 further includes a certification meta-information field, and the certification meta-information field includes information for parsing and verifying the certification data. In one embodiment, the attestation meta-information field may include an attestation type field. In one embodiment, the certification meta information field may include a certification type field and a data structure type field, where the data structure type field is the data structure type of the certification data, such as the data structure type corresponding to the Spv certification data, and the multiple The type of data structure corresponding to the data is indicated.

FIG. 7 schematically shows a data structure of self-describing cross-chain data. It is schematically shown in the data structure that the certification meta information field includes: a certification type field, a data structure type field, a hash value field, and a verification root field. Among them, the hash value field is the hash value of the proof data, which is used to verify the proof data, and the verification root field is the verification root of the proof data, that is, the verification root in the corresponding blockchain instance, and the verification root is used for combining The proof data is used to verify the cross-chain data.

In one embodiment, after reading the first data, node 1 may configure self-describing cross-chain data based on the first data according to the data structure of FIG. 3 or FIG. 4 to obtain the second data. Node 1 configures self-describing cross-chain data with the data structure shown in ”) and the chain type of the first blockchain 11 (ie, the Ethereum chain type), so that “Chain1” is filled in the chain identification field in FIG. 3 in the client, and the first data is filled in the data in FIG. 3 Meta field, fill in "Ethereum chain type" into the neuron information field in Figure 3, so as to obtain the self-describing cross-chain data corresponding to the first data.

In one embodiment, the first data is, for example, receipt 1. After reading receipt 1 and its Spv proof data, node 1 can configure the corresponding self-describing cross-section according to any of the predetermined data structures in FIG. 5-FIG. 7 . chain data as the second data. For example, the client of node 1 is pre-set with the chain identifier of the blockchain 11, the chain type, and the four data structure types in the first blockchain 11 (that is, the block header data type, transaction data type, receipt data type, Account status data type), proof type (that is, Spv proof type), data structure type of proof data (that is, the data structure type of Spv proof), and verification root, and the calculation unit of the hash value is also set in the client. After reading receipt 1 and its certificate, the client of node 1 determines that the data structure type of receipt 1 is the receipt data type, calculates the respective hash values of receipt 1 and its certificate through the hash value calculation unit, and combines the above items. , Receipt 1, its proof and their respective hash values are filled into the data structure shown in Figure 7, thereby obtaining self-describing cross-chain data corresponding to Receipt 1 and its proof data.

It can be understood that, as a data provider, the client of the node 1 in the first blockchain 11 only needs to preset various parameters related to the first blockchain 11 as described above. In the case where the relay device 121 acts as a data provider, it is connected to multiple blockchains, for example, it may read data from the respective blockchains to which it is connected and convert it into self-describing cross-chain data, in this case In the first relay device 121, the parameters related to each blockchain need to be preset. For example, parameters related to the first blockchain 11 and parameters related to the second blockchain 12 need to be preset in the multi-chain client of the first relay device 121, so that the first The relay device 121 may read data from the first blockchain 11 and the second blockchain 12 and convert them into self-describing cross-chain data, respectively.

In step S206, the second data is provided to the data recipient device.

In an embodiment, after acquiring the second data, the node 1 may directly send the second data to the device of the first relay device 121 .

In the case where the data provider is the first relay device 121 and the data receiver is the node 2, the first relay device 121 can provide the second data to the node 2 by sending a transaction to the node 2, in which the transaction starts with The second data is used as an incoming parameter to invoke a predetermined contract in the second blockchain 13 , thereby providing the second data to the node 2 .

8 shows a flow chart of a method for processing cross-chain data according to an embodiment of the present specification. The method is executed by a data receiver device, including: step S802, receiving second data from a data provider device, the second data It has a predetermined data structure, and the second data includes: a chain identifier of the first blockchain, first data, and related information of the first data, wherein the related information of the first data includes the first data. The chain type of the blockchain; Step S804, determine a data parser corresponding to the first data based on the relevant information of the first data; Step S806, parse the first data through the data parser.

As mentioned above, the data recipient can be a blockchain node, proxy node, off-chain relay device, etc., which can receive data through a multi-chain client, or a blockchain node can receive data through a predetermined smart contract. Hereinafter, description will be given by taking the node 1 as the data provider and the first relay device 121 as the data receiver by way of example.

In step S802, second data is received from the data provider device, the second data has a predetermined data structure, and the second data includes: the chain identifier of the first blockchain, the first data, the first data The related information, wherein the related information of the first data includes the chain type of the first blockchain.

As described above, the second data may have a data structure as shown in any one of FIGS. 3-7 . The data meta-information and the certification meta-information may also include different field configurations as described above. For example, the second data may include the following fields: chain identifier, data element, chain type, or the second data may include the following fields: chain identifier, data element, chain type, data structure type, or, in the second data The following fields may be included: chain ID, data element, chain type, data structure type, hash value, etc.

In step S804, a data parser corresponding to the first data is determined based on the relevant information of the first data. Step S806, parsing the first data through a data parser.

Since the first relay device 121 and the node 1 have negotiated the data structure of the self-describing cross-chain data in advance, the first relay device 121 can parse the self-describing data based on the data structure, so as to read from it. The data of each field in the self-describing data can obtain relevant information of the first data therein, and a parser for parsing the first data can be determined based on the relevant information, where the parser refers to a parsing algorithm.

The parser corresponding to each blockchain type can be preset in the multi-chain client in the first relay device 121, since each blockchain type adopts different data formats, for example, as mentioned above, the Ethereum chain type The data format of the blockchain is rlp encoding, and the data format of the Fabric chain type blockchain is protobuf encoding. Therefore, the parser corresponding to each blockchain type is used to decode different data formats.

The multi-chain client in the first relay device 121 may also preset parsers corresponding to different data structures in the blockchain, and the parsers corresponding to different data structures are used to perform data processing based on different data structures. Parse. For example, in an Ethereum chain type blockchain, assuming that the type of the first data is a receipt, after the first data is decoded by the above parser, the parser corresponding to the receipt is also used to parse the first data to obtain Obtain the content of the first data.

Therefore, after acquiring the relevant information of the first data, the multi-chain client of the first relay device 121 can select a corresponding parser to parse the first data based on the relevant information of the first data. For example, the related information of the first data includes the Ethereum chain type, so that the multi-chain client in the first relay device 121 selects a parser for decoding the rlp code to parse the first data. For example, the relevant information of the first data includes: Ethereum chain type, receipt type, so the multi-chain client in the first relay device 121 first selects a parser for decoding the rlp code to parse the first data, Then, a parser for reading the receipt is selected to further read the first data, so that the content of the first data can be obtained.

In one embodiment, as shown in FIG. 4 , the data element information further includes a hash value of the first data, so that before parsing the first data, the hash value of the first data can be calculated and combined with the data The hash value in the meta information is compared to determine whether the first data is the original data provided by the data provider.

In an implementation manner, the second data further includes certification data of the first data, and after receiving the second data, the data recipient may further perform the following steps to verify the first data included in the second data Verify the data: Step S808, determine the certification data parser and verifier corresponding to the certification data; Step S810, parse the certification data through the certification data parser; Step S812, use the verifier to use the certification data The proof data verifies the first data.

First, in step S808, the certification data parser and verifier corresponding to the certification data are determined.

Proof data parsers and validators corresponding to various chain types are preset in the multi-chain client of the first relay device 121. For example, the multi-chain client includes an Spv proof corresponding to the Ethereum chain type. A data parser (that is, a parsing algorithm), and a validator (that is, a verification algorithm) for verifying using the Spv proof data, in addition, the multi-chain client also includes a multi-state certification data parser corresponding to the type of Fabric chain , and a validator for authenticating with multi-signature proof data.

In one embodiment, the second data has the data structure shown in FIG. 5 , and the multi-chain client is based on the chain type (Ethereum chain type) in the data metadata and the data structure in the data metadata Type (receipt type), which determines the parser that parses the Spv proof data of the receipt in the Ethereum chain type blockchain, and determines the validator that uses the Spv proof data for verification.

In one embodiment, the second data has the data structure shown in FIG. 6 or FIG. 7 , and the multi-chain client can directly determine the corresponding parser based on the proof type and data structure type in the second data and validator.

Step S810: Parse the certification data through the certification data parser. The parsing process is similar to the parsing process for the first data above, including the decoding process of the data format and the reading process of the data structure, which will not be repeated here.

In step S812, the first data is verified by the verifier using the certification data.

As mentioned above, the validator refers to a preset validation algorithm in the multi-chain client. In addition, the chain identifier and minimum verification root of each blockchain are preset in the multi-chain client. Based on the chain identifier of the first blockchain 11 in the second data, the multi-chain client can obtain the preset minimum verification root corresponding to the first blockchain 11, and the minimum verification root is, for example, the first blockchain The hash of the genesis block of 11.

For example, the first data is receipt 1 , and the certification data is correspondingly the Spv certification data of receipt 1 . The multi-chain client can verify receipt 1 through the following steps: calculate the hash value of receipt 1; calculate the receipt tree in block 1 based on the hash values of other nodes in the tree path included in the Spv proof data the root hash value of ; compare the calculated root hash value to the root hash value of the receipt tree of block 1 included in the Spv proof data to determine whether receipt 1 is receipt 1 in block 1; and, Based on the Spv proof data including the block header hash value of block 1 and the minimum verification root of the first block chain 11 preset in the multi-chain client, determine whether block 1 is in the first block chain 11 block.

In one embodiment, as shown in FIG. 7 , the certification meta information further includes a verification root. For example, the verification root may include more verification root information than the minimum verification root preset in the multi-chain client. , for example, can include the block information of the genesis block, the longest chain information of block 1 in the blockchain, etc., so that the multi-chain client can use the minimum verification root to verify the verification root in the second data. , after the verification is passed, the receipt 1 can be verified based on the verification root and the Spv proof data. The verification root included in the certification meta information may also be the minimum verification root.

In one embodiment, as shown in FIG. 7 , the proof meta information further includes a hash value of the proof data, so that before using the proof data for verification, the hash value of the proof data can be calculated and compared with the proof data. The hash value in the meta information is compared to determine whether the proof data is the original data provided by the data provider.

FIG. 9 shows a cross-chain data processing apparatus 900 according to an embodiment of the present specification. The apparatus is deployed in a data provider device, and includes: an obtaining unit 91 configured to obtain first data from a first blockchain; The unit 92 is configured to generate second data, the second data has a predetermined data structure, and the second data includes: the chain identifier of the first blockchain, the first data, and the related information of the first data, Wherein, the relevant information of the first data includes the chain type of the first blockchain; the providing unit 93 is configured to provide the second data to the data receiver device.

In one embodiment, the obtaining unit 91 is further configured to obtain first data and its certification data from the first blockchain, and the second data further includes the certification data.

FIG. 10 shows a cross-chain data processing apparatus 1000 according to an embodiment of the present specification. The apparatus is deployed in a data receiver device, and includes: a receiving unit 101 configured to receive second data from a data provider device, the The second data has a predetermined data structure, and the second data includes: a chain identifier of the first blockchain, first data, and related information of the first data, wherein the related information of the first data includes all the chain type of the first blockchain; the first determining unit 102 is configured to determine a data parser corresponding to the first data based on the relevant information of the first data; the first parsing unit 103 is configured to: The first data is parsed by a data parser.

In an embodiment, the related information of the first data further includes a data structure type of the first data, wherein the first determining unit 102 is further configured to: The type and the data structure type of the first data determine the data parser corresponding to the first data.

In an embodiment, the data receiver device is preset with a corresponding relationship between the chain identifier of the first blockchain and the first verification root of the first blockchain, and the second data contains It also includes certification data of the first data, and the apparatus 1000 further includes: a second determination unit 104, configured to determine a certification data parser and a validator corresponding to the certification data; a second parsing unit 105, configured to In order to parse the certification data through the certification data parser; the verification unit 106 is configured to verify the first data based on the first verification root and the certification data through the verifier.

In an embodiment, the second determining unit 104 is further configured to determine a certification data parser corresponding to the certification data based on the type of the first blockchain and the data structure type of the first data and validator.

In an implementation manner, the second data further includes the type of the certification data and the data structure type of the certification data, wherein the second determining unit 104 is further configured to: The type, the data structure type of the attestation data, determines the attestation data parser and verifier corresponding to the attestation data.

In an embodiment, the second data further includes a second verification root of the first blockchain, wherein the verification unit 106 includes a first verification sub-unit 1061 configured to pass the The verifier verifies the second verification root based on the first verification root, and the second verification subunit 1062 is configured to, after the verification passes, pass the verifier based on the second verification root and the proof The data validates the first data.

Another aspect of the present specification provides a computer-readable storage medium on which a computer program or instruction is stored, and when the computer program or instruction is executed in a computer, causes the computer to execute any one of the above methods.

Another aspect of the present specification provides a computing device, including a memory and a processor, where a computer program or instruction is stored in the memory, and the processor implements any one of the above methods when executing the computer program or instruction.

Through the data processing scheme for cross-chain data according to the embodiments of this specification, different cross-chain data can be converted into a unified data structure, so that the data receiver only needs to preset less data locally to realize the The analysis and proof process of different cross-chain data can realize multi-chain clients with a small amount of data, or multi-chain data processing smart contracts, etc., which improves the convenience of cross-chain communication.

Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, as for the system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and for related parts, please refer to the partial descriptions of the method embodiments.

The foregoing describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that in the embodiments and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Those of ordinary skill in the art should further realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software or a combination of the two, in order to clearly illustrate the hardware and software interchangeability, the components and steps of each example have been generally described in terms of functions in the above description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Persons of ordinary skill in the art may use different methods of implementing the described functionality for each particular application, but such implementations should not be considered beyond the scope of this application.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be implemented in hardware, a software module executed by a processor, or a combination of the two. A software module can be placed in random access memory (RAM), internal memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other in the technical field. in any other known form of storage medium.

The specific embodiments described above further describe the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above descriptions are only specific embodiments of the present invention, and are not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims (28)

1. A cross-chain data processing method, the method is executed by a data provider device, comprising:

   Obtain the first data from the first blockchain;

   generating second data, the second data has a predetermined data structure, and the second data includes: a chain identifier of the first blockchain, first data, and related information of the first data, wherein the first The relevant information of the data includes the chain type of the first blockchain;

   The second data is provided to a data recipient device.
2. The method according to claim 1, wherein the related information of the first data further includes a data structure type of the first data.
3. The method according to claim 2, wherein the data structure type of the first data is one of the following types: block header type, transaction type, account status type, and receipt type.
4. The method according to claim 1, wherein obtaining the first data from the first blockchain comprises obtaining the first data and its certification data from the first blockchain, and the second data further includes the certification data .
5. The method according to claim 4, wherein the second data further includes related information of the certification data, and the related information of the certification data includes at least one of the following: the type of the certification data, the certification The data structure type of the data, the hash value of the attestation data, and the verification root of the attestation data.
6. The method according to claim 5, wherein the type of the certification data is one of the following types: Spv certification data type, multi-issue certification data type.
7. The method according to claim 1, wherein the type of the first blockchain is one of the following types: a Bitcoin chain type, an Ethereum chain type, and a Hyperledger Fabric chain type.
8. A cross-chain data processing method, the method is executed by a data receiver device, comprising:

   Receive second data from the data provider device, the second data has a predetermined data structure, and the second data includes: the chain identifier of the first blockchain, the first data, and the related information of the first data, wherein , the relevant information of the first data includes the chain type of the first blockchain;

   determining a data parser corresponding to the first data based on the relevant information of the first data;

   The first data is parsed by a data parser.
9. The method according to claim 8, wherein the related information of the first data further includes a data structure type of the first data, wherein the related information of the first data is determined based on the related information of the first data The corresponding data parser includes determining a data parser corresponding to the first data based on the type of the first blockchain and the data structure type of the first data.
10. The method according to claim 9, wherein a correspondence relationship between a chain identifier of the first blockchain and a first verification root of the first blockchain is preset in the data recipient device, and the The second data also includes certification data of the first data, and the method further includes:

    determining an attestation data parser and a validator corresponding to the attestation data;

    Parse the attestation data by the attestation data parser;

    The first data is verified by the verifier based on the first verification root and the attestation data.
11. 11. The method of claim 10, wherein determining an attestation data parser and a validator corresponding to the attestation data comprises, based on a type of the first blockchain and a data structure type of the first data, determining a parser and a validator corresponding to the attestation data The attestation data parser and verifier corresponding to the attestation data.
12. The method according to claim 10, wherein the second data further includes the type of the attestation data and the data structure type of the attestation data, wherein the attestation data parser and the attestation data parser corresponding to the attestation data are determined. The verifier includes a certification data parser and a verifier corresponding to the certification data determined based on the type of the certification data and the data structure type of the certification data.
13. 11. The method of claim 10, wherein the second data further includes a second verification root of the first blockchain, wherein the verification is based on the first verification root and the proof by the validator The first data is verified by the data, the second verification root is verified by the validator based on the first verification root, and after the verification is passed, the second verification root is verified by the validator based on the second verification root and The certification data verifies the first data.
14. A cross-chain data processing device, the device is deployed in a data provider device, comprising:

    an obtaining unit, configured to obtain the first data from the first blockchain;

    a generating unit, configured to generate second data, the second data has a predetermined data structure, and the second data includes: the chain identifier of the first blockchain, the first data, and the related information of the first data, Wherein, the relevant information of the first data includes the chain type of the first blockchain;

    A providing unit is configured to provide the second data to a data recipient device.
15. The apparatus according to claim 14, wherein the related information of the first data further includes a data structure type of the first data.
16. The apparatus according to claim 15, wherein the data structure type of the first data is one of the following types: block header type, transaction type, account status type, and receipt type.
17. The apparatus according to claim 14, wherein the obtaining unit is further configured to obtain the first data and its certification data from the first blockchain, and the second data further includes the certification data.
18. The device according to claim 17, wherein the second data further includes related information of the certification data, and the related information of the certification data includes at least one of the following: the type of the certification data, the certification The data structure type of the data, the hash value of the attestation data, and the verification root of the attestation data.
19. The apparatus according to claim 18, wherein the type of the certification data is one of the following types: Spv certification data type, multi-issue certification data type.
20. The apparatus according to claim 14, wherein the type of the first blockchain is one of the following types: Bitcoin chain type, Ethereum chain type, Hyperledger Fabric chain type.
21. A cross-chain data processing device, the device is deployed in a data receiver device, comprising:

    a receiving unit, configured to receive second data from the data provider device, the second data has a predetermined data structure, and the second data includes: the chain identifier of the first blockchain, the first data, the first relevant information of the data, wherein the relevant information of the first data includes the chain type of the first blockchain;

    a first determining unit, configured to determine a data parser corresponding to the first data based on the relevant information of the first data;

    The first parsing unit is configured to parse the first data through a data parser.
22. The apparatus according to claim 21, wherein the related information of the first data further includes a data structure type of the first data, wherein the first determining unit is further configured to, based on the first area The type of the block chain and the data structure type of the first data determine a data parser corresponding to the first data.
23. The apparatus according to claim 22, wherein a correspondence relationship between a chain identifier of the first blockchain and a first verification root of the first blockchain is preset in the data receiver device, and the The second data further includes certification data of the first data, and the device further includes:

    a second determining unit, configured to determine a certification data parser and a validator corresponding to the certification data;

    a second parsing unit, configured to parse the attestation data through the attestation data parser;

    A verification unit configured to verify the first data based on the first verification root and the certification data by the verifier.
24. The apparatus according to claim 23, wherein the second determination unit is further configured to determine the certificate corresponding to the certificate data based on the type of the first blockchain and the data structure type of the first data Data parsers and validators.
25. The apparatus according to claim 23, wherein the second data further includes the type of the certification data and the data structure type of the certification data, wherein the second determining unit is further configured to, based on the The type of attestation data and the data structure type of the attestation data determine the attestation data parser and verifier corresponding to the attestation data.
26. The apparatus according to claim 23, wherein the second data further includes a second verification root of the first blockchain, wherein the verification unit includes a first verification sub-unit configured to pass The verifier verifies the second verification root based on the first verification root, and the second verification subunit is configured to, after the verification is passed, pass the verifier based on the second verification root and the The proof data verifies the first data.
27. A computer-readable storage medium on which computer programs or instructions are stored, which, when executed in a computer, cause the computer to perform the method of any one of claims 1-13.
28. A computing device, comprising a memory and a processor, wherein a computer program or instruction is stored in the memory, and the processor implements the method according to any one of claims 1-13 when executing the computer program or instruction .

Images