CN112258183B

CN112258183B - Cross-chain private transaction method, blockchain network and electronic equipment

Info

Publication number: CN112258183B
Application number: CN202011175943.XA
Authority: CN
Inventors: 唐坤; 李成才; 邓柯
Original assignee: Chengdu Quality Starker Technology Co Ltd
Current assignee: Chengdu Quality Starker Technology Co Ltd
Priority date: 2020-10-28
Filing date: 2020-10-28
Publication date: 2023-08-01
Anticipated expiration: 2040-10-28
Also published as: CN112258183A

Abstract

The embodiment of the invention provides a cross-chain private transaction method, a blockchain network and electronic equipment, aiming at realizing private transaction of the cross-blockchain network. The cross-chain private transaction method is applied to a public blockchain network, and comprises the following steps: obtaining a public transaction, a first pre-execution result of a first blockchain network, and a second pre-execution result of a second blockchain network, wherein the public transaction is a non-private part of a cross-chain private transaction; judging whether the first blockchain network and the second blockchain network successfully pre-execute the cross-chain private transaction according to the first pre-execution result and the second pre-execution result; if yes, executing the public transaction, and returning an execution result of the public transaction to the first blockchain network and the second blockchain network, so that each blockchain network records a respective pre-execution result to each blockchain.

Description

Cross-chain private transaction method, blockchain network and electronic equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a cross-chain private transaction method, a blockchain network, and an electronic device.

Background

The block chain technology is built on a transmission network (also called a block chain network), distributed node equipment (hereinafter called nodes for short) in the transmission network realizes generation, verification and uplink storage of block data by running a block chain program, finally realizes a data tamper-proof mechanism, and provides a safe and reliable technical new idea for service development.

The blockchain technology can be applied to various business scenes, such as financial field, electronic commerce field, commodity or raw material tracing field, electronic certificate storing field and the like, and can be used for developing business due to the fact that the blockchain technology realizes a data tamper-proof mechanism, so that the trust crisis among parties involved in the business can be solved.

In the related art, each blockchain network is typically docked with a plurality of users, and a service can be deployed in the blockchain network by docking between a plurality of users of the same blockchain network. However, as business requirements continue to update and increase, there is a need to conduct transactions across block-chain networks, and in some scenarios, to satisfy the privacy of the transactions. Therefore, how to implement private transactions across blockchain networks is a technical problem to be solved.

Disclosure of Invention

The embodiment of the invention aims to provide a cross-chain private transaction method, a blockchain network and electronic equipment, and aims to realize private transaction of the cross-blockchain network. The specific technical scheme is as follows:

in a first aspect of an embodiment of the present invention, a cross-chain private transaction method is provided, applied to a public blockchain network, the method including:

obtaining a public transaction, a first pre-execution result of a first blockchain network on a cross-chain private transaction and a second pre-execution result of a second blockchain network on the cross-chain private transaction, wherein the cross-chain private transaction is a transaction between the first blockchain network and the second blockchain network, and the public transaction is a non-private part in the cross-chain private transaction;

judging whether the first blockchain network and the second blockchain network successfully pre-execute the cross-chain private transaction according to the first pre-execution result and the second pre-execution result;

if yes, executing the public transaction, and returning an execution result of the public transaction to the first blockchain network and the second blockchain network, so that the first blockchain network records the first pre-execution result to a blockchain of the first blockchain network, and the second blockchain network records the second pre-execution result to a blockchain of the second blockchain network, or the first blockchain network executes the cross-chain private transaction, records an execution result of the cross-chain private transaction to a blockchain of the first blockchain network, and the second blockchain network executes the cross-chain private transaction, and records an execution result of the cross-chain private transaction to a blockchain of the second blockchain network.

In a second aspect of the embodiments of the present invention, another cross-chain private transaction method is provided, applied to a second blockchain network, the method including:

pre-executing cross-chain private transaction to obtain a second pre-execution result, and sending the second pre-execution result to a public blockchain network, wherein the cross-chain private transaction is a transaction between a first blockchain network and a second blockchain network;

recording the second pre-execution result to a blockchain of the second blockchain network under the condition of obtaining the execution result returned by the public blockchain network, or executing the cross-chain private transaction under the condition of obtaining the execution result returned by the public blockchain network, and recording the execution result of the cross-chain private transaction to a blockchain of the second blockchain network;

wherein the execution result is obtained by the public blockchain network by: when the public blockchain network determines that the first blockchain network and the second blockchain network both successfully pre-execute the cross-chain private transaction according to a first pre-execution result of the first blockchain network and a second pre-execution result of the second blockchain network, the public blockchain network executes a public transaction to obtain the execution result, wherein the public transaction is a non-private part in the cross-chain private transaction.

In a third aspect of embodiments of the present invention, a blockchain network is provided that implements the cross-chain private transaction method provided by any of the embodiments of the present invention when the blockchain network is running.

In a fourth aspect of the embodiments of the present invention, an electronic device is provided, where the electronic device belongs to the blockchain network, and the electronic device is configured to cooperate with other electronic devices in the blockchain network to implement the cross-chain private transaction method provided by any one of the embodiments of the present invention.

By applying the cross-chain private transaction method provided by the invention, under the condition that the first blockchain network and the second blockchain network both successfully pre-execute the cross-chain private transaction, the public blockchain network executes the public transaction, so that the first blockchain network and the second blockchain network record the respective pre-execution results to the respective blockchains. In this way, the invention can avoid the occurrence of the following situations: one of the blockchain networks fails to execute the cross-chain private transaction, records the result of the execution failure in the blockchain, and the other blockchain network succeeds in executing the cross-chain private transaction, and records the result of the execution success in the blockchain, so that the two blockchain networks do not correspond to account book data of the same cross-chain private transaction. Therefore, by implementing the invention, the cross-chain transaction can be accurately and reliably realized.

In addition, the public blockchain network witnessed a cross-chain private transaction between the first blockchain network and the second blockchain network by performing a public transaction, equivalent to in the public blockchain. And because the public transaction is a non-private part in the cross-chain private transaction, the public blockchain network cannot cause disclosure on the cross-chain private transaction, and the privacy of the cross-chain transaction is ensured.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It is evident that the drawings in the following description are only some embodiments of the present invention and that other drawings may be obtained from these drawings by those of ordinary skill in the art without inventive effort.

FIG. 1 is a schematic diagram of a cross-chain private transaction system according to one embodiment of the present invention;

FIG. 2 is a flow chart of a cross-chain private transaction according to one embodiment of the invention;

FIG. 3 is a schematic representation of voting according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a transaction structure according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a public blockchain network processing transaction in accordance with an embodiment of the present invention;

FIG. 6 is a diagram illustrating a commit pre-execution result according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a transaction structure according to another embodiment of the present invention;

FIG. 8 is a schematic diagram of a public blockchain network processing transaction in accordance with another embodiment of the present invention;

FIG. 9 is a flow chart of a cross-chain private transaction method according to an embodiment of the present invention;

FIG. 10 is a flow chart of a cross-chain private transaction method according to another embodiment of the present invention;

fig. 11 is a schematic diagram of an electronic device according to an embodiment of the invention.

Description of the embodiments

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. It will be apparent that the described embodiments are some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

In view of this, the present invention proposes a cross-chain private transaction system, a cross-chain private transaction method, a blockchain network, and an electronic device through the following embodiments, which aim to implement a private transaction across the blockchain network.

