WO2023019903A1 - Cross-chain transaction system and method, and device and storage medium - Google Patents

Abstract

The present application belongs to the technical field of blockchains. Disclosed are a cross-chain transaction system and method, and a device and a storage medium. In the cross-chain transaction method provided in the embodiments of the present application, cross-chain transaction data of a cross-chain transaction can be directly sent between two clients, thereby avoiding the risk of centralization. Furthermore, the client which has received the cross-chain transaction data can check the cross-chain transaction data by means of a check node, and then execute the current cross-chain transaction if the checking is passed, such that the security of the cross-chain transaction is effectively improved on the premise of direct communication between the two clients.

Description

Cross-chain transaction system, method, device and storage medium

This application claims the priority of the Chinese patent application with the application number 202110961524.7 and the title of the invention "Cross-chain transaction system, method, equipment and storage medium" submitted on August 20, 2021, the entire contents of which are incorporated in this application by reference middle.

technical field

This application relates to the technical field of blockchain, in particular to a cross-chain transaction system, method, device and storage medium.

Background technique

With the development of blockchain technology, blockchain technology is widely used in various industries, and each industry can build a blockchain system according to its own needs, so as to use the constructed blockchain system to store its own data. Different industries can provide users with different services. In order to realize data transfer between different businesses, cross-chain technology has emerged as the times require. Cross-chain technology is a key technology to break through information interaction barriers between chains and realize data circulation and value exchange. , is a bridge for the outward expansion and connection of the blockchain.

At present, cross-chain technologies mainly include notary mechanisms, hash locks, and relay chains. However, the notary mechanism relies too much on third parties, and there is a risk of centralization, which leads to poor security of cross-chain transactions; hash locking is limited to cross-chain asset exchange operations on assets, and the use scenarios are limited; there are malicious operations in the relay chain and other security risks. Therefore, there is an urgent need for a cross-chain transaction method that can effectively improve the security of cross-chain transactions.

Contents of the invention

This application provides a cross-chain transaction system, method, device and storage medium, which can effectively improve the security of cross-chain transactions. The technical solution is as follows:

In a first aspect, a cross-chain transaction system is provided, the cross-chain transaction system includes a first client of a first blockchain, a second client of a second blockchain, and a verification node;

The first client is configured to send the cross-chain transaction data of the cross-chain transaction to the second client;

The second client is used to receive the cross-chain transaction data, verify the cross-chain transaction data through the verification node, and execute the cross-chain transaction when the cross-chain transaction data passes the verification. The check node does not belong to the first blockchain and the second blockchain.

Through this cross-chain transaction system, two clients can directly send the cross-chain transaction data of cross-chain transactions, thereby avoiding the risk of centralization. Further, the client receiving the cross-chain transaction data can pass the verification node , to verify the cross-chain transaction data, and execute this cross-chain transaction when the verification passes, thus effectively improving the security of cross-chain transactions under the premise of direct communication between two clients sex.

In some embodiments, the second client is used to receive the cross-chain transaction data, and verify the cross-chain transaction data through the verification node on the third block chain, and the cross-chain transaction data If the verification is passed, execute the cross-chain transaction.

The cross-chain transaction data is verified by the verification node on the third block chain, which can ensure the security of the data, thereby improving the security of the cross-chain transaction.

In some embodiments, the second client is used to receive the cross-chain transaction data, verify the cross-chain transaction data through the verification node in the verification cluster, and pass the cross-chain transaction data verification In the case of , the cross-chain transaction is executed, and the verification cluster is a cluster based on a consensus mechanism.

Since the verification cluster is a cluster based on the consensus mechanism, the cross-chain transaction data is verified through the verification nodes in the verification cluster, so that the security of the data stored in the verification cluster is guaranteed, thus Further improve the security of cross-chain transactions.

In some embodiments, the second client is further configured to, based on the identification of the cross-chain transaction carried in the cross-chain transaction data, if the number corresponding to the identification of the cross-chain transaction is queried from the verification node Signature, execute the cross-chain transaction, and the digital signature indicates that the cross-chain transaction data has passed the verification.

The cross-chain transaction data is verified by querying the digital signature, which improves the security of the cross-chain transaction.

In some embodiments, the verification node is used to store the cross-chain transaction record of the cross-chain transaction, and the cross-chain transaction record indicates the transaction process and transaction execution status of the cross-chain transaction.

By storing the cross-chain transaction record of the cross-chain transaction in the verification node, it can provide rights confirmation and accountability services for illegal cross-chain transactions, thereby improving the security of cross-chain transactions.

In some embodiments, the cross-chain transaction record includes the execution result of the cross-chain transaction, the execution result indicates that the cross-chain transaction has been successfully executed, or the execution result indicates that the cross-chain transaction has failed to execute.

By recording the results of cross-chain transaction execution failure or successful execution, it can provide rights confirmation and accountability services for illegal cross-chain transactions, thereby improving the security of cross-chain transactions.

In some embodiments, the check node is also used to:

Receive a transaction query request sent by the third client, and the transaction query request indicates to query the cross-chain transaction record;

Based on the transaction query request, the third client is verified, and if the third client is the first client or the second client, the cross-chain transaction record is sent to the third client.

In this way, only the participants of the cross-chain transaction have query authority for the cross-chain transaction record stored in the verification node, which can ensure the security of the cross-chain transaction record and prevent the cross-chain transaction record from being illegally Obtain.

In some embodiments, the check node is also used to:

receiving the cross-chain transaction request sent by the first client, the cross-chain transaction request indicating to execute the cross-chain transaction on the second block chain;

Based on the data stored in the verification node, the cross-chain transaction request is verified. If the cross-chain transaction request passes the verification, a confirmation notification is sent to the first client, and the confirmation notification indicates that the first The client sends the cross-chain transaction data to the second client.

By verifying the cross-chain transaction request, and returning a confirmation notification to the first client if the verification is passed, the security of this cross-chain transaction can be ensured.

In some embodiments, the verification node is further configured to verify the cross-chain transaction request based on the identity data of the first client and the identity data of the second client stored in the verification node.

By verifying the cross-chain transaction request through the identity data of both parties in the cross-chain transaction, it can ensure that the identities of the two parties participating in this cross-chain transaction are credible, thereby improving the security of the cross-chain transaction.

In some embodiments, the identity data of the first client includes the first identity certificate of the first client, and the first identity certificate indicates that the first client has registered for the cross-chain service; the identity data of the second client includes the The second identity certificate of the second client, where the second identity certificate indicates that the second client has registered for the cross-chain service.

By means of the identity certificate, it is convenient for the first client to initiate a cross-chain transaction for the second client to verify the identities of the two parties to ensure the security of the cross-chain transaction.

In some embodiments, the check node is also used to:

Receive the first registration request sent by the first client, verify the identity of the first client, and generate the first identity certificate if the verification is passed, store the first identity certificate, and the first registration The request indicates that the first client requests to register the cross-chain service;

Receive the second registration request sent by the second client, verify the identity of the second client, and generate the second identity certificate if the verification is passed, store the second identity certificate, and the second registration The request indicates that the second client requests to register the cross-chain service.

By issuing identity certificates for the first client and the second client to prove that both clients have registered for the cross-chain service, it ensures that the identities of both parties are guaranteed when the first client and the second client perform cross-chain transactions Credible, thereby improving the security of cross-chain transactions.

In some embodiments, the identity data of the first client further includes an authorization record of the first client, and the authorization record indicates the type of cross-chain operation for which the first client has obtained permission.

By storing the authorization record of the client for the type of cross-chain operation as the identity data of the client, it is ensured that when the first client and the second client perform a cross-chain transaction, the cross-chain operation involved has been authorized. Thereby improving the security of cross-chain transactions.

In some embodiments, the verification node is also used to receive the authorization request sent by the first client, store the authorization request, and the authorization request indicates that the cross-chain operation type corresponding to the cross-chain operation is performed on the second blockchain. cross-chain transactions;

The second client is further configured to send an authorization notification to the verification node based on the authorization request, and the authorization notification indicates that the first client is allowed to perform the cross-chain operation corresponding to the cross-chain operation type on the second blockchain. Cross-chain transactions;

The check node is also used to receive the authorization notification and store the authorization notification.

By storing the authorization request of the first client and the authorization notification of the second client to record the authorization of the cross-chain operation between the first client and the second client, it is ensured that the subsequent execution of the first client and the second client When cross-chain transactions are involved, the cross-chain operations involved have been authorized, thereby improving the security of cross-chain transactions.

In some embodiments, the second client is also used for any of the following:

Querying the authorization request through the verification node, and sending the authorization notification to the verification node;

receiving the authorization request sent by the check node, and sending the authorization notification to the check node.

In some embodiments, the verification node is also used to generate a digital signature of the cross-chain transaction and store the digital signature when the cross-chain transaction request passes the verification, and the digital signature indicates that the cross-chain transaction data It has been verified.

By generating the digital signature of this cross-chain transaction, an endorsement signature is carried out for this cross-chain transaction, which also provides a guarantee for the security of this cross-chain transaction, so that the subsequent second client can receive this cross-chain When transacting cross-chain transaction data, the cross-chain transaction data is verified by verification nodes to improve the security of cross-chain transactions.

In the second aspect, a cross-chain transaction method is provided, which is executed by the first client of the first block chain in the cross-chain transaction system, and the cross-chain transaction system also includes the second client of the second block chain and the proofreader test point, the method includes:

Send a cross-chain transaction request to the verification node, the cross-chain transaction request indicates to perform a cross-chain transaction on the second blockchain, and the verification node does not belong to the first blockchain and the second blockchain;

receiving the confirmation notification sent by the verification node, the confirmation notification instructing the first client to send the cross-chain transaction data of the cross-chain transaction to the second client;

Send the cross-chain transaction data to the second client.

In some embodiments, the method also includes:

Sending a first registration request to the verification node, where the first registration request indicates that the first client requests to register for the cross-chain service.

In some embodiments, the method also includes:

An authorization request is sent to the verification node, where the authorization request indicates that a cross-chain transaction corresponding to a cross-chain operation type is executed on the second blockchain.

In the third aspect, a cross-chain transaction method is provided, which is executed by the second client of the second block chain in the cross-chain transaction system, and the cross-chain transaction system also includes the first client of the first block chain and the proofreader test point, the method includes:

Receive the cross-chain transaction data of the cross-chain transaction sent by the first client, verify the cross-chain transaction data through the verification node, and execute the cross-chain transaction if the cross-chain transaction data verification passes , the check node does not belong to the first blockchain and the second blockchain.

In some embodiments, the verification of the cross-chain transaction data by the verification node includes:

The cross-chain transaction data is verified by the verification node on the third block chain.

In some embodiments, the verification of the cross-chain transaction data by the verification node includes:

The cross-chain transaction data is verified by the verification node in the verification cluster, which is a cluster based on a consensus mechanism.

In some embodiments, the cross-chain transaction data is verified by the verification node, and the cross-chain transaction is executed when the verification of the cross-chain transaction data passes, including:

Based on the identification of the cross-chain transaction carried in the cross-chain transaction data, if the digital signature corresponding to the identification of the cross-chain transaction is queried from the verification node, the cross-chain transaction is executed, and the digital signature indicates that the cross-chain transaction The transaction data has been verified.

In some embodiments, the method also includes:

Sending a second registration request to the check node, where the second registration request indicates that the second client requests to register for the cross-chain service.

In some embodiments, the method also includes:

Based on the authorization request of the first client, an authorization notification is sent to the verification node, the authorization request indicates that the cross-chain transaction corresponding to the cross-chain operation type is performed on the second blockchain, and the authorization notification indicates that the first The client executes a cross-chain transaction corresponding to the cross-chain operation type on the second blockchain.

In some embodiments, the authorization notification sent to the verification node based on the authorization request of the first client includes any of the following:

Querying the authorization request through the verification node, and sending the authorization notification to the verification node;

receiving the authorization request sent by the check node, and sending the authorization notification to the check node.

In the fourth aspect, a cross-chain transaction method is provided, which is executed by a verification node in a cross-chain transaction system, and the cross-chain transaction system also includes a first client of the first blockchain and a first client of the second blockchain. For the second client, the method includes:

