CN112714158B

CN112714158B - Transaction processing method, relay network, cross-link gateway, system, medium and equipment

Info

Publication number: CN112714158B
Application number: CN202011521609.5A
Authority: CN
Inventors: 王诗鈞; 徐石成; 何光宇
Original assignee: Neusoft Corp
Current assignee: Neusoft Corp
Priority date: 2020-12-21
Filing date: 2020-12-21
Publication date: 2023-11-17
Anticipated expiration: 2040-12-21
Also published as: CN112714158A

Abstract

The present disclosure relates to a transaction processing method, a relay network, a cross-link gateway, a system, a medium and a device, and relates to the technical field of electronic information, and the method is applied to the relay network, and includes: receiving a transaction request sent by a client through each relay node, sending a pre-execution request to a cross-link gateway corresponding to each application blockchain through a main node, receiving a simulation execution result sent by the cross-link gateway corresponding to each application blockchain through the main node, broadcasting each simulation execution result to each relay node, checking each simulation execution result according to a relay intelligent contract corresponding to a relay network through each relay node, and sending an execution request to the cross-link gateway corresponding to each application blockchain through the main node under the condition that each simulation execution result passes the check of each relay node and each simulation execution result is successful, so that the cross-link gateway corresponding to the application blockchain executes the transaction request on the application blockchain.

Description

Transaction processing method, relay network, cross-link gateway, system, medium and equipment

Technical Field

The present disclosure relates to the field of electronic information technology, and in particular, to a transaction processing method, a relay network, a cross-link gateway, a system, a medium, and a device.

Background

With the continuous development of electronic information technology and network communication, transmission of service data by means of network communication has become a main technical means in each service field, so how to ensure that service data can be safely and reliably transmitted by means of network communication has become a key point of research of electronic information technology. The blockchain technology is a distributed, decentralised and distrusted network data consensus storage technology, and realizes synchronous and reliable distributed computation based on a blockwork (Block) generation mechanism and a Peer-to-Peer network (P2P network) communication mechanism.

Because blockchains are relatively independent, when transactions across blockchains are processed (a transaction may be understood to involve multiple blockchains), two-phase commit or hash-time locking is often required to ensure consistency of the transaction. However, both two-phase commit and hash time locking can degrade the processing performance of the transaction, resulting in problems of slow response times.

Disclosure of Invention

The purpose of the present disclosure is to provide a transaction processing method, a relay network, a cross-chain gateway, a system, a medium and a device, which are used for solving the problems of low processing performance and slow response time when a transaction of a cross-block chain is processed.

To achieve the above object, according to a first aspect of embodiments of the present disclosure, there is provided a transaction processing method applied to a relay network, the relay network being a peer-to-peer network, including a first number of relay nodes, the method including:

receiving a transaction request sent by a client through each relay node, wherein the transaction request corresponds to a second number of application blockchains;

sending a pre-execution request to a cross-link gateway corresponding to each application block chain through a master node, so that the cross-link gateway corresponding to the application block chain can simulate and execute the transaction request on the application block chain, wherein the master node is any relay node;

receiving a simulation execution result sent by the cross-chain gateway corresponding to each application blockchain through the master node, and broadcasting each simulation execution result to each relay node;

checking each simulation execution result according to a relay intelligent contract corresponding to the relay network through each relay node;

And under the condition that each simulation execution result passes the verification of each relay node and each simulation execution result is successful, sending an execution request to the cross-chain gateway corresponding to each application blockchain through the master node so as to enable the cross-chain gateway corresponding to the application blockchain to execute the transaction request on the application blockchain.

Optionally, after the sending, by the master node, an execution request to the cross-chain gateway corresponding to each of the application blockchains, the method further includes:

receiving, by the master node, an execution result sent by the cross-link gateway corresponding to each application blockchain, and broadcasting each execution result to each relay node;

and checking each execution result by each relay node according to the relay intelligent contract, and sending each execution result to the client side under the condition that each execution result passes the check.

Optionally, before the pre-execution request is sent to the cross-chain gateway corresponding to each application blockchain by the master node, the method further includes:

verifying the transaction request according to the relay intelligent contract through each relay node;

The sending, by the master node, a pre-execution request to a cross-link gateway corresponding to each application blockchain includes:

and under the condition that the transaction request passes the verification of each relay node, sending the pre-execution request to the cross-chain gateway corresponding to each application blockchain through the master node.

Optionally, the pre-executing request is configured to enable the cross-chain gateway corresponding to each application blockchain to simulate and execute the transaction request on the application blockchain, and set target ledger data in the application blockchain to be in an occupied state, where the target ledger data is ledger data used when the transaction request is simulated and executed;

the execution request is used for enabling the cross-chain gateway corresponding to each application blockchain to execute the transaction request on the target ledger data in the application blockchain, and setting the target ledger data in the application blockchain to be in an idle state.

Optionally, the method further comprises:

and under the condition that each simulation execution result passes the verification of each relay node and at least one simulation execution result is failure, sending a rollback request to the cross-chain gateway corresponding to each application blockchain through the master node so that the cross-chain gateway corresponding to the application blockchain sets the target account data in the application blockchain to be in an idle state.

Optionally, the method further comprises:

if the master node does not receive the simulation execution result sent by the cross-chain gateway corresponding to each application blockchain within a preset duration, sending a rollback request to the cross-chain gateway corresponding to each application blockchain through the master node, so that the cross-chain gateway corresponding to the application blockchain sets the target ledger data in the application blockchain to be in an idle state.

Optionally, the method further comprises:

and under the condition that each simulation execution result passes the verification of each relay node and at least one simulation execution result is failure, the pre-execution request is sent to the cross-chain gateway corresponding to each application blockchain through the master node again.

Optionally, each of the relay nodes has a relay blockchain stored thereon, and the method further includes:

receiving, by the master node, registration information sent by the cross-link gateway corresponding to each application blockchain, and broadcasting the registration information to each relay node, where the registration information includes a first transaction tag of the application blockchain;

checking the registration information through each relay node according to the relay intelligent contract, and storing the registration information into the relay blockchain under the condition that the registration information passes the check of each relay node;

Before the pre-execution request is sent to the cross-chain gateway corresponding to each application blockchain by the master node, the method further comprises:

and determining, by the master node, a second number of the application blockchains of the first transaction tag matching the second transaction tag according to the second transaction tag included in the transaction request.

Optionally, the method further comprises:

storing, by each of the relay nodes, the transaction request, and/or the pre-execution request, in the relay blockchain;

and under the condition that each simulation execution result passes the verification of each relay node, storing each simulation execution result into the relay blockchain through each relay node.

According to a second aspect of embodiments of the present disclosure, a transaction processing method is provided, applied to a cross-chain gateway, where the cross-chain gateway corresponds to an application blockchain; the method comprises the following steps:

receiving a pre-execution request sent by a master node in a relay network, wherein the relay network is a peer-to-peer network and comprises a plurality of relay nodes, the master node is any one of the relay nodes, and the pre-execution request is sent by the master node after each relay node receives a transaction request sent by a client;

Simulating execution of the transaction request on the application blockchain, and sending a simulation execution result to the master node;

and receiving an execution request sent by the master node, and executing the transaction request on the application blockchain.

Optionally, the simulating the executing the transaction request on the application blockchain includes:

simulating and executing the transaction request on the application blockchain, and setting target account book data in the application blockchain to be in an occupied state, wherein the target account book data is account book data used when simulating and executing the transaction request;

the executing the transaction request on the application blockchain includes:

executing the transaction request on the application blockchain and setting the target ledger data to an idle state.

Optionally, the method further comprises:

and receiving a rollback request sent by the master node, and setting the target account data to an idle state.

According to a third aspect of embodiments of the present disclosure, there is provided a relay network, the relay network being a peer-to-peer network, comprising a first number of relay nodes;

each relay node is configured to receive a transaction request sent by a client, where the transaction request corresponds to a second number of application blockchains;

The master node is used for sending a pre-execution request to the cross-chain gateway corresponding to each application block chain so that the cross-chain gateway corresponding to the application block chain can simulate and execute the transaction request on the application block chain, and the master node is any relay node;

the master node is further configured to receive a simulation execution result sent by the cross-link gateway corresponding to each application blockchain, and broadcast each simulation execution result to each relay node;

each relay node is further configured to verify each simulation execution result according to a relay intelligent contract corresponding to the relay network;

and under the condition that each simulation execution result passes the verification of each relay node and each simulation execution result is successful, the master node is further configured to send an execution request to the cross-chain gateway corresponding to each application blockchain, so that the cross-chain gateway corresponding to the application blockchain executes the transaction request on the application blockchain.

Optionally, the master node is further configured to receive an execution result sent by the cross-link gateway corresponding to each application blockchain after sending an execution request to the cross-link gateway corresponding to each application blockchain, and broadcast each execution result to each relay node;

And each relay node is further configured to verify each execution result according to the relay intelligent contract, and send each execution result to the client if each execution result passes the verification.

Optionally, each relay node is further configured to verify, before the master node sends a pre-execution request to a cross-link gateway corresponding to each application blockchain, the transaction request according to the relay intelligent contract;

and the master node is used for sending the pre-execution request to the cross-chain gateway corresponding to each application blockchain under the condition that the transaction request passes the verification of each relay node.

Optionally, the master node is further configured to send a rollback request to the cross-link gateway corresponding to each application blockchain when each simulation execution result passes the verification of each relay node and at least one simulation execution result is failure, so that the cross-link gateway corresponding to the application blockchain sets the target ledger data in the application blockchain to an idle state.

Optionally, the master node is further configured to send a rollback request to the cross-link gateway corresponding to each application blockchain if the master node does not receive the simulation execution result sent by the cross-link gateway corresponding to each application blockchain within a preset duration, so that the cross-link gateway corresponding to the application blockchain sets the target ledger data in the application blockchain to an idle state.

Optionally, the master node is further configured to send the pre-execution request to a cross-link gateway corresponding to each application blockchain again when each simulation execution result passes the verification of each relay node and at least one simulation execution result is failure.

Optionally, each of the relay nodes has a relay blockchain stored thereon;

the master node is further configured to receive registration information sent by the cross-link gateway corresponding to each application blockchain, and broadcast the registration information to each relay node, where the registration information includes a first transaction tag of the application blockchain;

each relay node is further configured to verify the registration information according to the relay intelligent contract, and store the registration information into the relay blockchain if the registration information passes the verification of each relay node;

the master node is further configured to determine, according to a second transaction tag included in the transaction request, a second number of application blockchains that are matched with the first transaction tag and the second transaction tag before sending a pre-execution request to a cross-chain gateway corresponding to each application blockchain.

Optionally, each of the relay nodes is further configured to store the transaction request and/or the pre-execution request in the relay blockchain, and store each of the simulation execution results in the relay blockchain if each of the simulation execution results passes the verification of each of the relay nodes.

According to a fourth aspect of embodiments of the present disclosure, there is provided a cross-chain gateway comprising:

the receiving module is used for receiving a pre-execution request sent by a main node in a relay network, wherein the relay network is a peer-to-peer network and comprises a plurality of relay nodes, the main node is any relay node, and the pre-execution request is sent by the main node after each relay node receives a transaction request sent by a client;

the simulation execution module is used for simulating the transaction request on the application blockchain and sending a simulation execution result to the master node;

and the execution module is used for receiving the execution request sent by the master node and executing the transaction request on the application blockchain.

Optionally, the simulation execution module is configured to simulate and execute the transaction request on the application blockchain, and set target ledger data in the application blockchain to an occupied state, where the target ledger data is ledger data used when the transaction request is simulated and executed;

the execution module is configured to execute the transaction request on the application blockchain and set the target ledger data to an idle state.

Optionally, the cross-chain gateway further comprises:

and the rollback module is used for receiving the rollback request sent by the master node and setting the target account book data into an idle state.

According to a fifth aspect of embodiments of the present disclosure, there is provided a transaction processing system, the system comprising: the system comprises a relay network, a plurality of application blockchains and a cross-chain gateway corresponding to each application blockchain;

the relay network is configured to perform the transaction processing method according to the first aspect of the embodiments of the present disclosure;

each of the cross-chain gateways is configured to perform the transaction method of the second aspect of the embodiments of the present disclosure.

According to a sixth aspect of the disclosed embodiments, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the steps of the method of the first aspect of the disclosed embodiments.

According to a seventh aspect of embodiments of the present disclosure, there is provided an electronic device, comprising:

a memory having a computer program stored thereon;

a processor for executing the computer program in the memory to implement the steps of the method of the first aspect of the embodiments of the present disclosure.

According to an eighth aspect of the disclosed embodiments, there is provided a computer readable storage medium having stored thereon a computer program which when executed by a processor implements the steps of the method of the second aspect of the disclosed embodiments.

According to a ninth aspect of embodiments of the present disclosure, there is provided an electronic device, including:

a memory having a computer program stored thereon;

a processor for executing the computer program in the memory to implement the steps of the method of the second aspect of the embodiments of the present disclosure.