Referring to fig. 1, fig. 1 is a schematic diagram of a cross-chain private transaction system according to an embodiment of the present invention. As shown in fig. 1, the cross-chain private transaction system includes: a common blockchain network, a first blockchain network, and a second blockchain network. Each blockchain network includes a plurality of distributed node devices (hereinafter referred to as nodes), each of which maintains its own set of blockchains. It should be noted that the cross-chain private transaction system may also include other blockchain networks connected to the public blockchain network, and for simplicity of the drawing, only both the first and second blockchain networks are schematically shown in fig. 1.

Alternatively, in some embodiments, intra-chain traffic, i.e., non-inter-chain traffic, may be developed within a single blockchain network. The specific service development process comprises the following steps: real data generated in the physical world is structured into a transaction format supported by the blockchain and published to the blockchain network; after each node of the blockchain network receives the transaction, processing the transaction, and recording the transaction and the processing result of the transaction to a block; the nodes mutually agree on respective blocks, and each node adds the respective block to the end of the respective stored blockchain under the condition that the consensus is reached.

It should be noted that, in the specific implementation, how to perform the service in a single blockchain network is not limited to the specific implementation. In addition to the above specific embodiments, other well-known technical solutions may be adopted by those skilled in the art, and will not be described herein.

Optionally, in some embodiments, the first blockchain network shown in fig. 1 is a federation chain or a private chain, and a plurality of nodes of the first blockchain network are operated by one or several financial institutions. The second blockchain network shown in fig. 1 is also a federation chain or a private chain, and a plurality of nodes of the second blockchain network are also operated by another financial institution or institutions.

To facilitate understanding, the first blockchain network illustratively includes 50 nodes, which are operated by respective branches of bank a. Specifically, 22 nodes are operated by a branch A1, 16 nodes are operated by a branch A2, and 12 nodes are operated by a branch A3. The second blockchain network includes 35 nodes, which are operated by respective branches of the bank B. Specifically, 15 nodes are operated by a branch B1, 12 nodes are operated by a branch B2, and 8 nodes are operated by a branch B3. Between the branches of bank a, a service may be performed in the first blockchain network. In addition, between the account a1 and the account a2 opened by the bank a, a service may be developed in the first blockchain network. And between branches of the bank B, business can be developed in the second blockchain network. In addition, between account B1 and account B2 opened by bank B, a service may also be developed in the second blockchain network.

In some cases, a need for a private transaction across the blockchain network arises between the first blockchain network and the second blockchain network. For example, if account a of bank a needs to transfer to account B of bank B and the transfer between account a and account B is desired to be kept secret, then a private transaction across the blockchain network is required between the first blockchain network and the second blockchain network. For how to implement private transactions across blockchain networks, please refer to the following, which is not repeated here.

Optionally, in some embodiments, as shown in fig. 1, the first blockchain network corresponds to one gateway (hereinafter referred to as a first gateway) and the second blockchain network corresponds to another gateway (hereinafter referred to as a second gateway).

The first gateway communicates with the first blockchain network by communicating with any node or a plurality of designated nodes in the first blockchain network, and the first gateway communicates with the public blockchain network by communicating with any node or a plurality of designated nodes in the public blockchain network. Thus, the first blockchain network is in communication connection with the public blockchain network through the first gateway.

The second gateway communicates with the second blockchain network by communicating with any node or a plurality of designated nodes in the second blockchain network, and the second gateway communicates with the public blockchain network by communicating with any node or a plurality of designated nodes in the public blockchain network. Thus, the second blockchain network is in communication connection with the public blockchain network through the second gateway.

In addition, a first gateway of the first blockchain network may be in communication with a second gateway of the second blockchain network, such that the first blockchain network is communicatively coupled to the second blockchain network through the first gateway and the second gateway.

In fig. 1, the communication connections between the various blockchain networks are represented by dashed arrows.

As previously described, in some cases, the need for a private transaction across the blockchain network arises between the first blockchain network and the second blockchain network. To implement a private transaction across a blockchain network, referring to fig. 2, fig. 2 is a flow chart of a cross-chain private transaction according to an embodiment of the invention.

It should be noted in advance that fig. 2 presented below is a general drawing. During the introduction of fig. 2, fig. 3 to 8 are introduced alternately, and fig. 3 to 8 can be regarded as a specific explanation of the content of fig. 2.

As shown in FIG. 2, the first blockchain network receives a transaction submitted by a user (shown as tx-1 in FIG. 2) that includes the following data: transaction ID, transaction type identification, public transactions, cross-chain private transactions, and ciphertext of cross-chain private transactions.

Wherein, the transaction ID is the number of the transaction tx-1, and is also the number of the cross-chain private transaction.

Wherein the transaction type identifier is used to characterize: whether the transaction involves cross-chain behavior. To facilitate understanding, illustratively, if the transaction type is identified as KL, it is stated that the transaction involves cross-chain behavior. If the transaction type is identified as GE, then it is stated that the transaction does not involve cross-chain behavior. The characters "KL" and "GE" are merely examples, and should not be construed as limiting the present invention.

Wherein, the public transaction refers to: the non-private portion of the cross-chain private transaction, the public transaction needs to be performed within the public blockchain network.

The cross-chain private transaction comprises two parts, namely a front private transaction and a rear private transaction. The front private transaction refers to: the portion of the cross-chain private transaction that needs to be performed within the first blockchain network. The post private transaction refers to: the portion of the cross-chain private transaction that needs to be performed within the second blockchain network.

For ease of understanding, assuming that account a of bank a requires 500 transfers to account B of bank B, the pre-private transaction of the cross-chain private transaction includes the following two steps: firstly, transferring 500 yuan from an account a of a first blockchain network to a main account of the first blockchain network; then, 500 elements are destroyed from the primary account of the first blockchain network.

The post-private transaction of the cross-chain private transaction comprises the following two steps: firstly, adding 500 yuan in a main account of a second blockchain network; the master account of the second blockchain network then transfers 500 yuan to account b of the second blockchain network.

The cross-chain private transaction corresponds to the public transaction and comprises the following steps: a first master account of the public blockchain network transfers 500 yuan to a second master account of the public blockchain network. Wherein the first primary account of the public blockchain network corresponds to the primary account of the first blockchain network and the second primary account of the public blockchain network corresponds to the primary account of the second blockchain network.

Therefore, the public transaction is executed in the public blockchain network, and the front private transaction and the rear private transaction of the cross-chain private transaction are not executed in the public blockchain network, so that only a first main account of the public blockchain network can be queried to transfer 500 elements to a second main account of the public blockchain network through the public blockchain network, and account a cannot be queried to transfer 500 elements to account b, thereby being beneficial to ensuring the privacy when the account a and the account b develop business.

In addition, the front private transaction can also carry: the network ID of the blockchain network that performs the pre-private transaction. The post-private transaction can also be carried: the network ID of the blockchain network that performs the post-secret transaction. Because the cross-chain private transaction in fig. 2 is a transaction between the first blockchain network and the second blockchain network, the network ID carried by the pre-private transaction is the network ID of the first blockchain network, and the network ID carried by the post-private transaction is the network ID of the second blockchain network.

As shown in FIG. 2, the first blockchain network, upon receiving transaction tx-1, votes for the cross-chain private transaction therein, thereby indicating whether the first blockchain network agrees to perform the cross-chain private transaction.