Receive a cross-chain transaction request for a cross-chain transaction sent by the first client, where the cross-chain transaction request indicates that the cross-chain transaction is executed on the second blockchain;

Based on the data stored in the verification node, the cross-chain transaction request is verified. If the cross-chain transaction request passes the verification, a confirmation notification is sent to the first client, and the confirmation notification indicates that the first The client sends the cross-chain transaction data to the second client.

In some embodiments, the check node belongs to a third blockchain.

In some embodiments, the verification node belongs to a verification cluster, and the verification cluster is a cluster based on a consensus mechanism.

In some embodiments, the method also includes:

The cross-chain transaction record of the cross-chain transaction is stored, and the cross-chain transaction record indicates the transaction process and transaction execution status of the cross-chain transaction.

In some embodiments, the cross-chain transaction record includes the execution result of the cross-chain transaction, the execution result indicates that the cross-chain transaction has been successfully executed, or the execution result indicates that the cross-chain transaction has failed to execute.

In some embodiments, the method also includes:

Receive a transaction query request sent by the third client, and the transaction query request indicates to query the cross-chain transaction record;

Based on the transaction query request, the third client is verified, and if the third client is the first client or the second client, the cross-chain transaction record is sent to the third client.

In some embodiments, the cross-chain transaction request is verified based on the data stored in the verification node, including:

The cross-chain transaction request is verified based on the identity data of the first client and the identity data of the second client stored in the verification node.

In some embodiments, the identity data of the first client includes the first identity certificate of the first client, and the first identity certificate indicates that the first client has registered for the cross-chain service; the identity data of the second client includes the The second identity certificate of the second client, where the second identity certificate indicates that the second client has registered for the cross-chain service.

In some embodiments, the method also includes:

Receive the first registration request sent by the first client, verify the identity of the first client, and generate the first identity certificate if the verification is passed, store the first identity certificate, and the first registration The request indicates that the first client requests to register the cross-chain service;

Receive the second registration request sent by the second client, verify the identity of the second client, and generate the second identity certificate if the verification is passed, store the second identity certificate, and the second registration The request indicates that the second client requests to register the cross-chain service.

In some embodiments, the identity data of the first client further includes an authorization record of the first client, and the authorization record indicates the type of cross-chain operation for which the first client has obtained permission.

In some embodiments, the method also includes:

Receive the authorization request sent by the first client, store the authorization request, and the authorization request indicates to execute the cross-chain transaction corresponding to the cross-chain operation type on the second blockchain;

receiving an authorization notification sent by the second client, storing the authorization notification, the authorization notification indicating that the first client is allowed to perform a cross-chain transaction corresponding to the cross-chain operation type on the second block chain.

In some embodiments, the method also includes:

In the case that the cross-chain transaction request is verified and passed, a digital signature of the cross-chain transaction is generated and stored, and the digital signature indicates that the cross-chain transaction data has passed the verification.

In a fifth aspect, a cross-chain transaction device is provided, which includes a sending module and a receiving module.

The sending module is used to send a cross-chain transaction request to the verification node, the cross-chain transaction request indicates that the cross-chain transaction is performed on the second blockchain, and the verification node does not belong to the first blockchain and the second blockchain ;

A receiving module, configured to receive a confirmation notification sent by the verification node, the confirmation notification instructing the first client to send the cross-chain transaction data of the cross-chain transaction to the second client;

The sending module is also used to send the cross-chain transaction data to the second client.

In some embodiments, the sending module is further configured to send a first registration request to the verification node, where the first registration request indicates that the first client requests to register for the cross-chain service.

In some embodiments, the sending module is further configured to send an authorization request to the verification node, where the authorization request indicates to perform a cross-chain transaction corresponding to a cross-chain operation type on the second blockchain.

In a sixth aspect, a cross-chain transaction device is provided, and the device includes an execution module.

The execution module is used to receive the cross-chain transaction data of the cross-chain transaction sent by the first client, and verify the cross-chain transaction data through the verification node, and if the verification of the cross-chain transaction data passes , execute the cross-chain transaction, and the check node does not belong to the first block chain and the second block chain.

In some embodiments, the execution module is configured to verify the cross-chain transaction data through the verification node on the third block chain.

In some embodiments, the execution module is configured to verify the cross-chain transaction data through the verification node in the verification cluster, and the verification cluster is a cluster based on a consensus mechanism.

In some embodiments, the execution module is configured to, based on the cross-chain transaction identifier carried in the cross-chain transaction data, if the digital signature corresponding to the cross-chain transaction identifier is found from the verification node, execute For the cross-chain transaction, the digital signature indicates that the cross-chain transaction data has been verified.

In some embodiments, the device further includes a sending module, configured to send a second registration request to the verification node, where the second registration request indicates that the second client requests to register for the cross-chain service.

In some embodiments, the sending module is further configured to send an authorization notification to the verification node based on the authorization request of the first client, and the authorization request indicates that the cross-chain operation type corresponding to the second block chain is executed on the second block chain. For a cross-chain transaction, the authorization notification indicates that the first client is allowed to perform a cross-chain transaction corresponding to the cross-chain operation type on the second blockchain.

In some embodiments, the sending module is also used for any of the following:

Querying the authorization request through the verification node, and sending the authorization notification to the verification node;

receiving the authorization request sent by the check node, and sending the authorization notification to the check node.

In a seventh aspect, a cross-chain transaction device is provided, which includes a receiving module and a verification module.

A receiving module, configured to receive a cross-chain transaction request for a cross-chain transaction sent by the first client, where the cross-chain transaction request indicates that the cross-chain transaction is executed on the second block chain;

A verification module, configured to verify the cross-chain transaction request based on the data stored in the verification node, and send a confirmation notification to the first client if the cross-chain transaction request passes the verification. The notification instructs the first client to send the cross-chain transaction data to the second client.

In some embodiments, the check node belongs to a third blockchain.

In some embodiments, the verification node belongs to a verification cluster, and the verification cluster is a cluster based on a consensus mechanism.

In some embodiments, the device also includes a storage module for:

The cross-chain transaction record of the cross-chain transaction is stored, and the cross-chain transaction record indicates the transaction process and transaction execution of the cross-chain transaction.

In some embodiments, the cross-chain transaction record includes the execution result of the cross-chain transaction, the execution result indicates that the cross-chain transaction has been successfully executed, or the execution result indicates that the cross-chain transaction has failed to execute.

In some embodiments, the receiving module is also used to receive a transaction query request sent by the third client, the transaction query request indicates to query the cross-chain transaction record; the verification module is also used to, based on the transaction query request, The third client performs verification, and if the third client is the first client or the second client, sends the cross-chain transaction record to the third client.

In some embodiments, the verification module is further configured to verify the cross-chain transaction request based on the identity data of the first client and the identity data of the second client stored in the verification node.

In some embodiments, the identity data of the first client includes the first identity certificate of the first client, and the first identity certificate indicates that the first client has registered for the cross-chain service; the identity data of the second client includes the The second identity certificate of the second client, where the second identity certificate indicates that the second client has registered for the cross-chain service.

In some embodiments, the verification module is also used to:

Receive the first registration request sent by the first client, verify the identity of the first client, and generate the first identity certificate if the verification is passed, store the first identity certificate, and the first registration The request indicates that the first client requests to register the cross-chain service;

Receive the second registration request sent by the second client, verify the identity of the second client, and generate the second identity certificate if the verification is passed, store the second identity certificate, and the second registration The request indicates that the second client requests to register the cross-chain service.

In some embodiments, the identity data of the first client further includes an authorization record of the first client, and the authorization record indicates the type of cross-chain operation for which the first client has obtained permission.

In some embodiments, the storage module is also used to:

Receive the authorization request sent by the first client, store the authorization request, and the authorization request indicates to execute the cross-chain transaction corresponding to the cross-chain operation type on the second blockchain;

receiving an authorization notification sent by the second client, storing the authorization notification, the authorization notification indicating that the first client is allowed to perform a cross-chain transaction corresponding to the cross-chain operation type on the second block chain.

In some embodiments, the storage module is also used to:

In the case that the cross-chain transaction request is verified and passed, a digital signature of the cross-chain transaction is generated and stored, and the digital signature indicates that the cross-chain transaction data has passed the verification.

In an eighth aspect, a computing device is provided, the computing device includes a processor and a memory, the memory is used to store at least one piece of program code, the at least one piece of program code is loaded by the processor and executed as described in the second aspect or the second The cross-chain transaction method provided in any optional implementation of the third aspect, or the cross-chain transaction method provided in the third aspect or any optional implementation of the third aspect, or, as mentioned above The cross-chain transaction method provided in the fourth aspect or any optional implementation manner in the fourth aspect.

In a ninth aspect, a computer-readable storage medium is provided, where the computer-readable storage medium is used to store at least one piece of program code, and the at least one piece of program code is used to execute any one of the above-mentioned second aspect or second aspect. The cross-chain transaction method provided in the selected implementation manner, or the cross-chain transaction method provided in the third aspect or any of the optional implementation methods in the third aspect above, or, as in the fourth aspect or the fourth aspect above The cross-chain transaction method provided in any optional implementation of the aspect.

In a tenth aspect, a computer program product is provided. When the computer program product is run on a computer, the computer is made to execute the cross-chain link provided in the second aspect or any optional implementation manner of the second aspect. The transaction method, or the cross-chain transaction method provided in the above third aspect or any optional implementation of the third aspect, or, as the above fourth aspect or any optional implementation of the fourth aspect The cross-chain transaction method provided in .

Description of drawings

Figure 1 is a schematic diagram of the architecture of a cross-chain transaction system provided by the embodiment of the present application;

FIG. 2 is a schematic structural diagram of a first client 110 provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of an architecture of a check node 130 provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of the architecture of a verification cluster provided by an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a computing device provided by an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a computing device provided by an embodiment of the present application;

Fig. 7 is a schematic flow diagram of a cross-chain transaction method provided by the embodiment of the present application;

Figure 8 is a schematic diagram of a cross-chain transaction system provided by the embodiment of this application;

Fig. 9 is a schematic structural diagram of a cross-chain transaction device provided by the embodiment of the present application;

Figure 10 is a schematic structural diagram of a cross-chain transaction device provided by the embodiment of the present application;

Fig. 11 is a schematic structural diagram of a cross-chain transaction device provided by the embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the implementation manners of the present application will be further described in detail below in conjunction with the accompanying drawings.

Before introducing the technical solutions provided by the embodiments of the present application, key terms involved in the present application will be described below.

Blockchain is a new application model of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. It has the properties of transparency, credibility, tamper-proof, and traceability. Blockchain is essentially a decentralized database, which is a series of data blocks associated with each other using cryptographic methods. Each data block contains a batch of network transaction information to verify the validity of its information. (anti-counterfeiting) and generate the next block. In other words, blockchain technology uses block chain data structures to verify and store data, uses distributed node consensus algorithms to generate and update data, uses cryptography to ensure the security of data transmission and access, and utilizes automated script codes. A decentralized architecture and computing paradigm for programming and manipulating data through intelligent contracts.

A smart contract is a computerized protocol that can execute the terms of a contract, implemented by code deployed on a shared ledger for execution when certain conditions are met, and codes are used to complete automated transactions according to actual business needs , such as querying the logistics status of the goods purchased by the buyer, and transferring the buyer's electronic currency to the merchant's address after the buyer signs for the goods; The contract for processing. In some embodiments, smart contracts are also referred to as chaincodes.

Interoperability is the ability to exchange information between two or more systems and applications and to use the exchanged information.

Inter-blockchain is a protocol that solves the mutual transmission, transfer and exchange of digital assets and functional states on two or more different blockchains. important means of sexuality. In some embodiments, cross-chain operation refers to interoperability between multiple blockchains.

The consensus mechanism is an algorithm for blockchain transactions to reach a distributed consensus. In the embodiment of this application, the user can choose an appropriate consensus algorithm according to the actual business scenario, the consensus algorithm includes but not limited to: proof of work (proof of work, POW), proof of stake (proof of stake, POS), authorized equity Proof (delegated proof of stake, DPOS), practical Byzantine fault tolerance algorithm (practical byzantine fault tolerance, PBFT), raft, kafka, hotstuff, etc.

An endorsement is a guarantee, a guarantee. In the embodiment of this application, it refers to the process of confirming the validity of the transaction.