According to the transaction processing method, firstly, the first number of relay nodes receive transaction requests corresponding to the second number of application blockchains sent by the client, then the master node sends pre-execution requests to the cross-link gateway corresponding to each application blockchain, the cross-link gateway simulates the execution of the transaction requests on the corresponding application blockchains, and the simulation execution results are sent to the master node. And broadcasting the received simulation execution result to each relay node by the main node, checking the simulation execution result by the relay node according to the relay intelligent contract, and finally, under the condition that each simulation execution result passes the check of each relay node and each simulation execution result is successful, sending an execution request to each cross-link gateway by the main node, and executing a transaction request on the corresponding application block chain by the cross-link gateway. According to the method and the device, the peer relay nodes in the relay network coordinate among the plurality of application blockchains, so that distributed, decentralised and distrusted relay is realized, meanwhile, the execution of the transaction request on the application blockchain is realized through the cross-chain gateway corresponding to each application blockchain, and under the premise of ensuring the transaction consistency, the cross-chain transaction can be rapidly processed, the processing performance is improved, and the response time is shortened.

Additional features and advantages of the present disclosure will be set forth in the detailed description which follows.

Drawings

The accompanying drawings are included to provide a further understanding of the disclosure, and are incorporated in and constitute a part of this specification, illustrate the disclosure and together with the description serve to explain, but do not limit the disclosure. In the drawings:

FIG. 1 is a schematic diagram of a transaction processing system, shown in accordance with an exemplary embodiment;

FIG. 2 is a flow chart illustrating a transaction method according to an exemplary embodiment;

FIG. 3 is a flow chart illustrating another transaction method according to an exemplary embodiment;

FIG. 4 is a flow chart illustrating another transaction method according to an exemplary embodiment;

FIG. 5 is a flow chart illustrating another transaction method according to an exemplary embodiment;

FIG. 6 is a flowchart illustrating another transaction method according to an example embodiment;

FIG. 7 is a flowchart illustrating another transaction method according to an exemplary embodiment;

FIG. 8 is a flowchart illustrating another transaction method according to an exemplary embodiment;

FIG. 9 is a flowchart illustrating another transaction method according to an exemplary embodiment;

FIG. 10 is a flowchart illustrating a transaction method according to an exemplary embodiment;

FIG. 11 is a flowchart illustrating another transaction method according to an exemplary embodiment;

fig. 12 is a schematic diagram of a relay network according to an example embodiment;

FIG. 13 is a block diagram of a cross-chain gateway, shown in accordance with an exemplary embodiment;

FIG. 14 is a block diagram of another cross-chain gateway shown in accordance with an exemplary embodiment;

fig. 15 is a block diagram of an electronic device, according to an example embodiment.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

Before describing the transaction processing method, the relay network, the cross-chain gateway, the system, the medium and the device provided by the present disclosure, an application scenario related to various embodiments in the present disclosure is first described, where the application scenario may be a scenario of processing a transaction of a cross-blockchain, and may be a transaction processing system, as shown in fig. 1, where the transaction processing system includes the relay network, a second number of application blockchains, and a cross-chain gateway corresponding to each application blockchain (in fig. 1, the second number is denoted by 2 as an example).

The relay network is a peer-to-peer network, and includes a plurality of nodes, each node is in a peer-to-peer position, and the plurality of nodes can be divided into two main classes, one is a first number of relay nodes (which can be understood as endorsement nodes in the relay network) storing relay intelligent contracts corresponding to the relay network, and the other class is a third number of other nodes (which are exemplified by the first number of 5 in fig. 1) storing relay intelligent contracts. Further, a relay blockchain may be stored in the relay network, so as to record data in the relay network, that is, the relay blockchain is stored in each node in the relay network. Specifically, the relay intelligent contract corresponding to the relay network may be understood as a code stored in each node for implementing access and control of data in the relay network. Each relay node can verify the information received by the relay network according to the relay intelligent contract, if the information passes the verification of each relay node, the relay node can make a consensus on the information, and the relay network can perform corresponding processing (namely, execute the transaction) on the information. That is, the relay intelligent contract enables each relay node in the relay network to execute the transaction after reaching consensus, so that the consistency of the transaction in the relay network can be ensured.

The second number of application blockchains may be understood as blockchains to which transactions across blockchains are to be directed. Transactions across blockchains may include asset transactions, asset transfers, and the like. For example, for a transaction across blockchains, to add a record of "X1" to the a-application blockchain and a record of "Y1" to the b-application blockchain, the application blockchains corresponding to the a transaction are the a-application blockchain and the b-application blockchain. Each application blockchain is stored on each application node in the corresponding application blockchain network, and each application node in each application blockchain network is in a peer-to-peer position.

For each application blockchain, a corresponding cross-chain gateway is provided, and the cross-chain gateway can be understood as a proxy of the application blockchain, can access and operate the application blockchain, and can perform data communication with a relay network. It should be noted that, the first number and the second number mentioned above are positive integers greater than 1, and the third number may be a natural number. The following describes a specific implementation of the transaction method.

Fig. 2 is a flowchart illustrating a transaction method according to an exemplary embodiment, and as shown in fig. 2, the method is applied to a relay network, which is a peer-to-peer network, including a first number of relay nodes, and includes the following steps:

Step 101, receiving, by each relay node, a transaction request sent by a client, where the transaction request corresponds to a second number of application blockchains.

For example, when a user needs to perform a transaction that spans a blockchain, a transaction request may be sent by a client to each relay node in the relay network to instruct the execution of the transaction. The transaction request may include the identification of the corresponding second number of application blockchains, and may further include a transaction tag (i.e., a second transaction tag mentioned later) of the transaction to be executed, a client identification, a client identity credential, and the like. After each relay node receives the transaction request, the transaction request can be checked according to the relay intelligent contract, and if the transaction request passes the check of each relay node, the fact that each relay node agrees with the transaction request is indicated. After each relay node has agreed upon the transaction request, each relay node may record the transaction request, for example, in a relay blockchain. The client may be a mobile terminal with a display interface, such as a smart phone, a tablet computer, a smart television, a smart watch, a PDA (english: personal Digital Assistant, chinese: personal digital assistant), a portable computer, or a fixed terminal, such as a desktop computer.

Step 102, a pre-execution request is sent to the cross-link gateway corresponding to each application blockchain through the master node, so that the cross-link gateway corresponding to the application blockchain simulates and executes a transaction request on the application blockchain, and the master node is any relay node.

For example, after each relay node has agreed upon a transaction request, a pre-execution request may be sent by the master node to the cross-chain gateway corresponding to each application blockchain. The master node may be any relay node, for example, may be a relay node that is promoted from the first number of relay nodes and has more resources (such as power, normal running time, maintenance, storage space, memory, etc.). In the process of implementing the transaction processing method, the master node can be specified or updated in real time. Under the condition that the master node is appointed, a long link can be established between the master node and the cross-link gateway corresponding to each application block chain, so that the efficiency of data transmission between the master node and the cross-link gateway corresponding to each application block chain is improved.