Optionally, in some embodiments, as shown in fig. 3 (fig. 3 is a voting schematic diagram according to an embodiment of the present invention), any node in the first blockchain network (for example, node a in fig. 3) first reads the transaction type identifier carried by the transaction tx-1 when receiving the transaction tx-1 submitted by the user. If the read transaction type identifies a token: transaction tx-1 relates to cross-chain behavior, transaction tx-1 is processed by the first handler of node a, which is dedicated to handling transactions involving cross-chain behavior. If the read transaction type identifies a token: transaction tx-1 does not involve cross-chain behavior, then transaction tx-1 is processed by the second handler of node a, which is dedicated to handling transactions that do not involve cross-chain behavior, i.e., transactions within the blockchain network.

In the event that it is determined that transaction tx-1 involves cross-chain behavior, node a sends transaction tx-1 to a plurality of designated nodes within the first blockchain network by running a first handler, as shown in fig. 3. Each designated node, upon receiving transaction tx-1, votes for transaction tx-1 and submits the vote to node a, indicating whether the designated node agrees to perform the cross-chain private transaction carried in transaction tx-1.

Each designated node may read, for example, the business parameters of the cross-chain private transaction carried by transaction tx-1, such as the transfer user address, the recipient user address, the transfer quantity, the asset type, etc., at the time of voting. And judging whether the read service parameters meet the preset service requirements, if so, the appointed node throws a ticket representing consent to execution, and if not, the appointed node throws a ticket representing disagreement to execution.

Alternatively, each designated node may display transaction tx-1 to the administrator of the designated node and receive the administrator's vote for transaction tx-1, for example, at the time of the vote. The administrator's vote is used to characterize: whether the designated node agrees to perform the cross-chain private transaction carried in transaction tx-1.

It should be noted that the above two voting methods are merely examples, and the present invention may be implemented in a manner different from the above two voting methods.

As shown in FIG. 2, after the voting of the first blockchain network is completed, the first blockchain network transmits the transaction tx-1 and the voting of the first blockchain network to the second blockchain network.

Specifically, as shown in FIG. 2, the first blockchain network may populate the votes of the first blockchain network to transaction tx-1, and then send the voted transaction tx-1 to the second blockchain network, causing the second blockchain network to vote on the cross-chain private transaction.

Alternatively, in some embodiments, as shown in FIG. 3, node A of the first blockchain network may submit the transaction tx-1 and multiple votes to the master node of the first blockchain network upon receipt of the votes submitted by the respective designated nodes. After receiving the transaction tx-1 and the multiple votes, the master node fills the multiple votes into the transaction tx-1, reads the network ID from the post-secret transaction of the transaction tx-1, and sends the transaction tx-1 to the gateway corresponding to the network ID, i.e. the second gateway shown in fig. 3, through the first gateway. After the second gateway receives transaction tx-1, transaction tx-1 is submitted to any node within the second blockchain network (e.g., node Y in fig. 3). As such, the first blockchain network successfully transmits the transaction tx-1 to the second blockchain network such that the second blockchain network obtains the transaction tx-1 and the votes of the first blockchain network carried by the transaction tx-1.

As shown in FIG. 2, the second blockchain network, upon receiving transaction tx-1, votes for the cross-chain private transaction therein, thereby indicating whether the second blockchain network agrees to perform the cross-chain private transaction.

Optionally, in some embodiments, as shown in fig. 3, after receiving the transaction tx-1 submitted by the first blockchain network through the gateway, the node Y in the first blockchain network first reads the transaction type identifier carried by the transaction tx-1. If the read transaction type identifies a token: transaction tx-1 relates to cross-chain behavior, transaction tx-1 is processed by the first handler of node Y, which is dedicated to handling transactions involving cross-chain behavior. If the read transaction type identifies a token: transaction tx-1 does not involve cross-chain behavior, then transaction tx-1 is processed by a second handler of node Y that is dedicated to handling transactions that do not involve cross-chain behavior, i.e., transactions within the blockchain network.

In the event that it is determined that transaction tx-1 involves cross-chain behavior, node Y sends transaction tx-1 to a plurality of designated nodes within the second blockchain network by running a first handler, as shown in fig. 3. Each designated node, upon receiving transaction tx-1, votes for transaction tx-1 and submits the vote to node Y, indicating whether the designated node agrees to perform the cross-chain private transaction carried in transaction tx-1.

As shown in fig. 2, after the voting of the second blockchain network is completed, the second blockchain network transmits the following data to the common blockchain network: voting of a first blockchain network, voting of a second blockchain network, public transactions, and ciphertext of a cross-chain private transaction.

Specifically, the second blockchain network may populate a vote of the second blockchain network to transaction tx-1 and delete the cross-chain private transaction carried by transaction tx-1 from transaction tx-1, and generate and assign a new transaction ID to transaction tx-1 to form a new transaction (shown in fig. 2 and 3 as tx-2). The second blockchain network then sends the transaction tx-2 to the public blockchain network, such that the public blockchain network, upon receiving the transaction tx-2, can obtain from the transaction tx-2: voting of the first blockchain network, voting of the second blockchain network, public transactions, ciphertext of cross-chain private transactions, and the like.

Referring to fig. 4, fig. 4 is a schematic diagram of a transaction structure according to an embodiment of the invention. As shown in fig. 4, the new transaction (i.e., transaction tx-2) includes the following: the newly generated transaction ID (i.e., the transaction ID of transaction tx-2), the original transaction ID (i.e., the transaction ID of transaction tx-1, the transaction ID of the cross-chain private transaction), the transaction type identification, the public transaction, the ciphertext of the cross-chain private transaction, the vote of the first blockchain network, and the vote of the second blockchain network. In fig. 4, the cross-chain private transaction is shown by the cross-line drawn, indicating that the cross-chain private transaction is deleted from the transaction tx-2 sent by the second blockchain network to the main network.

Alternatively, in some embodiments, as shown in FIG. 3, node Y of the second blockchain network may submit the transaction tx-1 and multiple votes to the master node of the second blockchain network upon receipt of the votes submitted by the respective designated nodes. After receiving the transaction tx-1 and the multiple votes, the master node fills the multiple votes into the transaction tx-1, deletes the cross-link private transaction carried by the tx-1 from the transaction tx-1, generates a new transaction ID, and assigns the new transaction ID to the transaction tx-1 to form a new transaction, namely the transaction tx-2. The master node then sends the transaction tx-2 to any node within the public blockchain network through the second gateway. As such, the second blockchain network successfully transmits the transaction tx-2 to the public blockchain network such that the public blockchain network obtains the ciphertext of the first blockchain network's votes, the second blockchain network's votes, the public transactions, and the cross-chain private transactions.

As shown in FIG. 2, after receiving transaction tx-2, the public blockchain network determines whether the first blockchain network and the second blockchain network agree to execute a cross-chain private transaction based on the votes of the first blockchain network and the votes of the second blockchain network carried by transaction tx-2.

In particular, the public blockchain network determines whether the first blockchain network agrees to execute cross-chain private transactions based on preset judgment rules according to votes of each designated node of the first blockchain network. For ease of understanding, illustratively, the judgment rule is, for example: if the number of votes characterizing consent to execution in all votes for a blockchain network exceeds a predetermined proportion (e.g., 60%) of the number of all designated nodes for the blockchain network, then it is determined that the blockchain network consents to execution of a cross-chain private transaction. Assuming that the number of all designated nodes of the first blockchain network is 20 and that the number of votes characterizing consent to execution is 18 among all votes for the first blockchain network, the first blockchain network is determined to consent to execution of the cross-chain private transaction because the number of votes 18 exceeds 60% of 20.