A digital certificate refers to a digital certification that marks the identity information of each party in Internet communication. People can use it to identify each other's identity on the Internet, so a digital certificate is also called a digital identity. Digital certificates guarantee the integrity and security of information and data in the form of encryption or decryption for network users in computer network communication. In this embodiment of the application, a digital certificate is also called an identity certificate.

The following briefly introduces the application scenarios of the technical solution provided by the present application.

The cross-chain transaction method provided by the embodiment of the present invention can be applied in scenarios where cross-chain transactions are required to realize interconnection between chains, such as joint certificate deposit and joint traceability. Schematically, the scenarios where the cross-chain transaction method provided by the embodiment of the present invention can be applied include but are not limited to:

Scenario 1: Joint deposit of certificates.

Credible certificate storage is one of the blockchain scenarios that are currently being promoted in large numbers. Among them, joint certificate storage means that different blockchains used for certificate storage can conduct cross-chain transactions safely and reliably between blockchains. data flow. Schematically, in some data storage scenarios such as contract certificate storage chains and copyright certificate storage chains, if a dispute occurs, the judicial blockchain can obtain evidence information on other chains through cross-chain transactions, thereby ensuring the authenticity of the evidence. Improve the efficiency and effectiveness of evidence collection and reduce the cost of judicial judgment.

Scenario 2: Joint traceability.

Information traceability is also one of the blockchain scenarios that are currently widely promoted. Among them, joint traceability means that different blockchains used to store commodity information (including virtual commodities and physical commodities) can be carried out safely and credibly through cross-chain transactions. Data flow between blockchains. Schematically, manufacturers, processors, suppliers, and buyers can set up their own blockchain traceability platforms. Through cross-chain transactions, data circulation between blockchains can be carried out safely and credibly, and the whole life cycle tracking Commodity information ensures the quality of the product and can more accurately locate the target customer group. At the same time, the authenticity of the data on the chain is not lost in the cross-chain transmission, and the full life cycle information of the product is provided for manufacturers and end customers.

It should be noted that the above scenario is only an exemplary description, and the cross-chain transaction method provided by the embodiment of the present invention can be applied to various scenarios that require interconnection between chains through cross-chain transactions. For example, the cross-chain transaction method can also be applied to the scene of cross-chain asset transfer, etc. The embodiment of this application does not limit the application scene of the cross-chain transaction method.

Based on the above application scenarios, the embodiment of this application provides a cross-chain transaction method. In this cross-chain transaction method, the cross-chain transaction data of the cross-chain transaction can be directly transferred between clients corresponding to different blockchains, realizing direct Communication operation avoids the risk of centralization. Moreover, when one of the clients receives the cross-chain transaction data, it will verify the cross-chain transaction data through the verification node. If the verification passes, then execute Corresponding cross-chain transactions, thus effectively improving the security of cross-chain transactions.

Figure 1 is a schematic diagram of a cross-chain transaction system provided by the embodiment of this application. As shown in Figure 1, the cross-chain transaction system 100 includes a first client 110 of the first block chain, a second client 120 of the second block chain, and a verification node 130. The verification node 130 does not belong to the first A blockchain and a second blockchain.

The first client 110 is used to send the cross-chain transaction data of the cross-chain transaction to the second client 120;

The second client 120 is used to receive the cross-chain transaction data, verify the cross-chain transaction data through the verification node 130, and execute the cross-chain transaction when the cross-chain transaction data passes the verification.

Wherein, the first client 110 and the second client 120 are connected through a wired network or a wireless network. The verification node 130 communicates with the first client 110 and the second client 120 respectively through a wired network or a wireless network. In some embodiments, the wireless or wired network described above uses standard communication techniques and/or protocols. The network is usually the Internet, but can be any network, including but not limited to local area network (LAN), metropolitan area network (MAN), wide area network (WAN), mobile, wired or wireless Any combination of network, private network, or virtual private network. In some embodiments, peer-to-peer (P2P) communication is implemented between the first client 110 and the second client 120 based on a remote procedure call protocol (remote procedure call protocol, RPC). In some embodiments, data exchanged over a network is represented using technologies and/or formats including hyper text markup language (HTML), extensible markup language (XML), and the like. In addition, it is also possible to use methods such as secure socket layer (secure socket layer, SSL), transport layer security (transport layer security, TLS), virtual private network (virtual private network, VPN), Internet protocol security (internet protocol security, IPsec) and other conventional encryption techniques to encrypt all or some links. In other embodiments, custom and/or dedicated data communication techniques can also be used instead of or in addition to the data communication techniques described above.

The first client 110 has the function of operating the first block chain, and can perform block chain services by operating nodes on the first block chain, such as data uploading services and cross-chain communication services. In some embodiments, the first block chain is maintained by multiple first node devices 140, and each first node device 140 can be a terminal on the user side or a server. Terminals, also known as smart terminals or mobile smart terminals, refer to a type of equipment with rich human-computer interaction methods, the ability to access the Internet, usually equipped with various operating systems, and strong processing capabilities. In some embodiments, the types of mobile smart terminals include, but are not limited to, smart phones, tablet computers, vehicle-mounted terminals, handheld game consoles, and the like. A server may be a server cluster composed of one or more computing devices. It should be noted that, in some embodiments, the first client 110 is any first node device among the plurality of first node devices 140 , and the embodiment of the present application does not limit the form of the first client 110 . In some embodiments, the first client 110 calls the first blockchain through the software development kit (software development kit, SDK)/application programming interface (application programming interface, API) provided by the first blockchain to complete The blockchain business is not limited in the embodiment of this application.

The second client 120 has the function of operating the second blockchain, and can execute blockchain services by operating nodes on the second blockchain. Wherein, the second block chain is maintained by multiple second node devices 150 . It should be noted that the specific content of the second client 120 and the second blockchain is the same as that of the above-mentioned first client 110 and the first blockchain, so details will not be repeated here.

The verification node 130 has the function of communicating with the first client 110 and the second client 120, can receive the data sent by the first client 110 and the second client 120, process the received data, and send A client 110 and a second client 120 send data. In some embodiments, the check node 130 is implemented by a server or a server cluster composed of multiple servers. In some embodiments, the check node 130 is a node on the third blockchain. In some embodiments, the verification node 130 is a node in a verification cluster, and the verification cluster is a cluster based on a consensus mechanism, which is not limited in this embodiment of the present application.

Some optional functions of the first client 110, the second client 120, and the check node 130 are described below, wherein, in order to improve the readability of the embodiment, the implementation process is not described in detail here, please refer to Relevant descriptions in the following method embodiments.

In some embodiments, the second client 120 is used to receive the cross-chain transaction data, and the cross-chain transaction data is verified by the verification node 130 on the third blockchain, and the cross-chain transaction data If the verification is passed, execute the cross-chain transaction.

In some embodiments, the second client 120 is used to receive the cross-chain transaction data, and verify the cross-chain transaction data through the verification node 130 in the verification cluster, and verify the cross-chain transaction data If it passes, execute the cross-chain transaction, and the verification cluster is a cluster based on the consensus mechanism.

In some embodiments, the second client 120 is further configured to, based on the identification of the cross-chain transaction carried in the cross-chain transaction data, if the verification node 130 finds the A digital signature is used to execute the cross-chain transaction, and the digital signature indicates that the cross-chain transaction data has been verified.

In some embodiments, the verification node 130 is used to store the cross-chain transaction record of the cross-chain transaction, and the cross-chain transaction record indicates the transaction process and transaction execution status of the cross-chain transaction.

In some embodiments, the cross-chain transaction record includes the execution result of the cross-chain transaction, the execution result indicates that the cross-chain transaction has been successfully executed, or the execution result indicates that the cross-chain transaction has failed to execute.

In some embodiments, the check node 130 is also used for:

Receive a transaction query request sent by the third client, and the transaction query request indicates to query the cross-chain transaction record;

Based on the transaction query request, verify the third client, and if the third client is the first client 110 or the second client 120, send the cross-chain Transaction Record.

In some embodiments, the check node 130 is also used for:

receiving the cross-chain transaction request sent by the first client 110, the cross-chain transaction request indicating to execute the cross-chain transaction on the second block chain;

Based on the data stored in the verification node 130, the cross-chain transaction request is verified. If the cross-chain transaction request passes the verification, a confirmation notification is sent to the first client 110, and the confirmation notification indicates that the The first client 110 sends the cross-chain transaction data to the second client 120 .

In some embodiments, the verification node 130 is also used to perform the cross-chain transaction request based on the identity data of the first client 110 and the identity data of the second client 120 stored in the verification node 130 check.

In some embodiments, the identity data of the first client 110 includes the first identity certificate of the first client 110, and the first identity certificate indicates that the first client 110 has registered for the cross-chain service; the second client The identity data of the terminal 120 includes the second identity certificate of the second client 120, and the second identity certificate indicates that the second client 120 has registered for the cross-chain service.

In some embodiments, the check node 130 is also used for:

receiving the first registration request sent by the first client 110, verifying the identity of the first client 110, and generating the first identity certificate if the verification is passed, storing the first identity certificate, and The first registration request indicates that the first client 110 requests to register the cross-chain service;

receiving the second registration request sent by the second client 120, verifying the identity of the second client 120, and generating the second identity certificate if the verification is passed, storing the second identity certificate, and The second registration request indicates that the second client 120 requests to register for the cross-chain service.

In some embodiments, the identity data of the first client 110 also includes an authorization record of the first client 110, and the authorization record indicates the type of cross-chain operation for which the first client 110 has obtained permission.

In some embodiments, the verification node 130 is also used to receive the authorization request sent by the first client 110, store the authorization request, and the authorization request indicates the type of cross-chain operation performed on the second blockchain Corresponding cross-chain transactions; the second client 120 is also used to send an authorization notification to the verification node 130 based on the authorization request, and the authorization notification indicates that the first client 110 is approved to be on the second block chain Execute the cross-chain transaction corresponding to the cross-chain operation type; the verification node 130 is also used to receive the authorization notification and store the authorization notification.

In some embodiments, the second client 120 is also used for any of the following:

Querying the authorization request through the verification node 130, and sending the authorization notification to the verification node 130;

The authorization request sent by the verification node 130 is received, and the authorization notification is sent to the verification node 130 .

In some embodiments, the verification node 130 is also used to generate a digital signature of the cross-chain transaction and store the digital signature if the cross-chain transaction request passes the verification. The digital signature indicates that the cross-chain transaction data It has been verified.

The architecture of the first client 110 in the above-mentioned cross-chain transaction system 100 will be introduced below.

FIG. 2 is a schematic diagram of a structure of a first client 110 provided by an embodiment of the present application. It should be understood that FIG. 2 is only an exemplary schematic diagram showing a structure of the first client 110 , and the present application does not limit the division of various functions in the first client 110 . As shown in FIG. 2 , the functions of the first client 110 include but are not limited to: a business function 111 , a network function 112 , a certification function 113 and a storage function 114 .

Each function of the first client 110 is briefly described below:

The business function 111 is used to execute the business logic of the first blockchain. In some embodiments, the service function 111 includes an object layer, a data transmission layer, an identity verification analysis layer, and a data link layer. Among them, the object layer (also can be understood as the storage layer) is used to realize the addressability of cross-chain content, that is, the cross-chain content has a unique identifier; the data transmission layer is used to provide connection-oriented data flow support and reliability for cross-chain services. , flow control, multiplexing and other services to support the safe and reliable transmission of data between the two parties of the cross-chain transaction; the identity verification analysis layer is used to manage the node identity of each node on the first blockchain, such as the generation of node identity And verification, etc., to ensure the legality of the object of cross-chain transactions; the data link layer is used to maintain routing information to locate specific peer nodes, and is responsible for cross-chain addressing. In some embodiments, the service function 111 is also called a core function, which is not limited in this embodiment of the present application.

The network function 112 is used to provide a network communication function, and support nodes to perform data exchange, mutual cooperation, and collaborative work. In some embodiments, the network function 112 communicates with other blockchain clients (such as the second client) based on the RPC protocol. For example, the RPC protocol is the GRPC protocol (an open source RPC protocol). This application implements Examples are not limited to this. In some embodiments, the network function 112 communicates with the check node 130 based on a hypertext transfer protocol (hyper text transfer protocol, HTTP), which is not limited in this embodiment of the present application.