After receiving the pre-execution request, the cross-chain gateway corresponding to each application blockchain can simulate and execute the transaction request on the application blockchain to obtain a result of the application blockchain for simulating and executing the transaction request, namely a simulation execution result, wherein the simulation execution result can be success or failure. The transaction request is simulated to be executed, which is understood to be that transaction endorsement is carried out on the application blockchain, and only whether the transaction request can be executed on the application blockchain is determined, so that account book data on the application blockchain is not affected. After obtaining the simulation execution result of the application blockchain, the cross-chain gateway corresponding to the application blockchain sends the simulation execution result to the master node.

And step 103, receiving the simulation execution results sent by the cross-link gateway corresponding to each application blockchain through the master node, and broadcasting each simulation execution result to each relay node.

And 104, checking each simulation execution result through each relay node according to the relay intelligent contract corresponding to the relay network.

For example, after receiving the simulation execution result sent by the cross-chain gateway corresponding to each application blockchain, the master node may broadcast each simulation execution result to each relay node. After receiving the second number of simulation execution results, each relay node firstly checks each simulation execution result according to the relay intelligent contract. If the second number of simulation execution results pass the verification of each relay node, the second number of simulation execution results are indicated to reach consensus for each relay node.

Step 105, when each simulation execution result passes the verification of each relay node and each simulation execution result is successful, sending, by the master node, an execution request to the cross-chain gateway corresponding to each application blockchain, so that the cross-chain gateway corresponding to the application blockchain executes the transaction request on the application blockchain.

For example, after each relay node agrees with the second number of simulation execution results, each simulation execution result may be determined, if each simulation execution result is successful, it indicates that the second number of application blockchains may execute the transaction request, and at this time, the execution request may be sent to the cross-chain gateway corresponding to each application blockchain through the master node. The cross-chain gateway corresponding to the application blockchain may execute the transaction request on the application blockchain after receiving the execution request, thereby enabling execution of the transaction request on a second number of application blockchains. In this way, because the relay nodes in the relay network are peer-to-peer, the relay network coordinates among the second number of application blockchains through the distributed, decentralised, distrusted framework, such that each application blockchain can maintain the distributed, decentralised, distrusted framework. Meanwhile, corresponding cross-chain gateways are arranged for each application block chain, and the cross-chain gateways are used as agents of the application block chains to execute transaction requests on the application block chains, so that two-stage submission or hash time locking is not needed, the cross-chain transactions can be rapidly processed on the premise of ensuring the consistency of the transactions, the processing performance is improved, and the response time is shortened.

In summary, in the transaction processing method provided by the present disclosure, first, a first number of relay nodes receive transaction requests corresponding to a second number of application blockchains sent by a client, then a master node sends a pre-execution request to a cross-link gateway corresponding to each application blockchain, and the cross-link gateway simulates and executes the transaction requests on the corresponding application blockchains and sends a simulation execution result to the master node. And broadcasting the received simulation execution result to each relay node by the main node, checking the simulation execution result by the relay node according to the relay intelligent contract, and finally, under the condition that each simulation execution result passes the check of each relay node and each simulation execution result is successful, sending an execution request to each cross-link gateway by the main node, and executing a transaction request on the corresponding application block chain by the cross-link gateway. According to the method and the device, the peer relay nodes in the relay network coordinate among the plurality of application blockchains, so that distributed, decentralised and distrusted relay is realized, meanwhile, the execution of the transaction request on the application blockchain is realized through the cross-chain gateway corresponding to each application blockchain, and under the premise of ensuring the transaction consistency, the cross-chain transaction can be rapidly processed, the processing performance is improved, and the response time is shortened.

FIG. 3 is a flow chart illustrating another transaction method according to an exemplary embodiment, as shown in FIG. 3, after step 105, the method may further include:

and step 106, receiving an execution result sent by the cross-link gateway corresponding to each application blockchain through the master node, and broadcasting each execution result to each relay node.

And step 107, checking each execution result according to the relay intelligent contract through each relay node, and sending each execution result to the client side under the condition that each execution result passes the check.

For example, after the cross-chain gateway corresponding to each application blockchain executes the transaction request on the application blockchain, the result of executing the transaction request by the application blockchain may be obtained, that is, the execution result may be success or failure. Executing a transaction request may be understood as transacting the transaction request on the application blockchain, i.e., operating on ledger data on the application blockchain, such as adding a record. After the execution result of the application blockchain is obtained, the cross-chain gateway corresponding to the application blockchain sends the execution result to the master node.

After receiving the execution result sent by the cross-link gateway corresponding to each application blockchain, the master node may broadcast each execution result to each relay node. After receiving the second number of execution results, each relay node firstly checks each execution result according to the relay intelligent contract. And if the second number of execution results pass the verification of each relay node, the second number of execution results are indicated to reach consensus by each relay node. In one implementation, after each relay node agrees with the second number of analog execution results, each relay node may send the second number of execution results to the client, and if the second number of execution results sent by each relay node and received by the client are the same, the second number of execution results may be confirmed. In another implementation, the master node may send the second number of execution results to the client, where the client directly confirms the second number of execution results.

FIG. 4 is a flowchart illustrating another transaction method according to an exemplary embodiment, as shown in FIG. 4, prior to step 102, the method further comprising:

and step 108, checking the transaction request according to the relay intelligent contract through each relay node.

Accordingly, the implementation manner of step 102 may be:

and under the condition that the transaction request passes the verification of each relay node, sending a pre-execution request to a cross-chain gateway corresponding to each application blockchain through the master node.

For example, before the master node sends the pre-execution request to the cross-link gateway corresponding to each application blockchain, the relay network may further check the transaction request according to the relay intelligent contract through each relay node, and if the transaction request passes the check of each relay node, it indicates that each relay node agrees with the transaction request. After each relay node agrees with the transaction request, each relay node may record the transaction request, and at the same time, the master node may send a pre-execution request to the cross-chain gateway corresponding to each application blockchain.

In an application scenario, a pre-execution request is used for enabling a cross-chain gateway corresponding to each application blockchain to simulate and execute a transaction request on the application blockchain, and setting target account book data in the application blockchain to be in an occupied state, wherein the target account book data is account book data used when the transaction request is simulated and executed.

And executing the request, namely enabling the cross-chain gateway corresponding to each application block chain to execute the transaction request on the target account book data in the application block chain, and setting the target account book data in the application block chain to be in an idle state.

For example, in order to further ensure the consistency of the transaction, the pre-execution request instructs the cross-chain gateway corresponding to each application blockchain, instructs the cross-chain gateway corresponding to the application blockchain while simulating the execution of the transaction request on the application blockchain, and sets the target ledger data in the application blockchain to an occupied state, so that it can be ensured that the target ledger data cannot be modified by other transactions before executing the transaction request on the target ledger data. The target ledger data is ledger data used when the transaction request is simulated to be executed, and can be understood as ledger data related to the transaction request.