In addition, the public blockchain network determines whether the second blockchain network agrees to perform cross-chain private transactions based on the same manner.

It should be noted that the above determination rule is only an example, and should not be construed as limiting the present invention. In the specific implementation of the present invention, other judgment rules different from the above judgment rules may be adopted.

Optionally, in some embodiments, as shown in fig. 5 (fig. 5 is a schematic diagram of a public blockchain network processing transaction according to an embodiment of the present invention), any node in the public blockchain network (e.g., node 3 in fig. 5) submits transaction tx-2 to a master node in the public blockchain network after receiving transaction tx-2 submitted by the second blockchain network.

As shown in FIG. 5, the master node is responsive to transaction tx-2 to generate a transaction envelope for transaction tx-2, which carries transaction tx-2 and the height of the transaction envelope. The master node distributes the generated transaction package to each node within the common blockchain network, and the process of the master node transmitting the transaction package to a portion of the nodes is only schematically shown in fig. 5 for simplicity of the drawing. After each node receives the transaction package, the transaction tx-2 carried in the transaction package is processed. Each node, when processing transaction tx-2, specifically, as previously described, determines whether the first blockchain network agrees to perform a cross-chain private transaction based on a preset decision rule based on votes from the respective designated nodes of the first blockchain network. And determining whether the second blockchain network agrees to execute the cross-chain private transaction according to the votes of all the designated nodes of the second blockchain network and based on a preset judgment rule.

Finally, each node determines whether the first blockchain network and the second blockchain network both agree to perform cross-chain private transactions. Each node stores the respective judgment result and the transaction tx-2 into the respective block to be uplinked, and sets the block height of the block to be uplinked as the height of the transaction package. And then, the nodes mutually share the blocks to be uplinked, and under the condition that the mutual identification is passed, each node adds the blocks to be uplinked to the tail end of the blockchain stored by each node.

As shown in fig. 2, when the public blockchain network determines that both the first blockchain network and the second blockchain network agree to perform the cross-chain private transaction, the public blockchain network returns a pre-execution hint to the first blockchain network and the second blockchain network so that the first blockchain network and the second blockchain network pre-execute the cross-chain private transaction.

Optionally, in some embodiments, as shown in fig. 5, any node (e.g., node 6) within the common blockchain network sends its block to the first gateway after determining that it is to be uplink to the block through consensus. Any node within the common blockchain network (e.g., node 3) sends its block to the second gateway after determining that it is to be uplinked through consensus.

After the first gateway obtains a block of the common blockchain network, each node of the first blockchain network obtains the block from the first gateway. The judgment result recorded in the block is used as a pre-execution prompt, and if the judgment result is: the first blockchain network and the second blockchain network both agree to perform the cross-chain private transaction, the first blockchain network will pre-perform the operation on the cross-chain private transaction. Otherwise, the first blockchain network does not pre-execute operations on the cross-chain private transactions.

Likewise, after obtaining a block of the common blockchain network, the second gateway obtains the block from the second gateway by each node of the second blockchain network. The judgment result recorded in the block is used as a pre-execution prompt, and if the judgment result is: the first blockchain network and the second blockchain network both agree to perform the cross-chain private transaction, and the second blockchain network will pre-perform the operation on the cross-chain private transaction. Otherwise, the second blockchain network does not pre-execute operations on the cross-chain private transaction.

Wherein, the first blockchain network may include the following sub-steps when pre-executing a cross-chain private transaction:

(1) After any node of the first blockchain network obtains a block of the common blockchain network from the first gateway, if the judgment result of the block record is: the first blockchain network and the second blockchain network both agree to perform a cross-chain private transaction, the node reads the original transaction ID from the transaction tx-2 recorded by the block.

(2) And the node locally determines the cross-chain private transaction corresponding to the original transaction ID according to the read original transaction ID.

(3) The node executes the determined front-end private transaction of the cross-link private transaction in the memory of the node to obtain an execution result of the front-end private transaction.

(4) The node records the execution result to a blockchain independent database, i.e., a non-ledger database. The node does not record the execution result of the front private transaction to the account database related to the blockchain, so the execution result of the front private transaction is not preserved by the uplink.

Accordingly, when the second blockchain network pre-executes the cross-chain private transaction, the second blockchain network can execute the post private transaction of the corresponding cross-chain private transaction in the memory of the node in the same manner as the first blockchain network, and record the execution result to a database irrelevant to the blockchain, namely a non-account database.

As shown in fig. 2, after the first and second blockchain networks pre-execute the cross-chain private transaction, the pre-execution results are sent to the public blockchain network. In fig. 2, the pre-execution result of the first blockchain network is denoted as a first pre-execution result, and the pre-execution result of the second blockchain network is denoted as a second pre-execution result. The second blockchain network firstly sends the second pre-execution result to the first blockchain network, and then the first blockchain network submits the first pre-execution result and the second pre-execution result to the public blockchain network in a unified way.

Optionally, in some embodiments, as shown in fig. 6 (fig. 6 is a schematic diagram illustrating submitting pre-execution results according to an embodiment of the present invention), each node of the first blockchain network sends, as the pre-execution result, the execution result of the pre-private transaction stored in its non-ledger database to the master node of the first blockchain network. Similarly, each node of the second blockchain network sends the execution result of the post-private transaction stored in its non-ledger database as a pre-execution result to the master node of the second blockchain network. In addition, the master node of the second blockchain network sends the collected pre-execution result to the master node of the first blockchain network through the second gateway and the first gateway. To simplify the drawing, only a partial node is schematically shown in fig. 6 submitting the pre-execution result to the master node.

As shown in FIG. 6, after obtaining the pre-execution results of each node in the first blockchain network and the pre-execution results of each node in the second blockchain network, the master node of the first blockchain network extracts transaction tx-2 from the blocks of the common blockchain network and populates the pre-execution results of each node in the first blockchain network and the pre-execution results of each node in the second blockchain network to transaction tx-2. In addition, the master node of the first blockchain network assigns an original transaction ID to tx-2 to form a new transaction (shown as tx-3 in FIGS. 2 and 6). The master node of the first blockchain network then sends the transaction tx-3 to any node within the public blockchain network through the first gateway. As such, the first blockchain network successfully sends the transaction tx-3 to the common blockchain network such that the common blockchain network obtains the pre-execution results of each of the first and second blockchain networks.

In the present invention, since the transaction ID of the transaction tx-3 is the original transaction ID, the original transaction ID is the transaction ID grasped by the user. And as described below, as the public blockchain network processes transaction tx-3, the public transaction carried in transaction tx-3 is executed and the execution result of the public transaction is recorded to the blockchain. Therefore, the user can inquire the execution result of the public transaction in the public blockchain by utilizing the mastered original transaction ID, and the user experience is improved.

Referring to fig. 7, fig. 7 is a schematic diagram of a transaction structure according to another embodiment of the present invention. As shown in fig. 7, the new transaction (i.e., transaction tx-3) includes the following: the original transaction ID (i.e., the transaction ID of the cross-chain private transaction, transaction tx-1, and transaction tx-3), the transaction type identification, the public transaction, the ciphertext of the cross-chain private transaction, the vote of the first blockchain network, the vote of the second blockchain network, the pre-execution result of the first blockchain network, and the pre-execution result of the second blockchain network.

As shown in fig. 2, after the first pre-execution result and the second pre-execution result are obtained, the public blockchain network determines whether the first blockchain network and the second blockchain network both successfully pre-execute the cross-chain private transaction according to the first pre-execution result and the second pre-execution result.