The certification function 113 is used to provide adaptive data verification services according to different blockchain types, to prove the legitimacy of cross-chain transaction data and to verify signatures (this part will be explained in subsequent embodiments, so it will not be repeated here) . Wherein, the block chain type includes but not limited to: bitcoin, ethereum (ethereum) and fabric, etc., which is not limited in this embodiment of the present application.

The storage function 114 is used to store various types of data, including but not limited to the cross-chain service registry, user certificates, cross-chain operation ledger, and client configuration data, etc., which is not limited in this embodiment of the application.

In addition, the functions of the first client 110 are not limited to the above-mentioned 111 to 114. In practical applications, more functions can be set according to the needs of users. The embodiment of the present application does not limit the function setting of the first client 110. It should be noted that the architecture of the second client 120 is the same as that of the first client 110 , so details will not be repeated here.

The structure of the verification node 130 in the above-mentioned cross-chain transaction system 100 will be introduced below.

FIG. 3 is a schematic diagram of an architecture of a check node 130 provided in an embodiment of the present application. It should be understood that FIG. 3 is only an exemplary structural diagram of the check node 130 , and the present application does not limit the division of various functions in the check node 130 . As shown in FIG. 3 , the functions of the verification node 130 include but not limited to: a verification function 131 , a network function 132 and a storage function 133 .

Each function of the check node 130 is briefly described below:

The verification function 131 is used to verify the cross-chain transaction request according to the cross-chain transaction request sent by the client. In some embodiments, the verification function 131 is also used to generate a digital signature of the cross-chain transaction if the cross-chain transaction request passes the verification. In some embodiments, the verification function 131 is also used to verify the identity of the client according to the registration request sent by the client, and generate an identity certificate of the client if the verification is passed. In some embodiments, the verification function 131 is also used to verify the client according to the transaction query request of the cross-chain transaction sent by the client, and provide the client with the cross-chain transaction if the verification is passed. Cross-chain transaction records of chain transactions.

The network function 132 is used to provide a network communication function, and support data exchange, mutual cooperation and collaborative work between the verification node 130 and the client. In some embodiments, the network function 132 implements network communication based on the RPC protocol and the HTTP protocol, which is not limited in this embodiment of the present application.

The storage function 133 is used to store various types of data, including but not limited to cross-chain transaction records of cross-chain transactions, digital signatures of cross-chain transactions, identity data of clients of both parties to cross-chain transactions, etc., which is not limited in this embodiment of the application. In some embodiments, the verification node 130 stores various types of data in the form of a database, a blockchain block, or a file to implement the storage function 133, which is not limited in this embodiment of the present application.

In addition, the functions of the check node 130 are not limited to the above-mentioned 131 to 133. In practical applications, more functions can be set according to the needs of users. The embodiment of the present application does not limit the function settings of the check node 130.

Through the above functions, the verification node provided by the embodiment of this application can verify the cross-chain transaction request of the cross-chain transaction when two clients conduct cross-chain transactions, and when the verification passes , to endorse this cross-chain transaction, so that the client that receives the cross-chain transaction data of this cross-chain transaction can verify the cross-chain transaction data of this cross-chain transaction through the verification node, so that the two Under the premise of direct communication between the two clients, the security of cross-chain transactions can be effectively improved.

It should be noted that, according to the above introduction to FIG. 1 , in some embodiments, the verification node 130 is a node on the third blockchain, and in other embodiments, the verification node 130 is a node in the verification cluster. of nodes. That is, the verification node 130 can be configured in the cross-chain transaction system 100 provided by the embodiment of the present application in various forms, for example, in the form of a single node, or in the form of a certain node on the blockchain, or in the form of , in the form of a certain node in the cluster based on the consensus mechanism, which is not limited in this embodiment of the present application.

Taking the verification node 130 as a node in the verification cluster and multiple nodes in the verification cluster jointly maintaining the third blockchain as an example, the architecture of the verification cluster will be introduced below.

FIG. 4 is a schematic diagram of an architecture of a verification cluster provided by an embodiment of the present application. It should be understood that FIG. 4 is only an exemplary structural diagram showing a verification cluster, and the present application does not limit the division of various functions in the verification cluster. As shown in FIG. 4 , the verification cluster 400 is a blockchain network composed of a plurality of verification nodes, and the plurality of verification nodes jointly maintain a third blockchain (also called a verification chain). Schematically, the architecture of the verification cluster 400 includes but not limited to the following five parts: contract layer 401 , consensus layer 402 , network layer 403 , security layer 404 and storage layer 405 .

The following briefly describes the functions of each part of the verification cluster:

The contract layer 401 is used to specify transaction methods and process details according to smart contracts. In some embodiments, the contract layer 401 includes identity management contracts, authority management contracts, and behavior supervision contracts. Among them, the identity management contract is responsible for managing the identity data of the client. For example, according to the registration request sent by the client, the identity of the client is verified. If the verification is passed, the identity certificate of the client is generated and recorded; authority management The contract is responsible for managing the cross-chain operation permissions of both parties to the cross-chain transaction, such as authorization, deauthorization, and permission verification; the behavior monitoring contract is responsible for recording the transaction process and transaction execution of the cross-chain transaction.

The consensus layer 402 is used to ensure the data consistency of each verification node in the verification cluster. In some embodiments, the user can select a suitable consensus algorithm according to the actual business scenario, and the embodiment of the present application does not limit the specific type of the consensus algorithm.

The network layer 403 is used to provide network communication functions, and support data exchange, mutual cooperation, and collaborative work between various verification nodes in the verification cluster. At the same time, the network layer 403 is also used to provide communication between each verification node in the verification cluster and the client. In some embodiments, the network layer 403 provides network communication based on P2P network, GRPC protocol and HTTP protocol, which is not limited in this embodiment of the present application.

The security layer 404 is used to ensure the security of the verification cluster through cryptographic algorithms. In some embodiments, cryptographic algorithms include but not limited to algorithms based on hash functions, digital signature algorithms, and asymmetric encryption algorithms, etc., which are not limited in this embodiment of the present application.

The storage layer 405 is used to store various types of data, including but not limited to the current state of each variable in the smart contract, all historical states of each variable, and the block file index (blockIndex) of the blockchain, etc. In some embodiments, the storage layer 405 includes multiple databases (database, DB) for storing various types of data, for example, multiple databases include but not limited to state database (stateDB) and history database (historyDB), etc., the present application The embodiment does not limit this.

In addition, the architecture of the verification cluster is not limited to the above 401 to 405. In practical applications, more functions can be set according to the needs of users. For example, the verification cluster can also include an incentive layer and an application layer, among which the incentive layer uses In order to provide certain incentives to encourage nodes to participate in the security verification of the blockchain, the application layer is used to realize various application scenarios in life. The embodiment of this application does not limit the architecture settings of the verification cluster.

Through the various parts shown in Figure 4 above, the verification cluster provided by the embodiment of this application can verify the cross-chain transaction request of the cross-chain transaction when two clients perform cross-chain transactions, and verify If it passes, it will endorse this cross-chain transaction, so that the client that receives the cross-chain transaction data of this cross-chain transaction can verify the cross-chain transaction data of this cross-chain transaction through the verification nodes in the verification cluster. Transaction data is verified to effectively improve the security of cross-chain transactions under the premise of direct communication between two clients. Further, since the verification cluster is a blockchain network composed of multiple verification nodes, and the plurality of verification nodes jointly maintain the third blockchain, therefore, the security of the data stored in the verification cluster is obtained. The guarantee is guaranteed, which further improves the security of cross-chain transactions.

Through the above-mentioned Figures 1 to 4, the cross-chain transaction system provided by the embodiment of the present application is introduced from the perspective of architecture. The deployment environment of the first client, the second client and the verification node in the cross-chain transaction system is as follows Make an introduction.

The embodiment of the present application provides a computing device that can be configured as the first client in the above-mentioned cross-chain transaction system (the second client is the same as the first client, and will not be repeated here). Schematically, refer to FIG. 5 , which is a schematic diagram of a hardware structure of a computing device provided by an embodiment of the present application. As shown in FIG. 5 , the computing device 500 includes a memory 501 , a processor 502 , a communication interface 503 and a bus 504 . Wherein, the memory 501 , the processor 502 , and the communication interface 503 are connected to each other through a bus 504 .

Memory 501 may be read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM) or other types that can store information and instructions It can also be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be programmed by a computer Any other medium accessed, but not limited to. The memory 501 can store at least one piece of program code. When the program code stored in the memory 501 is executed by the processor 502, the processor 502 and the communication interface 503 are used to execute the method for the first client to conduct a cross-chain transaction. The memory 501 can also store cross-chain service registry, user certificate, cross-chain operation account book, client configuration data, etc., which is not limited in this embodiment of the present application.

The processor 502 may be a network processor (network processor, NP), a central processing unit (central processing unit, CPU), a specific application integrated circuit (application-specific integrated circuit, ASIC) or an integrated circuit for controlling the execution of the program program of this application. circuit. The processor 502 may be a single-core (single-CPU) processor, or a multi-core (multi-CPU) processor. The number of the processor 502 may be one or more. The communication interface 503 uses a transceiver module such as a transceiver to implement communication between the computing device 500 and other devices or communication networks. For example, data can be acquired through the communication interface 503 .

Wherein, the memory 501 and the processor 502 may be provided separately, or may be integrated together.

Bus 504 may include pathways for transferring information between various components of computing device 500 (eg, memory 501 , processor 502 , communication interface 503 ).

It should be noted that, in some embodiments, the first client is independently deployed on a computing device. In some embodiments, the first client is deployed on a certain computing device on the first blockchain. In some embodiments, the first client can also be deployed in different environments in a distributed manner, for example, the first client can be logically divided into multiple parts, each part has different functions, and each part is deployed separately On a computing device, the embodiment of the present application does not limit the deployment manner of the first client.

The embodiment of the present application also provides a computing device that can be configured as a verification node in the above-mentioned cross-chain transaction system. Schematically, refer to FIG. 6 , which is a schematic diagram of a hardware structure of a computing device provided by an embodiment of the present application. As shown in FIG. 6 , the computing device 600 includes a memory 601 , a processor 602 , a communication interface 603 and a bus 604 . Wherein, the memory 601 , the processor 602 , and the communication interface 603 are connected to each other through a bus 604 .

Memory 601 may be read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM) or other types that can store information and instructions It can also be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be programmed by a computer Any other medium accessed, but not limited to. The memory 601 can store at least one piece of program code. When the program code stored in the memory 601 is executed by the processor 602, the processor 602 and the communication interface 603 are used to execute the verification node to perform cross-chain transaction method. The memory 601 can also store various types of data, including but not limited to cross-chain transaction records of cross-chain transactions, digital signatures of cross-chain transactions, identity data of clients of both parties to cross-chain transactions, etc., which are not limited in this embodiment of the present application.

The processor 602 may be a network processor (network processor, NP), a central processing unit (central processing unit, CPU), a specific application integrated circuit (application-specific integrated circuit, ASIC), or an integrated circuit for controlling the execution of the program program of this application. circuit. The processor 602 may be a single-core (single-CPU) processor, or a multi-core (multi-CPU) processor. The number of the processor 602 may be one or more. The communication interface 603 uses a transceiver module such as a transceiver to implement communication between the computing device 600 and other devices or communication networks. For example, data can be acquired through the communication interface 603 .

Wherein, the memory 601 and the processor 602 may be provided separately, or may be integrated together.

Bus 604 may include pathways for transferring information between various components of computing device 600 (eg, memory 601 , processor 602 , communication interface 603 ).

It should be noted that, in some embodiments, the check node is independently deployed on a computing device. In some embodiments, the verification node is deployed on a certain computing device in the verification cluster. In some embodiments, check nodes can also be deployed in different environments in a distributed manner. For example, check nodes can be logically divided into multiple parts, each part has different functions, and each part is deployed separately in a On the computing device, the embodiment of the present application does not limit the deployment mode of the verification node.

On the basis of introducing the system architecture of the cross-chain transaction method provided by the embodiment of the present application, the cross-chain transaction method provided by the embodiment of the present application will be exemplarily described below in conjunction with FIG. 7 .