Correspondingly, the execution request instructs the cross-link gateway corresponding to each application blockchain to execute the transaction request on the target ledger data in the application blockchain, and instructs the cross-link gateway corresponding to the application blockchain to set the target ledger data in the application blockchain to be in an idle state, so that after the transaction request is executed on the target ledger data, the target ledger data is restored to be in the idle state and can be modified by other transactions. For example, if the target ledger data corresponding to the transaction request is "XX", then when the transaction request is executed using "XX" simulation, the storage state of "XX" may be set to "1" to indicate that "XX" is in the occupied state. After executing the transaction request on "XX", the storage state of "XX" may be set to "0" to indicate that "XX" is in the idle state.

FIG. 5 is a flowchart illustrating another transaction method according to an exemplary embodiment, as shown in FIG. 5, which may further include:

step 109, when each simulation execution result passes the verification of each relay node and at least one simulation execution result is failure, a rollback request is sent to the cross-link gateway corresponding to each application blockchain through the master node, so that the cross-link gateway corresponding to the application blockchain sets the target account data in the application blockchain to an idle state.

In another application scenario, after each relay node agrees with the second number of simulation execution results, each simulation execution result is judged, if at least one simulation execution result is failure, it means that there may be at least one application blockchain incapable of executing a transaction request in the second number of application blockchains, and a rollback request may be sent to a cross-chain gateway corresponding to each application blockchain by the master node, so as to set target account book data in the application blockchain to an idle state. If there is at least one application blockchain that cannot execute the transaction request, then it is indicated that the transaction request cannot be executed on the second number of application blockchains, and therefore the relay network will no longer send execution requests to the cross-chain gateway. Because the cross-chain gateway sets the target ledger data in the application blockchain to an occupied state when simulating execution of a transaction request on the corresponding application blockchain, and then does not execute the transaction request any more, the target ledger data in the application blockchain can be set to an idle state. Further, if at least one simulation execution result is failure, a prompt message may be sent to the client through the master node or each relay node to inform the client that the transaction request is not executed.

FIG. 6 is a flowchart illustrating another transaction method according to an exemplary embodiment, as shown in FIG. 6, which may further include:

step 110, if the master node does not receive the simulation execution result sent by the cross-link gateway corresponding to each application blockchain within the preset duration, sending a rollback request to the cross-link gateway corresponding to each application blockchain through the master node, so that the cross-link gateway corresponding to the application blockchain sets the target account data in the application blockchain to be in an idle state.

For example, since the master node needs to receive the simulation execution result sent by the cross-chain gateway corresponding to each application blockchain, the problem of access timeout is easily caused when the second number is larger because the second number is related to the second number of application blockchains. If the master node cannot receive the second number of simulation execution results, the master node is always in a waiting state, and the relay network is possibly in a blocking state, so that the performance of the relay network is seriously affected. Therefore, a preset duration (which may be understood as a timeout period, for example, may be 2 min) may be set, if the master node does not receive the simulation execution result sent by the cross-link gateway corresponding to each application blockchain within the preset duration, which indicates that the simulation execution result returns to timeout, and the transaction request cannot be executed on the second number of application blockchains, then the master node sends a rollback request to the cross-link gateway corresponding to each application blockchain, so as to set the target ledger data in the application blockchain to an idle state. Accordingly, the relay network will not send execution requests to the cross-link gateway. Because the cross-chain gateway sets the target ledger data in the application blockchain to an occupied state when simulating execution of a transaction request on the corresponding application blockchain, and then does not execute the transaction request any more, the target ledger data in the application blockchain can be set to an idle state. Thus, the relay network can be prevented from being blocked all the time, and the processing performance of the transaction is ensured.

Further, if the master node does not receive the execution result sent by the cross-link gateway corresponding to a certain application blockchain within a specified duration (for example, may be 5 min), then whether the execution result exists or not may be queried again from the cross-link gateway corresponding to the application blockchain at intervals (for example, 10 min).

FIG. 7 is a flowchart illustrating another transaction method according to an exemplary embodiment, as shown in FIG. 7, which may further include:

step 111, when each simulation execution result passes the verification of each relay node and at least one simulation execution result is failure, the pre-execution request is sent again to the cross-chain gateway corresponding to each application blockchain through the master node.

For example, after each relay node agrees with the second number of simulation execution results, each simulation execution result may be determined, and if at least one simulation execution result is failure, it indicates that at least one application blockchain may not be able to execute the transaction request in the second number of application blockchains. If the master node directly sends a rollback request to the cross-link gateway corresponding to each application blockchain at this time, the performance of the relay network may be affected, and the reason that the simulation execution result is failure may be due to network jitter, system blocking, and the like. Thus, the pre-execution request may be re-sent by the master node to the cross-chain gateway corresponding to each application blockchain, and then steps 103 to 105 are re-executed. Furthermore, the number of retries (for example, 3 times) that the master node sends the pre-execution request to the cross-link gateway corresponding to each application blockchain can be limited, and the number of retries can be set according to the state of the relay network or according to specific requirements.

Fig. 8 is a flowchart illustrating another transaction method according to an exemplary embodiment, as shown in fig. 8, in which each relay node has a relay blockchain stored thereon, the method may further include:

step 112, receiving, by the master node, registration information sent by the cross-link gateway corresponding to each application blockchain, and broadcasting the registration information to each relay node, where the registration information includes a first transaction tag of the application blockchain.

And 113, checking the registration information through each relay node according to the relay intelligent contract, and storing the registration information into the relay blockchain under the condition that the registration information passes the check of each relay node.

For example, a relay blockchain may be included in the relay network for recording data in the relay network, the relay blockchain being stored in each node (including relay nodes and other nodes) in the relay network. After the relay network is established, each application blockchain may be registered in the relay network through a corresponding cross-chain gateway. For example, the cross-chain gateway corresponding to each application blockchain may send registration information of the application blockchain to the master node, where the registration information includes a first transaction tag of the application blockchain, and may also include information such as identity credentials, network addresses, server interfaces of the application blockchain, identities in the relay network, and so on. Wherein the first transaction tag, which may be understood as identifying the type of transaction that the application blockchain is capable of handling. And broadcasting the registration information of the application block chain to each relay node by the master node, checking the registration information by each relay node according to the relay intelligent contract, and if the registration information passes the check of each relay node, indicating that each relay node agrees with the registration information. After each relay node has agreed upon the registration information, each relay node may record the registration information, e.g., may record the registration information in a relay blockchain. It is understood that the relay blockchain has stored therein registration information for each of the second number of application blockchains.

Accordingly, prior to step 102, the method further comprises:

step 114, by the master node, determining a second number of application blockchains for matching the first transaction tag with the second transaction tag based on the second transaction tag included in the transaction request.