In addition, as shown in fig. 2, when the public blockchain network determines that both the first blockchain network and the second blockchain network successfully pre-perform the cross-chain private transaction, the public blockchain network performs the public transaction and returns the execution result of the public transaction to the first blockchain network and the second blockchain network, so that the first blockchain network records the first pre-execution result to the blockchain of the first blockchain network and the second blockchain network records the second pre-execution result to the blockchain of the second blockchain network.

Or when the public blockchain network determines that the first blockchain network and the second blockchain network both successfully pre-execute the cross-chain private transaction, the public blockchain network executes the public transaction and returns an execution result of the public transaction to the first blockchain network and the second blockchain network, so that the first blockchain network executes the cross-chain private transaction, records an execution result of the cross-chain private transaction to a blockchain of the first blockchain network, and causes the second blockchain network to execute the cross-chain private transaction, and records an execution result of the cross-chain private transaction to a blockchain of the second blockchain network.

In particular, when the public blockchain network is implemented, according to the pre-execution result of each node in the first blockchain network on the pre-private transaction, whether the first blockchain network successfully pre-executes the cross-chain private transaction is determined based on a preset judgment rule. For ease of understanding, illustratively, the judgment rule is, for example: if the pre-execution result, which characterizes the success of the pre-execution, in all the pre-execution results of one blockchain network exceeds a preset proportion (for example, 60%) of the total number of nodes of the blockchain network, then the blockchain network is determined to successfully pre-execute the cross-chain private transaction. Assuming that the number of all nodes of the first blockchain network is 50 and that the number of pre-executions that characterize pre-execution success is 47 out of all votes for the first blockchain network, the first blockchain network is determined to have successfully pre-executed the cross-chain private transaction because 47 exceeds 60% of 50.

In addition, the public blockchain network determines whether the second blockchain network successfully pre-performed the cross-chain private transaction based on the same manner.

Optionally, in some embodiments, as shown in FIG. 8 (FIG. 8 is a schematic diagram of a public blockchain network processing transactions proposed by another embodiment of the present invention), any node within the public blockchain network (e.g., node 6 in FIG. 8) submits transaction tx-3 to a master node within the public blockchain network upon receiving transaction tx-3 submitted by the first blockchain network.

As shown in FIG. 8, the master node is responsive to transaction tx-3 to generate a transaction envelope for transaction tx-3, which carries transaction tx-3 and the height of the transaction envelope. The master node distributes the generated transaction package to each node within the common blockchain network, and the process of the master node transmitting the transaction package to a portion of the nodes is only schematically shown in fig. 8 for simplicity of the drawing. After each node receives the transaction package, the transaction tx-3 carried in the transaction package is processed. Each node, when processing a transaction tx-3, may specifically comprise the sub-steps of:

(1) As described above, according to the pre-execution result of each node in the first blockchain network on the pre-private transaction, and based on the preset judgment rule, determining whether the first blockchain network successfully pre-executes the cross-chain private transaction; and determining whether the second blockchain network successfully pre-executes the cross-chain private transaction or not according to a pre-execution result of each node in the second blockchain network on the post-private transaction and based on a preset judgment rule.

(2) If it is judged that: the first blockchain network and the second blockchain network successfully pre-execute the cross-chain private transaction, and then execute the public transaction in the transaction tx-3 to obtain an execution result of the public transaction; and then storing the execution result of the public transaction and the transaction tx-3 into a block to be uplinked of the node, and setting the block height of the block to be uplinked as the height of the transaction package.

And then, the nodes mutually share the blocks to be uplinked, and under the condition that the mutual identification is passed, each node adds the blocks to be uplinked to the tail end of the blockchain stored by each node.

Optionally, in some embodiments, as shown in fig. 8, any node (e.g., node 6) within the common blockchain network sends its block to the first gateway after determining that it is to be uplink to the block through consensus. Any node within the common blockchain network (e.g., node 3) sends its block to the second gateway after determining that it is to be uplinked through consensus.

After the first gateway obtains a block of the common blockchain network, each node of the first blockchain network obtains the block from the first gateway. For any node in the first blockchain network, if the execution result of the blockrecord represents that the execution of the public transaction is successful, the node records the stored execution result of the front private transaction to the blockchain of the node. If the block records the execution result of the public transaction, or if the block does not record the execution result of the public transaction, the node does not record the stored execution result of the front private transaction to the blockchain.

Likewise, after obtaining a block of the common blockchain network, the second gateway obtains the block from the second gateway by each node of the second blockchain network. For any node in the second blockchain network, if the execution result of the blockrecord represents that the execution of the public transaction is successful, the node records the stored execution result of the post private transaction to the blockchain of the node. If the block records the execution result of the public transaction, or if the block does not record the execution result of the public transaction, the node does not record the stored execution result of the post private transaction to the blockchain.

Above, the present invention provides a process of private transaction by a cross-block chain network through a preferred embodiment. In the above process, under the condition that the first blockchain network and the second blockchain network both successfully pre-execute the cross-chain private transaction, the public blockchain network executes the public transaction, so that the first blockchain network and the second blockchain network record respective pre-execution results to respective blockchains. In this way, the invention can avoid the occurrence of the following situations: one of the blockchain networks fails to execute the cross-chain private transaction, records the result of the execution failure in the blockchain, and the other blockchain network succeeds in executing the cross-chain private transaction, and records the result of the execution success in the blockchain, so that the two blockchain networks do not correspond to account book data of the same cross-chain private transaction. It should be noted that reasons for the failure of the execution of the cross-chain private transaction include, but are not limited to: insufficient balance, no transaction right, no satisfaction of time conditions or place conditions, etc.

Therefore, by implementing the invention, the cross-chain transaction can be accurately and reliably realized. In addition, the public blockchain network witnessed a cross-chain private transaction between the first blockchain network and the second blockchain network by performing a public transaction, equivalent to in the public blockchain. And because the public transaction is a non-private part in the cross-chain private transaction, the public blockchain network cannot cause disclosure on the cross-chain private transaction, and the privacy of the cross-chain transaction is ensured.

In the following, the present invention proposes a cross-chain private transaction method by other embodiments. For some of the following embodiments, reference may be made to the preferred embodiments described above.

Referring to fig. 9, fig. 9 is a flowchart of a cross-chain private transaction method according to an embodiment of the present invention, where the cross-chain private transaction method is applied to a public blockchain network. As shown in fig. 9, the cross-chain private transaction method includes the following steps:

step S91: obtaining a public transaction, a first pre-execution result of a first blockchain network on a cross-chain private transaction and a second pre-execution result of a second blockchain network on the cross-chain private transaction, wherein the cross-chain private transaction is a transaction between the first blockchain network and the second blockchain network, and the public transaction is a non-private part in the cross-chain private transaction.

Wherein the first pre-execution result of the first blockchain network refers to: and after the first blockchain network pre-executes the cross-chain private transaction, a pre-execution result is obtained. The second pre-execution result of the second blockchain network refers to: and after the second blockchain network pre-executes the cross-chain private transaction, a pre-execution result is obtained.

With reference to the foregoing preferred embodiment, specifically, an execution result obtained after each node in the first blockchain network executes a pre-private transaction of a cross-chain private transaction in its own memory is used as a pre-execution result of the node. The pre-execution result of each of the plurality of nodes in the first blockchain network is used as the pre-execution result of the whole first blockchain network. The pre-execution result of each node is "true" or "false", and if the pre-execution result of one node is "true", the pre-execution result indicates that the node successfully pre-executes the pre-private transaction of the cross-link private transaction.