Fig. 7 is a schematic flowchart of a cross-chain transaction method provided by the embodiment of the present application. As shown in FIG. 5, the cross-chain transaction method is applied to the system architecture 100 shown in FIG. As an example, this cross-chain transaction method is introduced. The cross-chain transaction method includes the following steps 701 to 714.

701. The first client sends a first registration request to the verification node, where the first registration request indicates that the first client requests to register for a cross-chain service.

In the embodiment of this application, the first client is a client of the first blockchain, and the first client executes blockchain services by operating nodes on the first blockchain, such as data upload and cross-chain communication etc., which are not limited in this embodiment of the present application. The first client’s request to register for cross-chain services means that the first client requests to perform cross-chain operations on blockchains other than the first blockchain, which can also be understood as the first client’s request to perform cross-chain operations on the verification node The identity registry for the service. The first registration request carries registration information of the first client. Optionally, the registration information of the first client includes but not limited to the following information: the network address of the first client, the identification (identification, ID) of the first client, the area of the first block chain to which the first client belongs The block chain identifier, the blockchain type of the first blockchain, the node certificates of each node on the first blockchain, and the smart contract identifier of the first blockchain are not limited in this embodiment of the present application.

In some embodiments, the first client sends the first registration request to the verification node according to the user-initiated registration behavior for the cross-chain service. Optionally, the first registration request also carries the identity certificate of the user who initiated the registration behavior, for example, the user's identity certificate includes a public key for identifying the user identity and a certificate of a certificate authority (certification authority, CA). Information such as digital signatures is not limited in this embodiment of the application.

It should be noted that the check node does not belong to the first block chain and the second block chain. In some embodiments, the check node is a node on the third blockchain. In some other embodiments, the verification node is a node in a verification cluster, and the verification cluster is a cluster based on a consensus mechanism, for example, the verification cluster is a blockchain network composed of multiple verification nodes, The multiple verification nodes jointly maintain the third blockchain, which is not limited in this embodiment of the present application.

In addition, when the verification node is a node in the verification cluster, in this step, the first client sends the first registration request to the verification cluster, and the gateway node of the verification cluster receives the first registration request, and distributed to the check nodes.

702. The verification node receives the first registration request, verifies the identity of the first client, and generates a first identity certificate if the verification passes, stores the first identity certificate, and the first identity certificate indicates The first client has registered for the cross-chain service.

In this embodiment of the application, the verification node receives the first registration request, verifies the identity of the first client based on the registration information carried in the first registration request, and generates a first The first identity certificate of the client, and store the first identity certificate as the identity data of the first client, and return the first identity certificate to the first client, that is, the verification node takes the first identity certificate as the first registration request The response is sent directly to the first client. In some embodiments, the verification node sends the serial number of the first identity certificate to the first client as a response to the first registration request, and the first client downloads the first identity certificate according to its own needs. This application The embodiment does not limit this. Optionally, the verification node stores the identity of the first client (for example, the network address or ID of the first client) corresponding to the first identity certificate, that is, the verification node can query the first identity according to the identity of the first client Certificate. Optionally, the first identity certificate includes information such as the registration information of the first client, the public key of the first client, and the digital signature of the CA, which is not limited in this embodiment of the present application.

In some embodiments, based on the registration information carried in the first registration request, the verification node performs format verification on the contents of the registration information, that is, judges whether the format of the contents in the registration information meets the requirements. If the verification is passed, the first identity certificate is generated.

In some embodiments, if the verification node finds that the first client has been registered after verifying the identity of the first client, the verification node determines that the verification fails and returns to the first client A first rejection message, so as to refuse to register the cross-chain service for the first client. For example, the first registration request carries the identity certificate of the user who initiated the registration behavior. After verifying the identity of the first client, the verification node finds that the identity of the user already exists in the cross-chain service registry of the verification node. certificate, the verification node determines that the verification fails, and returns a first rejection message to the first client.

In some embodiments, the check node stores the first registration request and a registration result of the first registration request, and the registration result includes registration success or registration failure. That is, the check node stores the registration record of the first client. For example, if the registration is successful, the registration record includes the first registration request and the first identity certificate; if the registration fails, the registration record includes the first registration request and the first rejection message. In addition, in some embodiments, when the verification node is a node in the verification cluster, and the verification cluster is a blockchain network composed of multiple verification nodes, the multiple verification nodes jointly maintain the third area When using a block chain, the above-mentioned registration records are stored on the third block chain by the verification cluster. Optionally, verifying the cluster operation identity management contract automatically executes step 702, which is not limited in this embodiment of the present application.

It should be noted that after the above step 701 and step 702, after the first client requests to register for the cross-chain service, the verification node generates the first identity certificate for it and stores it in the verification node, which is convenient for the subsequent first client. When a client initiates a cross-chain transaction for other clients, it verifies the first client to ensure the security of the cross-chain transaction.

703. The second client sends a second registration request to the check node, where the second registration request indicates that the second client requests to register for the cross-chain service.

In this embodiment of the application, the second client is a client of the second blockchain, and the second client performs blockchain services by operating nodes on the second blockchain, such as data upload and cross-chain communication etc., which are not limited in this embodiment of the present application. The second client’s request to register for cross-chain services means that the second client requests to perform cross-chain operations on blockchains other than the second blockchain, which can also be understood as the second client’s request to perform cross-chain operations on the verification node The identity registry for the service. The second registration request carries registration information of the second client. Optionally, the registration information of the second client includes but not limited to the following information: the network address of the second client, the ID of the second client, the blockchain identifier of the second blockchain to which the second client belongs, the The blockchain type of the second blockchain, the node certificates of each node on the second blockchain, and the smart contract identifier of the second blockchain are not limited in this embodiment of the present application.

In some embodiments, the second client sends the second registration request to the verification node according to the user-initiated registration behavior for the cross-chain service. Optionally, the second registration request also carries the identity certificate of the user who initiated the registration behavior. For example, the user’s identity certificate includes information such as the public key used to identify the user’s identity and the digital signature of the CA. The implementation of this application Examples are not limited to this.

In addition, when the verification node is a node in the verification cluster, in this step, the second client sends a second registration request to the verification cluster, and the gateway node of the verification cluster receives the second registration request, and distributed to the check nodes.

704. The verification node receives the second registration request, verifies the identity of the second client, and generates a second identity certificate if the verification passes, stores the second identity certificate, and the second identity certificate indicates The second client has registered for the cross-chain service.

In this embodiment of the application, the verification node receives the second registration request, verifies the identity of the second client based on the registration information carried in the second registration request, and generates a second The second identity certificate of the client, and store the second identity certificate as the identity data of the second client, and return the second identity certificate to the second client, that is, the verification node takes the second identity certificate as the second registration request The response is sent directly to the second client. In some embodiments, the verification node sends the serial number of the second identity certificate to the second client as a response to the second registration request, and the second client downloads the second identity certificate according to its own needs. This application The embodiment does not limit this. Optionally, the verification node stores the identity of the second client (such as the network address or ID of the second client) corresponding to the second identity certificate, that is, the verification node can query the second identity according to the identity of the second client Certificate. Optionally, the second identity certificate includes information such as the registration information of the second client, the public key of the second client, and the digital signature of the CA, which is not limited in this embodiment of the present application.

In some embodiments, based on the registration information carried in the second registration request, the verification node performs format verification on the contents of the registration information, that is, judges whether the format of the contents in the registration information meets the requirements. If the verification is passed, the second identity certificate is generated.

In some embodiments, if the verification node finds that the second client has been registered after verifying the identity of the second client, the verification node determines that the verification fails and returns to the second client The second rejection message is to refuse to register the cross-chain service for the first client. For example, the second registration request carries the identity certificate of the user who initiated the registration behavior. After verifying the identity of the second client, the verification node finds that the identity of the user already exists in the cross-chain service registry of the verification node. certificate, the verification node determines that the verification fails, and returns a second rejection message to the second client.

In some embodiments, the check node stores the second registration request and a registration result of the second registration request, and the registration result includes registration success or registration failure. That is, the check node stores the registration record of the second client. For example, if the registration is successful, the registration record includes the above-mentioned second registration request and the second identity certificate; if the registration fails, the registration record includes the above-mentioned second registration request and the second rejection message. In addition, in some embodiments, when the verification node is a node in the verification cluster, and the verification cluster is a blockchain network composed of multiple verification nodes, the multiple verification nodes jointly maintain the third area When using a block chain, the above-mentioned registration records are stored on the third block chain by the verification cluster. Optionally, verifying the cluster operation identity management contract automatically executes step 704, which is not limited in this embodiment of the present application.

After the above step 703 and step 704, after the second client requests to register for the cross-chain service, the verification node generates a second identity certificate for it and stores it in the verification node, so that the subsequent first client can initiate a second identity certificate for the second client. During the cross-chain transaction of the second client, the second client is verified to ensure the security of the cross-chain transaction.

It should be noted that, in the embodiment of the present application, the above step 701 to step 704 are executed in sequence from front to back. In some embodiments, steps 703 and 704 are performed while performing the above steps 701 and 702. In other embodiments, the above steps 703 and 704 are performed first, and then steps 701 and 702 are performed. The present application The embodiment does not limit the registration order of the first client and the second client.

In addition, after the above steps 701 to 704, both the first client and the second client have registered the cross-chain service with the verification node, and the verification node has issued identity certificates for both the first client and the second client , to prove that both clients have registered for the cross-chain service. In some embodiments, the process shown in the above steps 701 to 704 can also be understood as: the verification node provides identity management services for the first client and the second client. Through this identity management service, the identity data of the first client and the second client are stored, which ensures that when the first client and the second client perform cross-chain transactions, the identities of both parties are credible, thereby improving cross-chain transactions. security.

705. The first client sends an authorization request to the verification node, where the authorization request indicates to perform a cross-chain transaction corresponding to the cross-chain operation type on the second blockchain.

In the embodiment of this application, the type of cross-chain operation refers to the type of cross-chain operation involved when the client performs cross-chain transactions. Optionally, the authorization request carries the identity of the first client (such as the network address or ID of the first client), the identity of the second client of the second blockchain (such as the network address or ID of the second client) and the cross-chain The identification of the operation type and the like are not limited in this embodiment of the present application.

In some embodiments, cross-chain operations are divided into three categories, including ledger reading, chaincode reading, and chaincode writing. In some embodiments, cross-chain operations are divided into two categories, including ledger reading and full operations on chaincodes. It should be noted that the embodiment of the present application does not limit the classification of cross-chain operations, as long as the classified types of cross-chain operations are completely independent, and there is no relationship between upper and lower levels or inclusion. Of course, in some embodiments, Cross-chain operations are not classified, that is, cross-chain transactions corresponding to the above-mentioned cross-chain operation types indicate cross-chain transactions corresponding to all cross-chain operations, which is not limited in this embodiment of the present application.

706. The check node receives the authorization request, and stores the authorization request.

In this embodiment of the application, after receiving the authorization request sent by the first client, the verification node stores the authorization request as the identity data of the first client. In some embodiments, after receiving the authorization request, the verification node sends the authorization request to the second client, so that the second client can know in time that the first client requests to perform a cross-block on the second blockchain. chain transactions to improve the efficiency of cross-chain transactions. Optionally, the verification node stores the identifier of the first client corresponding to the authorization request, that is, the verification node can query the authorization request according to the identifier of the first client.

In some embodiments, the verification node receives the authorization request, verifies the identities of the first client and the second client, and returns a prompt message to the first client to prompt the identity of the second client if the verification fails. A client failed to verify the authorization request this time. For example, according to the identity of the first client and the identity of the second client carried in the authorization request, the verification node does not find the first identity certificate of the first client in the cross-chain service registry, or does not find the second client If the second identity certificate of the terminal or the identity certificates of the two clients are not found, it is determined that the verification fails, and a prompt message is returned to the first client.

707. The second client sends an authorization notification to the verification node based on the authorization request, and the authorization notification indicates that the first client is allowed to execute the cross-chain transaction corresponding to the cross-chain operation type on the second blockchain.

In this embodiment of the present application, based on the authorization request, the second client sends an authorization notification to the verification node if it agrees to this authorization.