For example, before sending the pre-execution request to the cross-chain gateway corresponding to each application blockchain, the master node may determine, according to a second transaction tag included in the transaction request, a second number of application blockchains that match the second transaction tag, thereby determining the cross-chain gateway corresponding to each application blockchain. Wherein a second transaction tag, which may be understood as identifying the type of transaction that the transaction request is to process. When a first transaction tag matches a second transaction tag (which may be understood to be the same as the first transaction tag), a number of application blockchains involved in the transaction request may be determined.

FIG. 9 is a flowchart illustrating another transaction method according to an exemplary embodiment, as shown in FIG. 9, which may further include:

in step 115, transaction requests, and/or pre-execution requests, are stored in the relay blockchain by each relay node.

In step 116, in the case that each simulation execution result passes the verification of each relay node, each simulation execution result is stored into the relay blockchain through each relay node.

For example, to ensure the security and reliability of the relay network, and traceability, the transaction request, the pre-execution request and the execution request received by the relay network may be stored in the relay blockchain through each relay node, and the client may query all operations in the relay network by accessing the relay blockchain. Meanwhile, under the condition that each simulation execution result passes the verification of each relay node, each simulation execution result can be stored into the relay block chain through each relay node, so that the consistency of data can be ensured when the relay node is prevented from exiting abnormally. Further, in the case that each execution result passes the verification of each relay node, each execution result may also be stored into the relay blockchain through each relay node.

FIG. 10 is a flowchart illustrating a transaction method, as shown in FIG. 10, applied to a cross-chain gateway corresponding to an application blockchain, where the application blockchain may be any application blockchain in a transaction system, and the cross-chain gateway may be a cross-chain gateway corresponding to the application blockchain, as described above. That is, it is a cross-chain gateway corresponding to each application blockchain in a transaction system that is configured to perform the transaction method, the method comprising the steps of:

step 201, receiving a pre-execution request sent by a master node in a relay network, where the relay network is a peer-to-peer network and includes a plurality of relay nodes, the master node is any relay node, and the pre-execution request is sent by the master node after each relay node receives a transaction request sent by a client.

Step 202, simulating an execution transaction request on an application blockchain, and sending a simulation execution result to a master node.

For example, when a user needs to perform a transaction across blockchains, a transaction request for indicating to perform the transaction may be sent by the client to each relay node in the relay network, the transaction request corresponding to a second number of application blockchains. After each relay node receives the transaction request, the transaction request can be checked according to the relay intelligent contract, and if the transaction request passes the check of each relay node, the fact that each relay node agrees with the transaction request is indicated. After each relay node has consensus on the transaction request, a pre-execution request can be sent to a cross-chain gateway corresponding to each application blockchain through the master node.

Step 203, receiving an execution request sent by the master node, and executing a transaction request on the application blockchain.

For example, after receiving the simulation execution result sent by the cross-chain gateway corresponding to each application blockchain, the master node may broadcast each simulation execution result to each relay node. After receiving the second number of simulation execution results, each relay node firstly checks each simulation execution result according to the relay intelligent contract. If the second number of simulation execution results pass the verification of each relay node, the second number of simulation execution results are indicated to reach consensus for each relay node. After each relay node agrees with the second number of simulation execution results, each simulation execution result can be judged, if each simulation execution result is successful, the second number of application blockchains can execute the transaction request, and the execution request can be sent to the cross-chain gateway corresponding to each application blockchain through the master node.

The cross-chain gateway corresponding to the application blockchain may execute the transaction request on the application blockchain after receiving the execution request, thereby enabling execution of the transaction request on a second number of application blockchains. After obtaining the execution result of the application blockchain (i.e. the result of the application blockchain executing the transaction request), the cross-chain gateway corresponding to the application blockchain sends the execution result to the master node. So that the master node verifies and/or stores each execution result. In this way, because the relay nodes in the relay network are peer-to-peer, the relay network coordinates among the second number of application blockchains through the distributed, decentralised, distrusted framework, such that each application blockchain can maintain the distributed, decentralised, distrusted framework. Meanwhile, corresponding cross-chain gateways are arranged for each application block chain, and the cross-chain gateways are used as agents of the application block chains to execute transaction requests on the application block chains, so that two-stage submission or hash time locking is not needed, the cross-chain transactions can be rapidly processed on the premise of ensuring the consistency of the transactions, the processing performance is improved, and the response time is shortened.

In an application scenario, the implementation of step 202 may be:

and simulating and executing the transaction request on the application block chain, and setting target account book data in the application block chain to be in an occupied state, wherein the target account book data is account book data used when simulating and executing the transaction request.

The implementation manner of step 203 may be:

a transaction request is executed on the application blockchain and the target ledger data is set to an idle state.

For example, in order to further ensure the consistency of the transaction, after receiving the pre-execution request, the cross-chain gateway may set the target ledger data in the corresponding application blockchain to an occupied state while simulating the execution of the transaction request on the corresponding application blockchain, so that it can be ensured that the target ledger data cannot be modified by other transactions before executing the transaction request on the target ledger data. The target ledger data is ledger data used when the transaction request is simulated to be executed, and can be understood as ledger data related to the transaction request.

Accordingly, after receiving the execution request, the cross-chain gateway can set the target ledger data in the application blockchain to be in an idle state while executing the transaction request on the target ledger data in the corresponding application blockchain, so that after executing the transaction request on the target ledger data, the target ledger data is restored to be in the idle state and can be modified by other transactions.

In another implementation, the method may further include:

and transmitting the registration information of the corresponding application blockchain to the master node so as to register the application blockchain in the relay network. The registration information may include a first transaction tag of the application blockchain, and may further include information such as an identity credential of the application blockchain, a network address, a server interface, an identity in a relay network, and the like. Wherein the first transaction tag, which may be understood as identifying the type of transaction that the application blockchain is capable of handling.

And broadcasting the registration information of the application block chain to each relay node by the master node, checking the registration information by each relay node according to the relay intelligent contract, and if the registration information passes the check of each relay node, indicating that each relay node agrees with the registration information. After each relay node has agreed upon the registration information, each relay node may record the registration information, e.g., may record the registration information in a relay blockchain. In this way, the master node may determine, based on the second transaction tag included in the transaction request, a second number of application blockchains that match each application blockchain before sending the pre-execution request to the cross-chain gateway corresponding to each application blockchain, thereby determining the cross-chain gateway corresponding to each application blockchain. Wherein a second transaction tag, which may be understood as identifying the type of transaction that the transaction request is to process. When a first transaction tag matches a second transaction tag (which may be understood to be the same as the first transaction tag), a number of application blockchains involved in the transaction request may be determined.

FIG. 11 is a flowchart illustrating another transaction method according to an exemplary embodiment, as shown in FIG. 11, which may further include:

step 204, receiving a rollback request sent by the master node, and setting the target ledger data to an idle state.