Similarly, each node in the second blockchain network performs the execution result obtained after the post-private transaction of the cross-chain private transaction in the respective memory thereof, and the execution result is used as the pre-execution result of the node. And the pre-execution result of each of the plurality of nodes in the second blockchain network is used as the pre-execution result of the whole second blockchain network. The pre-execution result of each node is "true" or "false", and if the pre-execution result of one node is "true", the node successfully pre-executes the post-private transaction of the cross-chain private transaction.

Step S92: and judging whether the first blockchain network and the second blockchain network successfully pre-execute the cross-chain private transaction according to the first pre-execution result and the second pre-execution result.

Optionally, in some specific embodiments, referring to the foregoing preferred embodiment, the public blockchain network may determine whether the first blockchain network successfully pre-performs the cross-chain private transaction according to a pre-performed result of each node in the first blockchain network on the pre-private transaction, and based on a preset judgment rule. Similarly, the public blockchain network may determine whether the second blockchain network successfully pre-performs the cross-chain private transaction based on a preset determination rule according to a pre-performed result of each node in the second blockchain network on the post-private transaction.

Step S93: if yes, executing the public transaction, and returning an execution result of the public transaction to the first blockchain network and the second blockchain network, so that the first blockchain network records the first pre-execution result to a blockchain of the first blockchain network, and the second blockchain network records the second pre-execution result to a blockchain of the second blockchain network.

Optionally, referring to the foregoing preferred embodiment, in some specific embodiments, the public blockchain network performs the public transaction, and after obtaining the execution result of the public transaction, records the execution result of the public transaction into a block of the public blockchain network. And then returning the block to the first block chain network and the second block chain network, so that the first block chain network obtains the block and reads the execution result recorded in the block, records the first pre-execution result to the block chain of the first block chain network, and the second block chain network obtains the block and reads the execution result recorded in the block, and records the second pre-execution result to the block chain of the second block chain network.

Optionally, in other embodiments, the public blockchain network performs the public transaction, and after obtaining the execution result of the public transaction, directly sends the execution result to the first blockchain network and the second blockchain network.

As described above, by applying the cross-chain private transaction method provided by the invention, under the condition that both the first blockchain network and the second blockchain network successfully pre-execute the cross-chain private transaction, the public blockchain network executes the public transaction, so that the first blockchain network and the second blockchain network record the respective pre-execution results to the respective blockchains. In this way, the invention can avoid the occurrence of the following situations: one of the blockchain networks fails to execute the cross-chain private transaction, records the result of the execution failure in the blockchain, and the other blockchain network succeeds in executing the cross-chain private transaction, and records the result of the execution success in the blockchain, so that the two blockchain networks do not correspond to account book data of the same cross-chain private transaction. Therefore, by implementing the invention, the cross-chain transaction can be accurately and reliably realized.

Optionally, in some embodiments, the cross-chain private transaction is a transaction between a first account of a first financial institution and a second account of a second financial institution; the public transaction is a transaction between the first financial institution and the second financial institution. Wherein the first financial institution interfaces with the first blockchain network and the second financial institution interfaces with the second blockchain network.

For ease of understanding, reference is made to the foregoing preferred embodiments, such as a cross-chain private transaction: bank a's account a transfers 500 yuan to bank B's account B. The corresponding public transactions are: bank a transfers 500 yuan to bank B. Wherein bank A interfaces with a first blockchain network and bank B interfaces with a second blockchain network.

Optionally, in some embodiments, the public blockchain network further performs the following steps before obtaining the public transaction, the first pre-execution result, and the second pre-execution result, i.e., before step S91:

(1) A first vote of the first blockchain network is obtained that characterizes whether the first blockchain network agrees to perform the cross-chain private transaction and a second vote of the second blockchain network is obtained that characterizes whether the second blockchain network agrees to perform the cross-chain private transaction.

(2) And judging whether the first blockchain network and the second blockchain network agree to execute the cross-chain private transaction according to the first vote and the second vote.

(3) If yes, a pre-execution prompt is returned to the first blockchain network and the second blockchain network, so that the first blockchain network and the second blockchain network pre-execute the cross-chain private transaction.

Wherein the first vote of the first blockchain network refers to: voting data obtained after voting the cross-chain private transaction by the first blockchain network. The second vote of the second blockchain network refers to: voting data obtained after voting the cross-chain private transaction by the second blockchain network.

With reference to the foregoing preferred embodiment, specifically, after voting on a cross-chain private transaction, a designated node in the first blockchain network obtains voting data of the designated node. Voting data of each of a plurality of designated nodes in the first blockchain network is used as voting data of the whole first blockchain network. Wherein the voting data of each designated node is shaped as "true" or "false", and if the voting data of one designated node is "true", the designated node agrees to execute the cross-chain private transaction.

Similarly, the designated node in the second blockchain network obtains voting data of the designated node after voting the cross-chain private transaction. Voting data of each of a plurality of designated nodes in the second blockchain network is used as voting data of the whole second blockchain network. Wherein the voting data of each designated node is shaped as "true" or "false", and if the voting data of one designated node is "true", the designated node agrees to execute the cross-chain private transaction.

The public blockchain network determines whether the first blockchain network agrees to execute the cross-chain private transaction according to the first vote and the second vote, specifically, with reference to the preferred embodiment, the public blockchain network determines whether the first blockchain network agrees to execute the cross-chain private transaction according to the votes of each designated node of the first blockchain network based on a preset determination rule. Similarly, the public blockchain network determines whether the second blockchain network agrees to execute the cross-chain private transaction based on the preset judgment rules according to the votes of the designated nodes of the second blockchain network.

In order to return the pre-execution hint to the first blockchain network and the second blockchain network, referring to the preferred embodiment, the public blockchain network may record the judgment result as the pre-execution hint in a block of the public blockchain network, and return the block to the first blockchain network and the second blockchain network, so that the first blockchain network and the second blockchain network may read the pre-execution hint from the block.

Alternatively, the common blockchain network may send the pre-execution hint information directly to the first and second blockchain networks in order for the common blockchain network to return the pre-execution hint to the first and second blockchain networks.

Optionally, in some embodiments, the public blockchain network obtains the transaction ID of the cross-chain private transaction along with the first vote and the second vote.

Illustratively, with reference to the foregoing preferred embodiment, the common blockchain network obtains a transaction tx-2 submitted by the second blockchain network, the transaction tx-2 including at least: transaction ID of transaction tx-1 (i.e., transaction ID of cross-chain private transaction), public transaction, vote of a first blockchain network, and vote of a second blockchain network.

Optionally, in some embodiments, when the public blockchain network returns the pre-execution hint to the first blockchain network and the second blockchain network, specifically, returns the pre-execution hint to the first blockchain network and the second blockchain network, the pre-execution hint carries a transaction ID of the cross-chain private transaction, so that the first blockchain network obtains the corresponding cross-chain private transaction from the local according to the transaction ID carried by the pre-execution hint and pre-executes the cross-chain private transaction, and the second blockchain network obtains the corresponding cross-chain private transaction from the local according to the transaction ID carried by the pre-execution hint and pre-executes the cross-chain private transaction.