In some embodiments, the second client queries the authorization request through the verification node, and sends the authorization notification to the verification node. For example, after the first client sends an authorization request to the verification node, it notifies the second client, and after receiving the notification, the second client queries the authorization request through the verification node. For another example, the second client can query information related to the second client on the service interface provided by the verification node, as long as the verification node receives an authorization request that requires the authorization of the second client, the second client You can query the authorization request.

In some embodiments, the second client receives the authorization request sent by the verification node, and sends the authorization notification to the verification node. That is, when the verification node receives an authorization request requiring authorization and consent from the second client, it sends the authorization request to the second client, and the second client responds to the received authorization request.

708. The check node receives the authorization notification, and stores the authorization notification.

In the embodiment of the present application, after receiving the authorization notification, the verification node stores the authorization notification as the identity data of the first client, and the authorization notification is the authorization result of the above authorization request. In some embodiments, the process of storing the above authorization request and authorization notification by the check node is also the process of storing the authorization records of the first client and the second client, which is not limited in this embodiment of the present application. Optionally, the verification node stores the identifier of the first client corresponding to the authorization notification, that is, the verification node can query the authorization notification according to the identifier of the first client. In some embodiments, when the check node is a node in a check cluster, and the check cluster is a blockchain network composed of multiple check nodes, the multiple check nodes jointly maintain the third blockchain When , the verification cluster stores the above-mentioned authorization record on the third block chain. Optionally, the cluster operation authority management contract is verified, and the above step 706 and step 708 are automatically executed, which is not limited in this embodiment of the present application.

In some embodiments, after receiving the authorization notification, the verification node sends the authorization notification to the first client, so that the first client can know in time that the second client has agreed to the first client's authorization in the second block. The cross-chain transaction corresponding to the type of cross-chain operation is executed on the chain.

After the above step 705 to step 708, the first client has obtained the authority to execute the cross-chain operation type of cross-chain transaction on the second blockchain, and the verification node has stored the authorization request of the first client and the authorization request of the second client. The authorization notification of the terminal to record the authorization of the cross-chain operation between the first client and the second client. In some embodiments, the process shown in the above step 705 to step 708 can also be understood as: the verification node provides rights management services for the first client and the second client. Through this authority management service, the authorization record of the client for the type of cross-chain operation is also stored as the identity data of the client, which ensures that when the first client and the second client perform cross-chain transactions, the cross-chain operations involved Authorization has been obtained, thereby improving the security of cross-chain transactions.

In addition, it should be noted that, in this embodiment of the application, the authorization request is a one-way authorization request, that is, in the above step 705 to step 708, the first client requests the second client to obtain and cross-chain operation type The authorization authority of the corresponding cross-chain transaction, after the second client agrees, the first client can execute the corresponding cross-chain transaction on the second blockchain, but the second client cannot execute it on the first blockchain For the corresponding cross-chain transaction, if the second client needs to execute the corresponding cross-chain transaction on the first blockchain, the second client needs to send an authorization request to the verification node in the same way as the first client , to obtain the authorization authority to execute the cross-chain transaction corresponding to the type of cross-chain operation on the first blockchain, which will not be repeated in this embodiment of the present application. In some embodiments, the first client and the second client send corresponding authorization requests to the verification node according to their own needs, so as to obtain authorization, which is not limited in this embodiment of the present application.

After the above steps 701 to 708, the verification node stores the first identity certificate of the first client, the second identity certificate of the second client, and the authorization records between the first client and the second client, which together constitute the The identity data of the first client and the identity data of the second client facilitate the verification of the cross-chain transaction when the subsequent cross-chain transaction is executed between the first client and the second client, thereby improving the security of the cross-chain transaction.

709. The first client sends a cross-chain transaction request for a cross-chain transaction to the verification node, and the cross-chain transaction request indicates to execute the cross-chain transaction on the second blockchain.

In this embodiment of the application, a cross-chain transaction refers to a transaction that performs cross-chain operations on the first blockchain and the second blockchain. For example, it can be to transfer the target amount of virtual resources in the first account on the first blockchain to the second account on the second blockchain, or to simultaneously modify the virtual resources on the first blockchain and the second blockchain. data. Here, the embodiment of this application does not limit the specific content of the cross-chain transaction. The cross-chain transaction request carries the identifiers of the clients of both parties to the cross-chain transaction (for example, the network addresses or IDs of both clients) and the identifier of the cross-chain transaction, which is used to uniquely identify this cross-chain trade.

In some embodiments, the cross-chain transaction request also carries the transaction type of the cross-chain transaction, the identification of the cross-chain operation type involved in the cross-chain transaction, the credible proof of the cross-chain transaction, and the The specific content and the like are not limited in this embodiment of the present application. Optionally, the cross-chain transaction request carries the above-mentioned various data in the form of metadata, which is not limited in this embodiment of the present application.

710. The verification node receives the cross-chain transaction request.

711. The verification node verifies the cross-chain transaction request based on the data stored in the verification node, and sends a confirmation notification to the first client if the cross-chain transaction request passes the verification, and the confirmation notification Instruct the first client to send the cross-chain transaction data of the cross-chain transaction to the second client.

In the embodiment of this application, after receiving the cross-chain transaction request, the verification node verifies the cross-chain transaction request according to the information carried in the cross-chain transaction request and the data stored in the verification node. If the verification is passed, a confirmation notification is sent to the first client, that is, the verification node sends the confirmation notification directly to the first client as the return of the cross-chain transaction request.

In some embodiments, the verification node verifies the cross-chain transaction request based on the identity data of the first client and the identity data of the second client stored in the verification node. The first client sends a confirmation notification. Optionally, the identity data of the first client includes the first identity certificate of the first client, the identity data of the second client includes the second identity certificate of the second client, and the verification node based on the If the identity certificates corresponding to the identity certificates of the two clients are found, the verification of the cross-chain transaction request is confirmed, A confirmation notification is sent to the first client, thereby ensuring the authenticity of the identities of both parties participating in this cross-chain transaction and improving the security of the cross-chain transaction. Optionally, the identity data of the first client also includes the authorization record of the first client, which indicates the type of cross-chain operation for which the first client has obtained permission, and the verification node based on the cross-chain transaction carried in the cross-chain transaction request The identification of the chain operation type and the identification of the first client. If the authorization record of the first client includes the authorization notice for this cross-chain operation type, it is determined that the cross-chain operation involved in this cross-chain transaction has been authorized. , thus improving the security of cross-chain transactions.

In some embodiments, when the verification of the cross-chain transaction request is passed, the verification node generates a digital signature of the cross-chain transaction, stores the digital signature, and the digital signature indicates that the cross-chain transaction data has passed the verification. Wherein, the digital signature is stored corresponding to the identification of the cross-chain transaction. By generating the digital signature of this cross-chain transaction, an endorsement signature is carried out for this cross-chain transaction, which also provides a guarantee for the security of this cross-chain transaction, so that the subsequent second client can receive this cross-chain When transacting cross-chain transaction data, the cross-chain transaction data is verified by verification nodes to improve the security of cross-chain transactions.

712. The first client receives the confirmation notification.

After the above step 709 to step 712, after receiving the cross-chain transaction request of the cross-chain transaction sent by the first client, the verification node verifies the cross-chain transaction request. The first client returns a confirmation notification. In some embodiments, the process shown in the above step 709 to step 712 can also be understood as: the verification node provides rights management services for the first client and the second client, through the rights management service, the client initiated Cross-chain transaction requests are verified to ensure the security of cross-chain transactions. In some embodiments, when the check node is a node in a check cluster, and the check cluster is a blockchain network composed of multiple check nodes, the multiple check nodes jointly maintain the third blockchain , the above step 710 and step 711 are automatically executed by verifying the cluster operation authority management contract, which is not limited in this embodiment of the present application.

713. The first client sends the cross-chain transaction data of the cross-chain transaction to the second client.

In this embodiment of the application, after receiving the confirmation notification sent by the verification node, the first client sends the cross-chain transaction data of the cross-chain transaction to the second client, and the cross-chain transaction data indicates the cross-chain transaction details. For example, if the cross-chain transaction is to transfer the target amount of virtual resources in the first account on the first block chain to the second account on the second block chain, the cross-chain transaction data includes the account of the resource transfer party, The account of the resource transferee and the amount of resource transfer. Wherein, the resource-transferring account is the first account, the resource-transferring account is the second account, and the resource transfer amount is the target amount. For another example, if the cross-chain transaction is to synchronously modify the data on the first block chain and the second block chain, then the cross-chain transaction data includes the location of the data to be modified on the first block chain, the second area The location of the data to be modified on the block chain, the modified data of the data to be modified on the first block chain, and the modified data of the data to be modified on the second block chain are not limited in this embodiment of the present application.

In some embodiments, the cross-chain transaction data carries an identifier of the cross-chain transaction, and the identifier of the cross-chain transaction is used to uniquely identify the cross-chain transaction. By carrying the identification of the cross-chain transaction in the cross-chain transaction data, it is convenient for the second client receiving the cross-chain transaction data to verify the cross-chain transaction data through the verification node according to the identification of the cross-chain transaction. In the case of passing the verification, the cross-chain transaction is executed to improve the security of the cross-chain transaction.

714. The second client receives the cross-chain transaction data, verifies the cross-chain transaction data through the verification node, and executes the cross-chain transaction when the cross-chain transaction data passes the verification.

In the embodiment of this application, after receiving the cross-chain transaction data, the second client verifies the cross-chain transaction data through the verification node based on the cross-chain transaction identifier carried in the cross-chain transaction data, If the verification is passed, the cross-chain transaction is executed on the second blockchain.

In some embodiments, based on the identification of the cross-chain transaction carried by the cross-chain transaction data, the second client executes the cross-chain transaction if the digital signature corresponding to the identification of the cross-chain transaction is found from the verification node. trade. The cross-chain transaction data is verified by querying the digital signature, which improves the security of the cross-chain transaction.

In some embodiments, after receiving the cross-chain transaction data, the second client verifies the cross-chain transaction data through the verification node. The cross-chain transaction data is verified, and the cross-chain transaction is executed after the legality of the cross-chain transaction data is verified and signed. In some embodiments, if the second client passes the verification of the cross-chain transaction data through the verification node, but the second client fails to pass the verification of the cross-chain transaction data, then this cross-chain transaction will not be executed, and the Rollback operation. In other embodiments, if the second client fails to verify the cross-chain transaction data through the verification node, but the second client passes the verification of the cross-chain transaction data, the cross-chain transaction will not be executed, and Perform a rollback operation. That is, in this process, the second client not only needs to verify the cross-chain transaction data through the verification node, but also needs to verify the cross-chain transaction data by itself. Execute the cross-chain transaction, thereby greatly improving the security of the cross-chain transaction.

After the above step 713 and step 714, the first client directly sends the cross-chain transaction data of the cross-chain transaction to the second client, which avoids the risk of centralization. Further, when the second client receives the cross-chain transaction data, The cross-chain verification data is verified by the verification node, so as to effectively improve the security of cross-chain transactions under the premise of direct communication between two clients.

In some embodiments, the verification node stores the cross-chain transaction record of the cross-chain transaction, and the cross-chain transaction record indicates the transaction process and transaction execution status of the cross-chain transaction. Optionally, the cross-chain transaction record includes the execution result of the cross-chain transaction, and the execution result indicates that the cross-chain transaction has been executed successfully, or the execution result indicates that the execution of the cross-chain transaction failed. Wherein, after executing the cross-chain transaction, the second client returns the execution result of the cross-chain transaction to the verification node, and the verification node stores the execution result after receiving the execution result of the cross-chain transaction. Optionally, the cross-chain transaction record also includes the time when the cross-chain transaction occurred, the information of both parties to the cross-chain transaction, and transaction execution parameters, etc., which are not limited in this embodiment of the present application. By storing the cross-chain transaction record of the cross-chain transaction in the verification node, it can provide rights confirmation and accountability services for illegal cross-chain transactions, thereby improving the security of cross-chain transactions.