Further, after each relay node agrees with the second number of simulation execution results, if at least one simulation execution result is failure, it indicates that there may be at least one application blockchain in the second number of application blockchains that cannot execute the transaction request, and the rollback request may be sent to the cross-chain gateway corresponding to each application blockchain through the master node. After receiving the rollback request, the cross-chain gateway may set the target ledger data in the corresponding application blockchain to an idle state. If there is at least one application blockchain that cannot execute the transaction request, then it is indicated that the transaction request cannot be executed on the second number of application blockchains, and therefore the relay network will no longer send execution requests to the cross-chain gateway. Because the cross-chain gateway sets the target ledger data in the application blockchain to an occupied state when simulating execution of a transaction request on the corresponding application blockchain, and then does not execute the transaction request any more, the target ledger data in the application blockchain can be set to an idle state.

It should be noted that, a blockchain adapter may be disposed on the blockchain gateway, where the blockchain adapter may be understood as a communication driver that the blockchain gateway can access and operate a corresponding application blockchain, and the blockchain gateway can call a pre-execution interface, an execution interface, and a rollback interface that are reserved by the application blockchain through the blockchain adapter. Specifically, upon receiving a pre-execution request, the cross-chain gateway may invoke a pre-execution interface through the blockchain adapter to simulate executing the transaction request on the application blockchain. Upon receiving an execution request, the cross-chain gateway may invoke an execution interface through the blockchain adapter to execute the transaction request on the application blockchain. Likewise, upon receiving a rollback request, the cross-chain gateway may invoke a rollback interface through the blockchain adapter to set the target ledger data to an idle state.

Fig. 12 is a schematic diagram of a relay network, shown in fig. 12, which is a peer-to-peer network including a first number of relay nodes, according to an example embodiment.

Each relay node is configured to receive a transaction request sent by a client, where the transaction request corresponds to a second number of application blockchains.

And the master node is used for sending a pre-execution request to the cross-chain gateway corresponding to each application block chain so that the cross-chain gateway corresponding to the application block chain can simulate and execute the transaction request on the application block chain, and is any relay node.

The main node is further configured to receive a simulation execution result sent by the cross-link gateway corresponding to each application blockchain, and broadcast each simulation execution result to each relay node.

And each relay node is also used for checking each simulation execution result according to the relay intelligent contract corresponding to the relay network.

And under the condition that each simulation execution result passes the verification of each relay node and each simulation execution result is successful, the master node is further used for sending an execution request to the cross-chain gateway corresponding to each application blockchain so as to enable the cross-chain gateway corresponding to the application blockchain to execute the transaction request on the application blockchain.

In an application scenario, the master node is further configured to receive an execution result sent by a cross-link gateway corresponding to each application blockchain after sending an execution request to the cross-link gateway corresponding to each application blockchain, and broadcast each execution result to each relay node.

And each relay node is further used for checking each execution result according to the relay intelligent contract and sending each execution result to the client under the condition that each execution result passes the check.

In another application scenario, each relay node is further configured to check the transaction request according to the relay intelligent contract before the master node sends the pre-execution request to the cross-link gateway corresponding to each application blockchain.

And the master node is used for sending a pre-execution request to the cross-chain gateway corresponding to each application blockchain under the condition that the transaction request passes the verification of each relay node.

In another application scenario, the pre-execution request is used for enabling the cross-chain gateway corresponding to each application blockchain to simulate and execute the transaction request on the application blockchain, and setting target account book data in the application blockchain to be in an occupied state, wherein the target account book data is account book data used when the transaction request is simulated and executed.

In another application scenario, the master node is further configured to send a rollback request to a cross-link gateway corresponding to each application blockchain when each simulation execution result passes the verification of each relay node and at least one simulation execution result is failure, so that the cross-link gateway corresponding to the application blockchain sets the target account data in the application blockchain to an idle state.

In another application scenario, the master node is further configured to send a rollback request to the cross-link gateway corresponding to each application blockchain if the master node does not receive the simulation execution result sent by the cross-link gateway corresponding to each application blockchain within a preset duration, so that the cross-link gateway corresponding to the application blockchain sets the target account data in the application blockchain to be in an idle state.

In another application scenario, the master node is further configured to send, when each simulation execution result passes the verification of each relay node and at least one simulation execution result is failure, a pre-execution request to a cross-chain gateway corresponding to each application blockchain again.

In another application scenario, a relay blockchain is stored on each relay node.

The main node is further configured to receive registration information sent by a cross-link gateway corresponding to each application blockchain, and broadcast the registration information to each relay node, where the registration information includes a first transaction tag of the application blockchain.

Each relay node is further configured to verify the registration information according to the relay intelligent contract, and store the registration information into the relay blockchain when the registration information passes the verification of each relay node.

The master node is further configured to determine, according to a second transaction tag included in the transaction request, a second number of application blockchains that match the first transaction tag with the second transaction tag before sending the pre-execution request to the cross-chain gateway corresponding to each application blockchain.

In another application scenario, each relay node is further configured to store the transaction request and/or the pre-execution request in the relay blockchain, and store each simulation execution result in the relay blockchain if each simulation execution result passes the check of each relay node.

The specific manner in which the relay network performs the operations in relation to the system of the above embodiments has been described in detail in relation to the embodiments of the method, and will not be described in detail here.

Fig. 13 is a block diagram of a cross-chain gateway, as shown in fig. 13, according to an example embodiment, the cross-chain gateway 300 includes:

the receiving module 301 is configured to receive a pre-execution request sent by a master node in a relay network, where the relay network is a peer-to-peer network and includes a plurality of relay nodes, the master node is any relay node, and the pre-execution request is sent by the master node after each relay node receives a transaction request sent by a client.

The simulation execution module 302 is configured to simulate and execute a transaction request on the application blockchain, and send a simulation execution result to the master node.

And the execution module 303 is configured to receive an execution request sent by the master node, and execute a transaction request on the application blockchain.

In one application scenario, the simulation execution module 302 is configured to simulate and execute a transaction request on an application blockchain, and set target ledger data in the application blockchain to an occupied state, where the target ledger data is ledger data used when the transaction request is simulated and executed.

The execution module 303 is configured to execute the transaction request on the application blockchain and set the target ledger data to an idle state.

Fig. 14 is a block diagram of another cross-chain gateway, shown in fig. 14, according to an example embodiment, the cross-chain gateway 300 may further include:

The rollback module 304 is configured to receive a rollback request sent by the master node, and set the target ledger data to an idle state.

The specific manner in which the operations are performed by the cross-chain gateway in relation to the system of the above embodiments has been described in detail in relation to the embodiments of the method and will not be described in detail herein.

The present disclosure also provides a transaction processing system, a schematic diagram of which is shown in fig. 1, including: the system comprises a relay network, a plurality of application blockchains and a cross-chain gateway corresponding to each application blockchain.