For example, with reference to the foregoing preferred embodiment, the public blockchain network may take the determination result as a pre-execution hint and record the determination result into a block of the public blockchain network. In addition, the common blockchain network also records transaction tx-2 into the block. Since transaction tx-2 includes the transaction ID of the cross-chain private transaction, both the pre-execution hint and the transaction ID of the cross-chain private transaction are included in the tile. The common blockchain network then returns the block to the first and second blockchain networks such that the first and second blockchain networks can read the transaction ID of the pre-execution hint and cross-chain private transaction from the block.

Alternatively, in some embodiments, the public blockchain network may obtain the transaction ID of the first vote, the second vote, and the cross-chain private transaction by:

obtaining a first public chain transaction submitted by a first block chain network or a second block chain network, wherein the first public chain transaction is carried: the first vote, the second vote, and the transaction ID of the cross-chain private transaction. Illustratively, with reference to the foregoing preferred embodiment, the transaction tx-2 submitted by the second blockchain network to the public blockchain network, namely the first public chain transaction described above.

Optionally, in some embodiments, when the public blockchain network determines whether the first blockchain network and the second blockchain network both agree to execute the cross-chain private transaction according to the first vote and the second vote, specifically, the public blockchain network responds to the first public chain transaction, determines whether the first blockchain network and the second blockchain network both agree to execute the cross-chain private transaction according to the first vote and the second vote carried by the first public chain transaction, and writes the determination result and the transaction ID carried by the first public chain transaction into the first block of the public blockchain network.

Optionally, in some embodiments, when the common blockchain network returns the pre-execution hint to the first blockchain network and the second blockchain network, specifically, the first block is returned to the first blockchain network and the second blockchain network, where the judgment result recorded in the first block is used as the pre-execution hint.

Optionally, in some embodiments, the public blockchain network may obtain the public transaction, the first pre-execution result, and the second pre-execution result by:

obtaining a second public chain transaction submitted by the first block chain network or the second block chain network, wherein the second public chain transaction is carried: a transaction, a first pre-execution result, and a second pre-execution result are disclosed. Illustratively, with reference to the foregoing preferred embodiment, the transaction tx-3 submitted by the first blockchain network to the public blockchain network, namely the second public chain transaction described above.

Optionally, in some embodiments, when the public blockchain network determines whether the first blockchain network and the second blockchain network both successfully pre-execute the cross-chain private transaction according to the first pre-execution result and the second pre-execution result, specifically, the public blockchain network responds to the second public chain transaction, and determines whether the first blockchain network and the second blockchain network both successfully pre-execute the cross-chain private transaction according to the first pre-execution result and the second pre-execution result carried by the second public chain transaction.

Optionally, in some embodiments, the public blockchain network is configured to return an execution result of the public transaction to the first blockchain network and the second blockchain network, specifically, the public blockchain network executes the public transaction recorded in the second public chain transaction and writes the execution result of the public transaction to the second block of the public blockchain network, and return the second block to the first blockchain network and the second blockchain network.

Referring to fig. 10, fig. 10 is a flowchart of a cross-chain private transaction method according to another embodiment of the present invention, where the cross-chain private transaction method is applied to a second blockchain network. As shown in fig. 10, the cross-chain private transaction method includes the following steps:

Step S101: pre-executing a cross-chain private transaction to obtain a second pre-execution result, and sending the second pre-execution result to a public blockchain network, wherein the cross-chain private transaction is a transaction between a first blockchain network and the second blockchain network.

Optionally, in some embodiments, referring to the foregoing preferred embodiment, each node in the second blockchain network performs, in its own memory, an execution result obtained after performing a post-private transaction of the cross-chain private transaction as a pre-execution result of the node. And the pre-execution result of each of the plurality of nodes in the second blockchain network is used as the pre-execution result of the whole second blockchain network. The pre-execution result of each node is "true" or "false", and if the pre-execution result of one node is "true", the node successfully pre-executes the post-private transaction of the cross-chain private transaction.

Step S102: recording the second pre-execution result to a blockchain of the second blockchain network under the condition that the execution result returned by the public blockchain network is obtained, or executing the cross-chain private transaction under the condition that the execution result returned by the public blockchain network is obtained, and recording the execution result of the cross-chain private transaction to a blockchain of the second blockchain network.

Optionally, in some embodiments, as previously described, the first blockchain network further performs the following steps prior to pre-performing the cross-chain private transaction, i.e., prior to step S101:

(1) Receiving a first private chain transaction sent by the first blockchain network, wherein the first private chain transaction carries: the cross-chain private transaction, the public transaction, and a first vote of the first blockchain network, wherein the first vote is used to characterize whether the first blockchain network agrees to perform the cross-chain private transaction.

(2) In response to the first private chain transaction, voting the cross-chain private transaction to obtain a second vote, the second vote being used to characterize whether the second blockchain network agrees to perform the cross-chain private transaction.

(3) And sending the public transaction, the first vote and the second vote to the public blockchain network, so that the public blockchain network judges whether the first blockchain network and the second blockchain network agree to execute the cross-chain private transaction according to the first vote and the second vote, and returns a pre-execution prompt to the first blockchain network and the second blockchain network under the condition that the first and the second votes agree to execute the cross-chain private transaction.

With reference to the foregoing preferred embodiment, the transaction tx-1 sent by the first blockchain network to the second blockchain network is the first private chain transaction.

Wherein, in order for the second blockchain network to send the public transaction, the first vote, and the second vote to the public blockchain network, referring to the preferred embodiment described above, the second blockchain network may encapsulate the public transaction, the first vote, and the second vote into the transaction tx-2 described above and submit the transaction tx-2 to the public blockchain network.

Optionally, in some embodiments, the first blockchain network pre-executes the cross-chain private transaction when pre-executing the cross-chain private transaction, in particular, the first blockchain network pre-executes the cross-chain private transaction in response to a pre-execution hint returned by the public blockchain network.

Optionally, in some specific embodiments, the first blockchain network sends the public chain transaction, the first vote and the second vote to the public blockchain network, and simultaneously sends the transaction ID of the cross-chain private transaction to the public blockchain network, so that the public blockchain network judges whether the first blockchain network and the second blockchain network agree to execute the cross-chain private transaction according to the first vote and the second vote, and if so, returns a pre-execution prompt to the first blockchain network and the second blockchain network, wherein the pre-execution prompt carries the transaction ID of the cross-chain private transaction.

Illustratively, with reference to the foregoing preferred embodiment, the second blockchain network submits a transaction tx-2 to the public blockchain network, the transaction tx-2 including at least: the transaction ID of transaction tx-1 (i.e., the transaction ID of the cross-chain private transaction), the public transaction, the vote of the first blockchain network (i.e., the first vote), and the vote of the second blockchain network (i.e., the second vote).

Optionally, in some embodiments, the second blockchain network, upon pre-executing the cross-chain private transaction in response to a pre-execution hint returned by the public blockchain network, specifically: the second blockchain network responds to the pre-execution prompt returned by the public blockchain network, obtains corresponding cross-chain private transaction from the local according to the transaction ID carried by the pre-execution prompt, and pre-executes the cross-chain private transaction.

Based on the same inventive concept, the embodiment of the present invention further provides a blockchain network, which implements the method steps in any of the method embodiments described above when running.

Based on the same inventive concept, the embodiment of the invention also provides electronic equipment, which belongs to the block chain network. As shown in fig. 11, the device includes a processor 1101, a communication interface 1102, a memory 1103 and a communication bus 1104, wherein the processor 1101, the communication interface 1102 and the memory 1103 communicate with each other through the communication bus 1104.