In some embodiments, only the participants of the cross-chain transaction have query authority for the cross-chain transaction record stored in the verification node, which can ensure the security of the cross-chain transaction record and prevent the cross-chain transaction record from being obtained illegally. Schematically, taking the third client wanting to query the cross-chain transaction record of the cross-chain transaction as an example, the verification node receives the transaction query request sent by the third client, and the transaction query request indicates to query the cross-chain transaction record Cross-chain transaction records; the verification node verifies the third client based on the transaction query request, and if the third client is the first client or the second client, the third client The client sends the cross-chain transaction record. Optionally, the verification node determines whether the third client is the first client or the second client according to the identity certificate of the third client, which is not limited in this embodiment of the present application. In some embodiments, when the check node is a node in a check cluster, and the check cluster is a blockchain network composed of multiple check nodes, the multiple check nodes jointly maintain the third blockchain , the above-mentioned steps of storing cross-chain transaction records and verifying the third client will be executed automatically by verifying the cluster operation behavior supervision contract, which is not limited in the embodiment of this application.

To sum up, in the cross-chain transaction method provided by the embodiment of this application, the cross-chain transaction data of the cross-chain transaction can be directly sent between two clients, thereby avoiding the risk of centralization. Further, the cross-chain transaction received The client of the data can verify the cross-chain transaction data through the verification node, and execute this cross-chain transaction after the verification is passed, so that under the premise of direct communication between two clients , effectively improving the security of cross-chain transactions. Furthermore, the cross-chain transaction method is based on the interaction between the client and the business blockchain, so that different types of blockchains can be adapted, effectively expanding the scope of application of the cross-chain transaction method.

The above embodiment shown in FIG. 7 illustrates the specific implementation of the cross-chain transaction method according to the cross-chain transaction system shown in FIG. 1 . Referring to FIG. 8, the cross-chain transaction method provided by the embodiment of the present application will be illustrated by taking the verification node as a node in the verification cluster shown in FIG. 4 as an example.

Fig. 8 is a schematic diagram of a cross-chain transaction system provided by an embodiment of the present application. As shown in Fig. 8, the cross-chain transaction system includes a first client of the first blockchain and a second client of the second blockchain Terminal and verification cluster, multiple verification nodes in the verification cluster jointly maintain the third block chain. Among them, the verification cluster is used to verify the identity of the client according to the registration request of the client, and issue an identity certificate for the client; the verification cluster is also used to receive the authorization request sent by the client and store the corresponding authorization record ; The verification cluster is also used to verify the cross-chain transaction request when receiving the cross-chain transaction request sent by the client, and notify the client to send Cross-chain transaction data; the verification cluster is also used to store cross-chain transaction records of cross-chain transactions; etc., the role of the verification cluster is the same as that of the verification nodes shown in Figure 7 above, so here No longer.

In addition, the specific execution steps of the cross-chain transaction method through interaction between the first client, the second client, and the verification cluster are the same as those shown in Figure 7 above, so they will not be repeated here. Among them, since the verification cluster is a blockchain network composed of multiple verification nodes, the verification cluster will store the identity data of the first client, the identity data of the second client, and the cross-chain transaction records of cross-chain transactions, etc. stored on the third blockchain. Optionally, the verification cluster runs the identity management contract, authority management contract and behavior supervision contract, and automatically executes the steps performed by the verification node in the embodiment shown in Figure 7 above, which is not limited in this embodiment of the application.

In the cross-chain transaction method provided by the embodiment shown in Figure 8, the cross-chain transaction data of the cross-chain transaction can be directly sent between two clients, thereby avoiding the risk of centralization. Further, the cross-chain transaction data received The client can verify the cross-chain transaction data by verifying the verification nodes in the cluster, and execute this cross-chain transaction after the verification is passed, so that the data can be directly exchanged between two clients. Under the premise of communication, the security of cross-chain transactions is effectively improved. Furthermore, the cross-chain transaction method is based on the interaction between the client and the business blockchain, so that different types of blockchains can be adapted, effectively expanding the scope of application of the cross-chain transaction method. Moreover, since the verification cluster is a blockchain network composed of multiple verification nodes, and the multiple verification nodes jointly maintain the third blockchain, the security of the data stored in the verification cluster is guaranteed. guarantee, thus further improving the security of cross-chain transactions.

Fig. 9 is a schematic structural diagram of a cross-chain transaction device provided by an embodiment of the present application. The cross-chain transaction device 900 shown in FIG. 9 realizes, for example, the function of the first client in the cross-chain transaction method shown in FIG. 7 . As shown in FIG. 9 , the cross-chain transaction device 900 includes a sending module 901 and a receiving module 902 .

Sending module 901, configured to send a cross-chain transaction request to a verification node, the cross-chain transaction request indicates to perform a cross-chain transaction on the second blockchain, and the verification node does not belong to the first blockchain and the second block chain;

The receiving module 902 is configured to receive a confirmation notification sent by the verification node, the confirmation notification instructing the first client to send the cross-chain transaction data of the cross-chain transaction to the second client;

The sending module 901 is further configured to send the cross-chain transaction data to the second client.

In some embodiments, the sending module 901 is further configured to send a first registration request to the verification node, where the first registration request indicates that the first client requests to register for the cross-chain service.

In some embodiments, the sending module 901 is further configured to send an authorization request to the verification node, where the authorization request indicates to perform a cross-chain transaction corresponding to a cross-chain operation type on the second blockchain.

It should be noted that when the cross-chain transaction device 900 provided in the above-mentioned embodiment performs cross-chain transactions, it only uses the division of the above-mentioned functional modules as an example. In practical applications, the above-mentioned functions can be assigned to different function modules according to needs Module completion means that the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the cross-chain transaction device and cross-chain transaction method embodiment provided by the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, and will not be repeated here.

Fig. 10 is a schematic structural diagram of a cross-chain transaction device provided by the embodiment of the present application. The cross-chain transaction device 1000 shown in FIG. 10 realizes, for example, the function of the second client in the cross-chain transaction method shown in FIG. 7 . As shown in FIG. 10 , the cross-chain transaction device 1000 includes an execution module 1001 .

The execution module 1001 is used to receive the cross-chain transaction data of the cross-chain transaction sent by the first client, and verify the cross-chain transaction data through the verification node, and if the verification of the cross-chain transaction data passes Next, the cross-chain transaction is executed, and the verification node does not belong to the first block chain and the second block chain.

In some embodiments, the execution module 1001 is configured to verify the cross-chain transaction data through the verification node on the third blockchain.

In some embodiments, the execution module 1001 is configured to verify the cross-chain transaction data through the verification node in the verification cluster, and the verification cluster is a cluster based on a consensus mechanism.

In some embodiments, the execution module 1001 is configured to, based on the identification of the cross-chain transaction carried in the cross-chain transaction data, if the digital signature corresponding to the identification of the cross-chain transaction is found from the verification node, Execute the cross-chain transaction, and the digital signature indicates that the cross-chain transaction data has been verified.

In some embodiments, the device further includes a sending module, configured to send a second registration request to the verification node, where the second registration request indicates that the second client requests to register for the cross-chain service.

In some embodiments, the sending module is further configured to send an authorization notification to the verification node based on the authorization request of the first client, and the authorization request indicates that the cross-chain operation type corresponding to the second block chain is executed on the second block chain. For a cross-chain transaction, the authorization notification indicates that the first client is allowed to perform a cross-chain transaction corresponding to the cross-chain operation type on the second blockchain.

In some embodiments, the sending module is also used for any of the following:

Querying the authorization request through the verification node, and sending the authorization notification to the verification node;

receiving the authorization request sent by the check node, and sending the authorization notification to the check node.

It should be noted that when the cross-chain transaction device 1000 provided by the above-mentioned embodiment performs cross-chain transactions, it only uses the division of the above-mentioned functional modules as an example. In practical applications, the above-mentioned functions can be assigned to different function modules according to needs Module completion means that the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the cross-chain transaction device and cross-chain transaction method embodiment provided by the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, and will not be repeated here.

Fig. 11 is a schematic structural diagram of a cross-chain transaction device provided by the embodiment of the present application. The cross-chain transaction device 1100 shown in FIG. 11 realizes, for example, the function of a verification node in the cross-chain transaction method shown in FIG. 7 . As shown in FIG. 11 , the cross-chain transaction device 1100 includes a receiving module 1101 and a verification module 1102 .

The receiving module 1101 is configured to receive a cross-chain transaction request for a cross-chain transaction sent by the first client, and the cross-chain transaction request indicates that the cross-chain transaction is executed on the second blockchain;

The verification module 1102 is configured to verify the cross-chain transaction request based on the data stored in the verification node, and send a confirmation notification to the first client if the cross-chain transaction request passes the verification. The confirmation notification instructs the first client to send the cross-chain transaction data to the second client.

In some embodiments, the check node belongs to a third blockchain.

In some embodiments, the verification node belongs to a verification cluster, and the verification cluster is a cluster based on a consensus mechanism.

In some embodiments, the device also includes a storage module for:

The cross-chain transaction record of the cross-chain transaction is stored, and the cross-chain transaction record indicates the transaction process and transaction execution status of the cross-chain transaction.

In some embodiments, the cross-chain transaction record includes the execution result of the cross-chain transaction, the execution result indicates that the cross-chain transaction has been successfully executed, or the execution result indicates that the cross-chain transaction has failed to execute.

In some embodiments, the receiving module 1101 is also used to receive a transaction query request sent by the third client, and the transaction query request indicates to query the cross-chain transaction record; the verification module 1102 is also used to, based on the transaction query request, Verifying the third client, and sending the cross-chain transaction record to the third client if the third client is the first client or the second client.

In some embodiments, the verification module 1102 is further configured to verify the cross-chain transaction request based on the identity data of the first client and the identity data of the second client stored in the verification node.

In some embodiments, the identity data of the first client includes the first identity certificate of the first client, and the first identity certificate indicates that the first client has registered for the cross-chain service; the identity data of the second client includes the The second identity certificate of the second client, where the second identity certificate indicates that the second client has registered for the cross-chain service.

In some embodiments, the checking module 1102 is also used for:

Receive the first registration request sent by the first client, verify the identity of the first client, and generate the first identity certificate if the verification is passed, store the first identity certificate, and the first registration The request indicates that the first client requests to register the cross-chain service;

Receive the second registration request sent by the second client, verify the identity of the second client, and generate the second identity certificate if the verification is passed, store the second identity certificate, and the second registration The request indicates that the second client requests to register the cross-chain service.

In some embodiments, the identity data of the first client further includes an authorization record of the first client, and the authorization record indicates the type of cross-chain operation for which the first client has obtained permission.

In some embodiments, the storage module is also used to:

Receive the authorization request sent by the first client, store the authorization request, and the authorization request indicates to execute the cross-chain transaction corresponding to the cross-chain operation type on the second blockchain;

receiving an authorization notification sent by the second client, storing the authorization notification, the authorization notification indicating that the first client is allowed to perform a cross-chain transaction corresponding to the cross-chain operation type on the second block chain.

In some embodiments, the storage module is also used to:

In the case that the cross-chain transaction request is verified and passed, a digital signature of the cross-chain transaction is generated and stored, and the digital signature indicates that the cross-chain transaction data has passed the verification.

It should be noted that when the cross-chain transaction device 1100 provided by the above-mentioned embodiment performs cross-chain transactions, it only uses the division of the above-mentioned functional modules as an example. In practical applications, the above-mentioned functions can be assigned to different function modules according to needs Module completion means that the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the cross-chain transaction device and cross-chain transaction method embodiment provided by the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, and will not be repeated here.

In the present invention, the terms "first" and "second" are used to distinguish the same or similar items with basically the same function and function. It should be understood that "first", "second" and "nth" There are no logical or timing dependencies, nor are there restrictions on quantity or order of execution. It should also be understood that although the following description uses the terms first, second, etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first client could be termed a second client, and, similarly, a second client could be termed a first client, without departing from the scope of the various described examples. Both the first client and the second client may be clients, and in some cases, separate and distinct clients.

The meaning of the term "at least one" in the present invention refers to one or more, the meaning of the term "multiple" in the present invention refers to two or more, for example, a plurality of clients refers to two or more client.

The above description is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person familiar with the technical field can easily think of various equivalent modifications within the technical scope disclosed in the present invention Or replacement, these modifications or replacements should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a program product. The program product includes one or more program instructions. When the program instructions are loaded and executed on the computing device, the processes or functions according to the embodiments of the present invention will be generated in whole or in part.