The relay network is used for executing the transaction processing method applied to the relay network in the embodiment of the disclosure.

Each of the cross-chain gateways is configured to perform a transaction method for applying the cross-chain gateway according to the embodiments of the present disclosure.

The specific manner in which the relay network and the cross-chain gateway perform operations in relation to the system in the above embodiments has been described in detail in relation to the embodiments of the method, and will not be described in detail here.

Fig. 15 is a block diagram of an electronic device 400, according to an example embodiment. As shown in fig. 15, the electronic device 400 may include: a processor 401, a memory 402. The electronic device 400 may also include one or more of a multimedia component 403, an input/output (I/O) interface 404, and a communication component 405.

Wherein the processor 401 is configured to control the overall operation of the electronic device 400 to perform all or part of the steps of the transaction method described above. The memory 402 is used to store various types of data to support operation at the electronic device 400, which may include, for example, instructions for any application or method operating on the electronic device 400, as well as application-related data, such as contact data, transceived messages, pictures, audio, video, and the like. The Memory 402 may be implemented by any type or combination of volatile or non-volatile Memory devices, such as static random access Memory (Static Random Access Memory, SRAM for short), electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM for short), erasable programmable Read-Only Memory (Erasable Programmable Read-Only Memory, EPROM for short), programmable Read-Only Memory (Programmable Read-Only Memory, PROM for short), read-Only Memory (ROM for short), magnetic Memory, flash Memory, magnetic disk, or optical disk. The multimedia component 403 may include a screen and an audio component. Wherein the screen may be, for example, a touch screen, the audio component being for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may be further stored in the memory 402 or transmitted through the communication component 405. The audio assembly further comprises at least one speaker for outputting audio signals. The I/O interface 404 provides an interface between the processor 401 and other interface modules, which may be a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 405 is used for wired or wireless communication between the electronic device 400 and other devices. Wireless communication, such as Wi-Fi, bluetooth, near field communication (Near Field Communication, NFC for short), 2G, 3G, 4G, NB-IOT, eMTC, or other 5G, etc., or one or a combination of more of them, is not limited herein. The corresponding communication component 405 may thus comprise: wi-Fi module, bluetooth module, NFC module, etc.

In an exemplary embodiment, the electronic device 400 may be implemented by one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), digital signal processors (Digital Signal Processor, abbreviated as DSP), digital signal processing devices (Digital Signal Processing Device, abbreviated as DSPD), programmable logic devices (Programmable Logic Device, abbreviated as PLD), field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), controllers, microcontrollers, microprocessors, or other electronic components for performing the above-described transaction methods.

In another exemplary embodiment, a computer readable storage medium is also provided comprising program instructions which, when executed by a processor, implement the steps of the transaction method described above. For example, the computer readable storage medium may be the memory 402 described above including program instructions executable by the processor 401 of the electronic device 400 to perform the transaction method described above.

In another exemplary embodiment, a computer program product is also provided, comprising a computer program executable by a programmable apparatus, the computer program having code portions for performing the above-described transaction method when executed by the programmable apparatus.

The preferred embodiments of the present disclosure have been described in detail above with reference to the accompanying drawings, but the present disclosure is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solutions of the present disclosure within the scope of the technical concept of the present disclosure, and all the simple modifications belong to the protection scope of the present disclosure.

In addition, the specific features described in the foregoing embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, the present disclosure does not further describe various possible combinations.

Moreover, any combination between the various embodiments of the present disclosure is possible as long as it does not depart from the spirit of the present disclosure, which should also be construed as the disclosure of the present disclosure.

Claims

1. A transaction processing method, applied to a relay network, the relay network being a peer-to-peer network including a first number of relay nodes, the method comprising:

2. The method of claim 1, wherein after said sending, by the master node, an execution request to the cross-chain gateway corresponding to each of the application blockchains, the method further comprises:

3. The method of claim 1, wherein prior to the sending, by the master node, a pre-execution request to each of the application blockchain-corresponding cross-chain gateways, the method further comprises:

4. The method of claim 1, wherein the pre-execution request is used for enabling the cross-chain gateway corresponding to each application blockchain to simulate execution of the transaction request on the application blockchain, and setting target ledger data in the application blockchain to be in an occupied state, wherein the target ledger data is ledger data used when simulating execution of the transaction request;

5. The method according to claim 4, wherein the method further comprises:

6. The method according to claim 4, wherein the method further comprises:

7. The method according to claim 1, wherein the method further comprises:

8. The method of any of claims 1-7, wherein each of the relay nodes has a relay blockchain stored thereon, the method further comprising:

9. The method of claim 8, wherein the method further comprises:

10. The transaction processing method is characterized by being applied to a cross-chain gateway, wherein the cross-chain gateway corresponds to an application blockchain; the method comprises the following steps:

simulating execution of the transaction request on the application blockchain, and sending simulation execution results to the master node, so that the master node receives the simulation execution results sent by the cross-chain gateway corresponding to each application blockchain, and broadcasts each simulation execution result to each relay node; checking each simulation execution result according to a relay intelligent contract corresponding to the relay network through each relay node; under the condition that each simulation execution result passes the verification of each relay node and each simulation execution result is successful, sending an execution request to the cross-chain gateway corresponding to each application blockchain through the master node;

11. The method of claim 10, wherein said emulating execution of said transaction request on said application blockchain comprises:

the executing the transaction request on the application blockchain includes:

12. The method of claim 11, wherein the method further comprises:

13. A relay network, wherein the relay network is a peer-to-peer network comprising a first number of relay nodes;

14. A cross-chain gateway, wherein the cross-chain gateway corresponds to an application blockchain, the cross-chain gateway comprising:

the simulation execution module is used for simulating and executing the transaction request on the application blockchain, sending a simulation execution result to the master node, enabling the master node to receive the simulation execution result sent by the cross-chain gateway corresponding to each application blockchain, and broadcasting each simulation execution result to each relay node; checking each simulation execution result according to a relay intelligent contract corresponding to the relay network through each relay node; under the condition that each simulation execution result passes the verification of each relay node and each simulation execution result is successful, sending an execution request to the cross-chain gateway corresponding to each application blockchain through the master node;

15. A transaction processing system, the system comprising: the system comprises a relay network, a plurality of application blockchains and a cross-chain gateway corresponding to each application blockchain;

the relay network being adapted to perform the transaction method of any of claims 1-9;

each of the cross-chain gateways is configured to perform the transaction method of any of claims 10-12.

16. A computer readable storage medium having stored thereon a computer program, characterized in that the program when executed by a processor realizes the steps of the method of any of claims 1-9, or of claims 10-12.

17. An electronic device, comprising:

a memory having a computer program stored thereon;

a processor for executing the computer program in the memory to implement the steps of the method of any of claims 1-9 or 10-12.