The memory 1103 is used for storing a computer program;

the processor 1101 is configured to cooperate with other electronic devices in the blockchain network when executing the program stored on the memory 1103, so as to implement the following steps:

Alternatively, the processor 1101 is configured to implement the following steps when executing a program stored on the memory 1103:

Alternatively, the processor 1101 is configured to implement the steps of the cross-chain private transaction method provided by the other method embodiments of the present invention when executing the program stored on the memory 1103.

The communication bus mentioned by the above electronic device may be a peripheral component interconnect standard (Peripheral Component Interconnect, abbreviated as PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated as EISA) bus, or the like. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.

The communication interface is used for communication between the electronic device and other devices.

The memory may include random access memory (Random Access Memory, RAM) or non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.

The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU for short), a network processor (Network Processor, NP for short), etc.; but also digital signal processors (Digital Signal Processing, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), field-programmable gate arrays (Field-Programmable Gate Array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The foregoing is merely a partial embodiment of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A cross-chain private transaction method, applied to a public blockchain network, the method comprising:

obtaining a first vote of a first blockchain network for characterizing whether the first blockchain network agrees to perform the cross-chain private transaction and a second vote of a second blockchain network for characterizing whether the second blockchain network agrees to perform the cross-chain private transaction;

judging whether the first blockchain network and the second blockchain network agree to execute the cross-chain private transaction according to the first vote and the second vote;

if yes, a pre-execution prompt is returned to the first blockchain network and the second blockchain network, so that the first blockchain network and the second blockchain network pre-execute the cross-chain private transaction;

2. The method of claim 1, wherein the cross-chain private transaction is a transaction between a first account of a first financial institution and a second account of a second financial institution; the public transaction is a transaction between the first financial institution and the second financial institution;

Wherein the first financial institution interfaces with the first blockchain network and the second financial institution interfaces with the second blockchain network.

3. The method of claim 1, wherein the obtaining the first vote of the first blockchain network and the second vote of the second blockchain network comprises:

obtaining a transaction ID of the cross-chain private transaction, the first vote of the first blockchain network, the second vote of the second blockchain network, and the second vote of the second blockchain network;

the returning a pre-execution hint to the first blockchain network and the second blockchain network such that the first blockchain network and the second blockchain network pre-execute the cross-chain private transaction comprises:

and returning a pre-execution prompt to the first blockchain network and the second blockchain network, wherein the pre-execution prompt carries the transaction ID, so that the first blockchain network obtains corresponding cross-chain private transaction from the local according to the transaction ID carried by the pre-execution prompt and pre-executes the cross-chain private transaction, and the second blockchain network obtains corresponding cross-chain private transaction from the local according to the transaction ID carried by the pre-execution prompt and pre-executes the cross-chain private transaction.

4. The method of claim 3, wherein the obtaining the transaction ID of the first vote of the first blockchain network, the second vote of the second blockchain network, and the cross-chain private transaction comprises:

obtaining a first public chain transaction submitted by the first blockchain network or the second blockchain network, wherein the first public chain transaction carries: a transaction ID of the first vote, the second vote, and the cross-chain private transaction;

the determining, according to the first vote and the second vote, whether the first blockchain network and the second blockchain network both agree to perform the cross-chain private transaction includes:

responding to the first public chain transaction, judging whether the first blockchain network and the second blockchain network agree to execute the cross-chain private transaction according to the first vote and the second vote carried by the first public chain transaction, and writing a judging result and a transaction ID carried by the first public chain transaction into a first block of the public blockchain network;

the returning a pre-execution hint to the first blockchain network and the second blockchain network, the pre-execution hint carrying the transaction ID, comprising:

And returning the first block to the first block chain network and the second block chain network, wherein the judgment result recorded in the first block is used as the pre-execution prompt.

5. The method of any of claims 1 to 4, wherein obtaining the public transaction, the first pre-execution result of the first blockchain network, and the second pre-execution result of the second blockchain network comprises:

obtaining a second public chain transaction submitted by the first blockchain network or the second blockchain network, wherein the second public chain transaction carries: the public transaction, the first pre-execution result, and the second pre-execution result;

the step of judging whether the first blockchain network and the second blockchain network both successfully pre-execute the cross-chain private transaction according to the first pre-execution result and the second pre-execution result comprises the following steps:

responding to the second public chain transaction, and judging whether the first blockchain network and the second blockchain network successfully pre-execute the cross-chain private transaction according to the first pre-execution result and the second pre-execution result carried by the second public chain transaction;

The executing the public transaction and returning the execution result of the public transaction to the first blockchain network and the second blockchain network, including:

and executing the public transaction recorded in the second public chain transaction, writing an execution result into a second block of the public block chain network, and returning the second block to the first block chain network and the second block chain network.

6. A cross-chain private transaction method, applied to a second blockchain network, the method comprising:

receiving a first private chain transaction sent by a first blockchain network, wherein the first private chain transaction carries: a cross-chain private transaction, a public transaction, and a first vote of the first blockchain network, wherein the first vote is used to characterize whether the first blockchain network agrees to perform the cross-chain private transaction;

voting the cross-chain private transaction in response to the first private chain transaction to obtain a second vote, the second vote being used to characterize whether the second blockchain network agrees to perform the cross-chain private transaction;

sending the public transaction, the first vote and the second vote to a public blockchain network, so that the public blockchain network judges whether the first blockchain network and the second blockchain network agree to execute the cross-chain private transaction according to the first vote and the second vote, and returns a pre-execution prompt to the first blockchain network and the second blockchain network under the condition that the first and the second blockchain networks agree to execute the cross-chain private transaction;

Pre-executing the cross-chain private transaction in response to a pre-execution prompt returned by the public blockchain network to obtain a second pre-execution result, and sending the second pre-execution result to the public blockchain network, wherein the cross-chain private transaction is a transaction between a first blockchain network and a second blockchain network;

7. The method of claim 6, wherein the cross-chain private transaction is a transaction between a first account of a first financial institution and a second account of a second financial institution; the public transaction is a transaction between the first financial institution and the second financial institution;

8. The method of claim 6, the sending the public transaction, the first vote, and the second vote to the public blockchain network such that the public blockchain network determines, based on the first vote and the second vote, whether the first blockchain network and the second blockchain network both agree to execute the cross-chain private transaction, and if so, returns a pre-execution hint to the first blockchain network and the second blockchain network, comprising:

transmitting the public transaction, the first vote, the second vote and the transaction ID of the cross-chain private transaction to the public blockchain network, so that the public blockchain network judges whether the first blockchain network and the second blockchain network agree to execute the cross-chain private transaction according to the first vote and the second vote, and returns a pre-execution prompt to the first blockchain network and the second blockchain network under the condition that the first and the second votes agree to execute the cross-chain private transaction, wherein the pre-execution prompt carries the transaction ID;

The pre-executing the cross-chain private transaction in response to a pre-execution hint returned by the public blockchain network, comprising:

responding to a pre-execution prompt returned by the public blockchain network, acquiring corresponding cross-chain private transaction from the local according to the transaction ID carried by the pre-execution prompt, and pre-executing the cross-chain private transaction.

9. A blockchain network, characterized in that it implements the method of any of claims 1 to 5 or implements the method of any of claims 6 to 8 when running.

10. An electronic device belonging to the blockchain network of claim 9, the electronic device being configured to cooperate with other electronic devices in the blockchain network to implement the method of any of claims 1 to 5 or to implement the method of any of claims 6 to 8.