Those of ordinary skill in the art can understand that all or part of the steps for implementing the above-mentioned embodiments can be completed by hardware, and can also be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned The storage medium can be read-only memory, magnetic disk or optical disk and so on.

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still understand the foregoing The technical solutions recorded in each embodiment are modified, or some of the technical features are replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.

Claims (40)

1. A cross-chain transaction system, characterized in that the cross-chain transaction system includes a first client of the first block chain, a second client of the second block chain, and a verification node;

   The first client is configured to send cross-chain transaction data of the cross-chain transaction to the second client;

   The second client is used to receive the cross-chain transaction data, verify the cross-chain transaction data through the verification node, and execute the cross-chain transaction data if the cross-chain transaction data is verified. For the cross-chain transaction, the verification node does not belong to the first block chain and the second block chain.
2. The system according to claim 1, characterized in that,

   The second client is used to receive the cross-chain transaction data, verify the cross-chain transaction data through the verification node on the third block chain, and verify the cross-chain transaction data in the cross-chain transaction data If the verification is passed, execute the cross-chain transaction.
3. The system according to claim 1, characterized in that,

   The second client is used to receive the cross-chain transaction data, verify the cross-chain transaction data by verifying the verification node in the cluster, and verify the cross-chain transaction data after passing the verification In the case of , the cross-chain transaction is executed, and the verification cluster is a cluster based on a consensus mechanism.
4. A system according to any one of claims 1 to 3, characterized in that,

   The second client is further configured to, based on the identification of the cross-chain transaction carried in the cross-chain transaction data, if the digital signature corresponding to the identification of the cross-chain transaction is found from the verification node , execute the cross-chain transaction, and the digital signature indicates that the cross-chain transaction data has passed the verification.
5. A system according to any one of claims 1 to 4, characterized in that,

   The verification node is used to store the cross-chain transaction record of the cross-chain transaction, and the cross-chain transaction record indicates the transaction process and transaction execution status of the cross-chain transaction.
6. The system according to claim 5, wherein the cross-chain transaction record includes the execution result of the cross-chain transaction, the execution result indicates that the cross-chain transaction has been successfully executed, or the execution result indicates The execution of the cross-chain transaction failed.
7. The system according to claim 5, characterized in that,

   The check node is also used for:

   receiving a transaction query request sent by a third client, the transaction query request indicating to query the cross-chain transaction records;

   Based on the transaction query request, verify the third client, and if the third client is the first client or the second client, send a message to the third client The cross-chain transaction records.
8. A system according to any one of claims 1 to 7, characterized in that,

   The check node is also used for:

   receiving a cross-chain transaction request sent by the first client, the cross-chain transaction request indicating that the cross-chain transaction is executed on the second block chain;

   Based on the data stored in the verification node, the cross-chain transaction request is verified, and if the verification of the cross-chain transaction request passes, a confirmation notification is sent to the first client, and the confirmation The notification instructs the first client to send the cross-chain transaction data to the second client.
9. The system of claim 8, wherein

   The verification node is further configured to verify the cross-chain transaction request based on the identity data of the first client and the identity data of the second client stored in the verification node.
10. The system of claim 9, wherein

    The identity data of the first client includes a first identity certificate of the first client, and the first identity certificate indicates that the first client has registered for a cross-chain service;

    The identity data of the second client includes a second identity certificate of the second client, and the second identity certificate indicates that the second client has registered for a cross-chain service.
11. The system of claim 10, wherein

    The check node is also used for:

    receiving the first registration request sent by the first client, verifying the identity of the first client, and generating the first identity certificate if the verification is passed, and storing the first identity certificate, The first registration request indicates that the first client requests to register a cross-chain service;

    receiving a second registration request sent by the second client, verifying the identity of the second client, and generating the second identity certificate if the verification is passed, and storing the second identity certificate, The second registration request indicates that the second client requests to register for a cross-chain service.
12. A system according to any one of claims 9 to 11, characterized in that,

    The identity data of the first client further includes an authorization record of the first client, and the authorization record indicates the type of cross-chain operation for which the first client has obtained permission.
13. The system of claim 12 wherein,

    The verification node is further configured to receive the authorization request sent by the first client, store the authorization request, and the authorization request indicates that the execution on the second block chain corresponds to the cross-chain operation type cross-chain transactions;

    The second client is further configured to send an authorization notification to the verification node based on the authorization request, and the authorization notification indicates that the first client is allowed to perform the same transaction as the verification node on the second blockchain. Cross-chain transactions corresponding to the above cross-chain operation types;

    The verification node is further configured to receive the authorization notification and store the authorization notification.
14. The system according to claim 13, wherein the second client is also used for any of the following:

    Querying the authorization request through the verification node, and sending the authorization notification to the verification node;

    receiving the authorization request sent by the verification node, and sending the authorization notification to the verification node.
15. A system according to any one of claims 8 to 14, characterized in that,

    The verification node is also used to generate a digital signature of the cross-chain transaction when the verification of the cross-chain transaction request is passed, and store the digital signature, and the digital signature indicates the cross-chain transaction data It has been verified.
16. A cross-chain transaction method, characterized in that it is executed by the first client of the first block chain in the cross-chain transaction system, and the cross-chain transaction system also includes the second client of the second block chain and verification node, the method comprising:

    Send a cross-chain transaction request to the verification node, the cross-chain transaction request indicates to perform a cross-chain transaction on the second blockchain, and the verification node does not belong to the first blockchain and the the second blockchain;

    receiving a confirmation notification sent by the verification node, the confirmation notification instructing the first client to send the cross-chain transaction data of the cross-chain transaction to the second client;

    Send the cross-chain transaction data to the second client.
17. The method according to claim 16, further comprising:

    Sending a first registration request to the verification node, where the first registration request indicates that the first client requests to register for a cross-chain service.
18. The method according to claim 16 or 17, wherein the method further comprises:

    An authorization request is sent to the verification node, where the authorization request indicates that a cross-chain transaction corresponding to a cross-chain operation type is executed on the second block chain.
19. A cross-chain transaction method, characterized in that it is executed by the second client of the second block chain in the cross-chain transaction system, and the cross-chain transaction system also includes the first client of the first block chain and the verification node, the method comprising:

    Receive the cross-chain transaction data of the cross-chain transaction sent by the first client, verify the cross-chain transaction data through the verification node, and execute For the cross-chain transaction, the verification node does not belong to the first block chain and the second block chain.
20. The method according to claim 19, wherein the verification of the cross-chain transaction data by the verification node includes:

    The cross-chain transaction data is verified by the verification node on the third block chain.
21. The method according to claim 19, wherein the verification of the cross-chain transaction data by the verification node includes:

    The cross-chain transaction data is verified by the verification nodes in the verification cluster, and the verification cluster is a cluster based on a consensus mechanism.
22. The method according to any one of claims 19 to 21, wherein the cross-chain transaction data is verified by the verification node, and when the cross-chain transaction data verification passes , execute the cross-chain transaction, including:

    Based on the identification of the cross-chain transaction carried in the cross-chain transaction data, if the digital signature corresponding to the identification of the cross-chain transaction is found from the verification node, the cross-chain transaction is executed, and the The digital signature indicates that the cross-chain transaction data has been verified.
23. The method according to any one of claims 19 to 22, further comprising:

    Sending a second registration request to the verification node, where the second registration request indicates that the second client requests to register for the cross-chain service.
24. The method according to any one of claims 19 to 23, further comprising:

    Based on the authorization request of the first client, an authorization notification is sent to the verification node, the authorization request indicates that a cross-chain transaction corresponding to a cross-chain operation type is performed on the second block chain, and the authorization notification indicating that the first client is allowed to perform a cross-chain transaction corresponding to the cross-chain operation type on the second block chain.
25. The method according to claim 24, wherein the sending an authorization notification to the verification node based on the authorization request of the first client includes any of the following:

    Querying the authorization request through the verification node, and sending the authorization notification to the verification node;

    receiving the authorization request sent by the verification node, and sending the authorization notification to the verification node.
26. A cross-chain transaction method, characterized in that it is executed by a verification node in a cross-chain transaction system, and the cross-chain transaction system also includes a first client of the first blockchain and a second client of the second blockchain. client, the method includes:

    receiving a cross-chain transaction request for a cross-chain transaction sent by the first client, the cross-chain transaction request indicating that the cross-chain transaction is executed on the second block chain;

    Based on the data stored in the verification node, the cross-chain transaction request is verified, and if the verification of the cross-chain transaction request passes, a confirmation notification is sent to the first client, and the confirmation The notification instructs the first client to send the cross-chain transaction data to the second client.
27. The method according to claim 26, wherein the check node belongs to a third blockchain.
28. The method according to claim 26, wherein the verification node belongs to a verification cluster, and the verification cluster is a cluster based on a consensus mechanism.
29. The method according to any one of claims 26 to 28, further comprising:

    The cross-chain transaction record of the cross-chain transaction is stored, and the cross-chain transaction record indicates the transaction process and transaction execution status of the cross-chain transaction.
30. The method according to claim 29, wherein the cross-chain transaction record includes the execution result of the cross-chain transaction, the execution result indicates that the cross-chain transaction has been successfully executed, or the execution result indicates The execution of the cross-chain transaction failed.
31. The method according to claim 29, further comprising:

    receiving a transaction query request sent by a third client, the transaction query request indicating to query the cross-chain transaction records;

    Based on the transaction query request, verify the third client, and if the third client is the first client or the second client, send a message to the third client The cross-chain transaction records.
32. The method according to any one of claims 26 to 31, wherein the verification of the cross-chain transaction request based on the data stored in the verification node includes:

    The cross-chain transaction request is verified based on the identity data of the first client and the identity data of the second client stored in the verification node.
33. The method of claim 32, wherein

    The identity data of the first client includes a first identity certificate of the first client, and the first identity certificate indicates that the first client has registered for a cross-chain service;

    The identity data of the second client includes a second identity certificate of the second client, and the second identity certificate indicates that the second client has registered for a cross-chain service.
34. The method according to claim 33, further comprising:

    receiving the first registration request sent by the first client, verifying the identity of the first client, and generating the first identity certificate if the verification is passed, and storing the first identity certificate, The first registration request indicates that the first client requests to register a cross-chain service;

    receiving the second registration request sent by the second client, verifying the identity of the second client, and generating the second identity certificate if the verification is passed, and storing the second identity certificate, The second registration request indicates that the second client requests to register for a cross-chain service.
35. The method according to any one of claims 32 to 34, wherein the identity data of the first client further includes an authorization record of the first client, and the authorization record indicates that the first client has acquired The type of cross-chain operation to the authority.
36. The method according to claim 35, further comprising:

    receiving the authorization request sent by the first client, storing the authorization request, the authorization request indicating that the cross-chain transaction corresponding to the cross-chain operation type is executed on the second block chain;

    receiving an authorization notification sent by the second client, and storing the authorization notification, the authorization notification indicating that the first client is allowed to perform a cross-chain operation corresponding to the cross-chain operation type on the second block chain; chain transactions.
37. The method according to any one of claims 26 to 36, further comprising:

    When the verification of the cross-chain transaction request is passed, a digital signature of the cross-chain transaction is generated, and the digital signature is stored, and the digital signature indicates that the cross-chain transaction data has passed the verification.
38. A computing device, characterized in that the computing device includes a processor and a memory, the memory is used to store at least one piece of program code, and the at least one piece of program code is loaded and executed by the processor as claimed in claim 16 to right The cross-chain transaction method according to any one of claim 18, or the cross-chain transaction method according to any one of claims 19 to 25, or any one of claims 26 to 37 The described cross-chain transaction method.
39. A computer-readable storage medium, characterized in that the computer-readable storage medium is used to store at least one piece of program code, and the at least one piece of program code is used to execute any one of claims 16 to 18. The cross-chain transaction method, or the cross-chain transaction method according to any one of claims 19 to 25, or the cross-chain transaction method according to any one of claims 26 to 37.
40. A computer program product, characterized in that, when the computer program product is run on a computer, the computer is made to execute the cross-chain transaction method according to any one of claims 16 to 18, or, as The cross-chain transaction method described in any one of claims 19 to 25, or the cross-chain transaction method described in any one of claims 26 to 37.

Images