CN114844905A - System and method for cross-block chain interaction - Google Patents
System and method for cross-block chain interaction Download PDFInfo
- Publication number
- CN114844905A CN114844905A CN202210465226.3A CN202210465226A CN114844905A CN 114844905 A CN114844905 A CN 114844905A CN 202210465226 A CN202210465226 A CN 202210465226A CN 114844905 A CN114844905 A CN 114844905A
- Authority
- CN
- China
- Prior art keywords
- routing node
- signature
- network
- cross
- blockchain network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 103
- 230000003993 interaction Effects 0.000 title abstract description 37
- 238000012546 transfer Methods 0.000 claims abstract description 103
- 238000012790 confirmation Methods 0.000 claims abstract description 14
- 238000012795 verification Methods 0.000 claims description 124
- 238000004891 communication Methods 0.000 claims description 48
- 230000006399 behavior Effects 0.000 claims description 14
- 230000005540 biological transmission Effects 0.000 claims description 8
- 238000006243 chemical reaction Methods 0.000 claims description 5
- 230000008569 process Effects 0.000 description 29
- 238000012545 processing Methods 0.000 description 24
- 238000010586 diagram Methods 0.000 description 23
- 238000005516 engineering process Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 12
- 230000007246 mechanism Effects 0.000 description 10
- 230000006872 improvement Effects 0.000 description 9
- 238000004590 computer program Methods 0.000 description 8
- 230000003287 optical effect Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 4
- 238000010168 coupling process Methods 0.000 description 4
- 238000005859 coupling reaction Methods 0.000 description 4
- 238000013524 data verification Methods 0.000 description 4
- 230000003068 static effect Effects 0.000 description 4
- 230000018109 developmental process Effects 0.000 description 3
- 238000010200 validation analysis Methods 0.000 description 3
- 101000652578 Homo sapiens Thyroid transcription factor 1-associated protein 26 Proteins 0.000 description 2
- 102100030344 Thyroid transcription factor 1-associated protein 26 Human genes 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000002955 isolation Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 108010001267 Protein Subunits Proteins 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000007795 chemical reaction product Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 239000004744 fabric Substances 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000003071 parasitic effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 239000000047 product Substances 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 210000003813 thumb Anatomy 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1059—Inter-group management mechanisms, e.g. splitting, merging or interconnection of groups
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present disclosure relates to systems and methods for cross blockchain interaction. The system includes a first blockchain network and an upper blockchain network deployed above the first blockchain network. The system also includes a first transit bridge network deployed below the upper zone blockchain network and a first heterogeneous blockchain network deployed below the first transit bridge network. The first transfer bridge network is isomorphic with the upper zone block chain network and the first zone block chain network. The first heterogeneous block chain network is heterogeneous with the upper block chain network and the first block chain network. Each of a plurality of first transit bridge consensus nodes of the first transit bridge network is configured with simple payment confirmation capabilities to monitor and verify block behavior in the first heterogeneous blockchain network.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of blockchain technology, and more particularly, to a system, method, apparatus, computing device, and storage medium for cross-blockchain interaction.
Background
The Blockchain (Blockchain) is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. Based on the basic characteristics of a blockchain, a blockchain is usually composed of several blocks. The time stamps corresponding to the creation time of the block are recorded in the blocks respectively, and all the blocks form a time-ordered data chain according to the time stamps recorded in the blocks strictly. The real data generated by the physical world can be constructed into a standard transaction (transaction) format supported by a block chain, then is issued to the block chain, the node equipment in the block chain performs consensus processing on the received transaction, and after the consensus is achieved, the node equipment serving as an accounting node in the block chain packs the transaction into a block and performs persistent evidence storage in the block chain. Because the blockchain has the characteristics of decentralization, information non-tampering, autonomy and the like, the blockchain is also paid more and more attention and is applied by people.
With the rapid development of the blockchain technology, the blockchain technology is applied in various fields such as finance, logistics, supply chain, medical treatment, judicial expertise, asset management, and the like. Different blockchain networks may be constructed to handle different types of traffic. In many application scenarios, some complex services need to be implemented by interacting between different blockchain networks.
Disclosure of Invention
It is an object of one or more embodiments of the present disclosure to provide a system, method, apparatus, computing device and storage medium for cross blockchain interaction.
In accordance with an aspect of one or more embodiments of the present disclosure, there is provided a system for cross blockchain interaction, comprising: a first blockchain network comprising a first routing node and a plurality of first consensus nodes in communication with each other; an upper blockchain network of the first blockchain network, the upper blockchain network comprising a first upper routing node trusted by the first blockchain network and in communication with the first routing node; a first transit bridge network deployed at a lower layer of the upper layer blockchain network and including a first transit bridge routing node and a plurality of first transit bridge consensus nodes in communication with each other, the first transit bridge routing node communicating with a second upper layer routing node in the upper layer blockchain network that is trusted by the first transit bridge network, the second upper layer routing node communicating with the first upper layer routing node; and a first heterogeneous blockchain network deployed at a lower level of the first transit bridge network and comprising a plurality of first heterogeneous consensus nodes in communication with the first transit bridge consensus node, wherein the first transit bridge network is homogeneous with the upper blockchain network, the first blockchain network, and the first heterogeneous blockchain network is heterogeneous with the upper blockchain network, the first blockchain network, and wherein each of the plurality of first transit bridge consensus nodes is configured with simple payment confirmation capability to monitor and verify blockchain behavior in the first heterogeneous blockchain network.
In accordance with another aspect of one or more embodiments of the present disclosure, there is provided a method for interacting across blockchains, comprising: obtaining, by a first routing node of a first blockchain network, a cross-chain transaction from the first blockchain network to be executed in a first heterogeneous blockchain network, requesting a plurality of first common identification nodes of the first blockchain network to sign the cross-chain transaction, and transmitting the cross-chain transaction and the received signature of the first common identification node to a first upper routing node of an upper blockchain network of the first blockchain network that is trusted by the first blockchain network when the number of received signatures of the first common identification nodes reaches a preset threshold value, the first heterogeneous blockchain network being disposed at a lower layer of a first transit bridge network that is disposed at a lower layer of the upper blockchain network; verifying whether the signature of the first common identification node received from the first routing node is correct or not through the first upper routing node, and transmitting the cross-chain transaction and the signature of the first upper routing node to a second upper routing node which is trusted by the first transfer bridge network of the upper block chain network when the signature passes the verification; verifying whether the signature of the first upper layer routing node received from the first upper layer routing node is correct or not through the second upper layer routing node, and transmitting the cross-link transaction and the signature of the second upper layer routing node to the first transfer bridge routing node of the first transfer bridge network when the signature passes the verification; and verifying, by the first transit bridge routing node, whether the signature of the second upper routing node received from the second upper routing node is correct, and broadcasting, in the first transit bridge network, the cross-chain transaction received from the second upper routing node such that a plurality of first transit bridge common identification nodes of the first transit bridge network receive and convert the cross-chain transaction into a format adapted to the first heterogeneous blockchain network and transmit the converted cross-chain transaction to the first heterogeneous blockchain network such that a plurality of first heterogeneous common identification nodes of the first heterogeneous blockchain network receive and execute the converted cross-chain transaction, wherein the first transit bridge network is homogeneous with the upper blockchain network, the first blockchain network, and the first heterogeneous blockchain network is heterogeneous with the upper blockchain network, the first blockchain network, and wherein each of the plurality of first transit bridge consensus nodes is configured with simple payment confirmation capabilities to monitor and verify block behavior in the first heterogeneous blockchain network.
In accordance with another aspect of one or more embodiments of the present disclosure, there is provided an apparatus for interacting across a blockchain, comprising: a collection module configured to obtain, by a first routing node of a first blockchain network, a cross-chain transaction from the first blockchain network to be performed in a first heterogeneous blockchain network, request a plurality of first common identification nodes of the first blockchain network to sign the cross-chain transaction, the first heterogeneous blockchain network being deployed at a lower layer of a first transit bridge network, the first transit bridge network being deployed at a lower layer of the upper layer blockchain network; a transmission module configured to transmit, by the first routing node, the cross-chain transaction and the received signature of the first common node to a first upper routing node of an upper layer block chain network of the first block chain network that is trusted by the first block chain network when the number of received signatures of the first common node reaches a preset threshold, verifying by the first upper routing node whether the signature of the first common identification node received from the first routing node is correct, and transmitting the cross-chain transaction and the signature of the first upper routing node to a second upper routing node of the upper blockchain network trusted by the first transit bridge network when the verification passes, verifying by the second upper level routing node whether the signature of the first upper level routing node received from the first upper level routing node is correct, and transmitting the cross-link transaction and the signature of the second upper layer routing node to a first transit bridge routing node of the first transit bridge network when the verification is passed; and an execution module configured to verify, by a first transit bridge routing node, whether a signature of a second upper routing node received from a second upper routing node is correct, and when the verification is passed, broadcast a cross-chain transaction received from the second upper routing node in the first transit bridge network, such that a plurality of first transit bridge consensus nodes of the first transit bridge network receive and convert the cross-chain transaction into a format adapted to a first heterogeneous blockchain network, and transmit the converted cross-chain transaction to the first heterogeneous blockchain network, such that a plurality of first heterogeneous consensus nodes of the first heterogeneous blockchain network receive and execute the converted cross-chain transaction, wherein the first transit bridge network is homogeneous with the upper blockchain network, the first blockchain network, and the first heterogeneous blockchain network is homogeneous with the upper blockchain network, The first blockchain network is heterogeneous and wherein each of the plurality of first transit bridge consensus nodes is configured with simple payment confirmation capabilities to monitor and verify blockchain behavior in the first heterogeneous blockchain network.
In accordance with yet another aspect of one or more embodiments of the present disclosure, there is provided a computing device for cross blockchain interaction, comprising: one or more processors; and a memory storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform a method according to any embodiment of the present disclosure.
According to yet another aspect of one or more embodiments of the present disclosure, there is provided a non-transitory storage medium having stored thereon computer-executable instructions that, when executed by a computer, cause the computer to perform a method according to any one of the embodiments of the present disclosure.
Other features of the present disclosure and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one or more embodiments of the disclosure and together with the description, serve to explain the principles of one or more embodiments of the disclosure.
One or more embodiments of the disclosure may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:
fig. 1 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 2 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 3 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 4 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 5 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 6 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 7 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 8 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 9 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 10 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 11 is a schematic diagram of a system for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
fig. 12 is a flowchart of a method for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
fig. 13 is a schematic block diagram of an apparatus for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure;
FIG. 14 is a schematic block diagram illustrating a computer system on which one or more exemplary embodiments of the present disclosure may be implemented;
fig. 15 is a schematic block diagram of a computing device for interacting across a blockchain in accordance with one or more exemplary embodiments of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. It should be understood, however, that one or more embodiments of the present disclosure may be presented in a number of different ways and are not limited to the embodiments described below. It is also to be understood that one or more embodiments of the present disclosure can be combined in various ways to provide further additional embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
It should be understood that like reference numerals refer to like elements throughout the several views. In the drawings, the size of some of the features may be varied for clarity.
It is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. All terms (including technical and scientific terms) used herein have the meaning commonly understood by one of ordinary skill in the art unless otherwise defined. Well-known functions or constructions may not be described in detail for brevity and/or clarity.
In this document, the term "coupled" is intended to encompass a physical, electrical, and/or communicative coupling of one feature to another, and may or may not have intervening features between the one feature and the other feature. When the connection is a communication connection, even though reference is made to a and B as being "directly connected," it is intended to emphasize that there is no feature or features emphasized by one or more embodiments of the present disclosure between the connection of a and B, but does not represent a limitation that the connection between a and B is not through any element, and those skilled in the art will understand that the connection between a and B may be through a cable, a router, a gateway, a channel, a link, a network, and the like. It should be noted that in the drawings of one or more embodiments of the present disclosure, a direct connection or an indirect connection between a and B is represented by a straight line or other graphic element connected between a and B.
Herein, the term "a or B" includes "a and B" and "a or B" rather than exclusively including only "a" or only "B" unless otherwise specifically stated.
In this document, the term "exemplary" means "serving as an example, instance, or illustration," and not as a "model" that is to be reproduced exactly. Any implementation exemplarily described herein is not necessarily to be construed as preferred or advantageous over other implementations. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the detailed description.
In this document, the term "substantially" is intended to encompass any minor variations due to design or manufacturing imperfections, tolerances of the devices or components, environmental influences and/or other factors. The term "substantially" also allows for differences from a perfect or ideal situation due to parasitics, noise, and other practical considerations that may exist in a practical implementation.
In addition, "first," "second," and like terms may also be used herein for reference purposes only, and thus are not intended to be limiting. For example, the terms "first," "second," and other such numerical terms referring to structures or elements do not imply a sequence or order unless clearly indicated by the context.
It will be further understood that the terms "comprises/comprising," "includes" and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
For ease of understanding, some terms referred to in this disclosure are described below.
Block chain network: a system for commonly maintaining chained data based on blockchain techniques through consensus rules by multiple participants on a distributed network.
Block chain consensus node: the network nodes in the block chain network have a complete copy of the ledger and have the ability to participate in block chain network consensus and ledger maintenance.
The block link is formed by a node: network nodes in a blockchain network, having the ability to communicate across blockchains but not to participate in blockchain network consensus and ledger maintenance, may sometimes be configured to have a complete ledger copy.
Chains of homogeneous blocks (also referred to herein simply as homogeneous chains): the block chains constructed based on the same block chain bottom technology platform have the same security mechanism, consensus algorithm, network topology and block generation verification logic among isomorphic chains, and generally adopt the same set of protocol, request format, verification mode and the like.
Heterogeneous blockchains (also referred to herein simply as heterogeneous chains): the block chains constructed based on different block chain bottom technology platforms have inconsistent security mechanisms, consensus algorithms, network topologies and block generation verification logics among heterogeneous chains, and generally adopt different protocols, request formats, verification modes and the like. For example, bitcoin adopts a workload certification PoW consensus algorithm, while alliance chain Fabric adopts a traditional deterministic consensus algorithm, and the block composition form and the deterministic assurance mechanism of the bitcoin and the traditional deterministic consensus algorithm are very different.
Cross-chain transaction: a transaction of one blockchain requires, during execution, invocation of an intelligent contract (also referred to herein simply as a contract) deployed in another blockchain, or requires as input the contract execution results of another blockchain.
And (3) chain loading and certificate storing: after the common identification confirmation of each common identification node, the common identification node successfully executes the common identification confirmation (i.e. "common identification uplink" or "uplink"), and the execution result can be used for future inquiry. This term may be used interchangeably herein with "common uplink".
With the increasing enlargement of the size of the blockchain, the number of nodes added into the blockchain network is more and more, and the types of the related services are more and more, so that the structure of a single chain is difficult to maintain high performance. In addition, from a business perspective, some loosely coupled services do not necessarily run on the same chain, and some nodes may have a need to implement small-scale transactions and other nodes may not be expected to obtain these small-scale transactions and related data. Thus, different blockchain networks can be constructed to handle different types of traffic. Because of the lack of uniform standards in the current blockchain industry, many organizations have developed their own blockchain platforms, and the blockchain underlying technologies on which blockchain platforms developed by different organizations are based may be different, such that blockchains constructed on different blockchain platforms may be heterogeneous with respect to each other. In many application scenarios, nodes belonging to different blockchain networks may have a need for cross-blockchain (also referred to herein as simply cross-chain) interaction between them to achieve their traffic. When multiple blockchain platforms are required to cooperate together to implement some complex services, there may be a need for cross-heterogeneous chain interaction between nodes of blockchain networks belonging to different blockchain platforms. Because the nodes not only belong to different blockchain networks, but also the adopted security mechanism, consensus algorithm, network topology, block generation verification logic and the like are all inconsistent, cross-chain transactions among the nodes not only have the problem of how to realize mutual trust, but also have the problem of how to verify heterogeneous data.
To this end, the present disclosure provides, in one aspect, a system for cross-blockchain interaction, which constructs a multi-layer blockchain network architecture with high scalability, and is capable of allowing cross-chain interaction between lower blockchain networks heterogeneous to each other through a common upper-layer blockchain network by deploying a homogeneous lower-layer blockchain network and a transit bridge network for accessing the heterogeneous lower-layer blockchain network under the same upper-layer blockchain network. A system 100 for cross blockchain interaction in accordance with various exemplary embodiments of the present disclosure will be described in detail below in conjunction with fig. 1-11.
As shown in fig. 1, the system 100 may include a first blockchain network 1110 and its overlying blockchain network 1100. In other words, the first blockchain network 1110 is deployed at the lower layer of the upper blockchain network 1100, and is the lower blockchain network of the upper blockchain network 1100. Thus, the first blockchain network 1110 and the upper blockchain network 1100 form a two-layer blockchain network architecture. For example, the upper layer blockchain network 1100 may be a relay-chain network that is a primary network of a large-scale blockchain network, while the first blockchain network 1110 may be a sub-network of the relay-chain network. The upper zone blockchain network 1100 may be deployed at the relay layer and the first zone blockchain network 1110 may be deployed at a network layer located below the relay layer. Of course, the upper layer blockchain network 1100 and the first blockchain network 1110 are not limited to the relay chain network and the sub-network thereof, and may be an upper layer blockchain network and a lower layer blockchain network in other two-layer blockchain network architectures. For example, the upper zone blockchain network 1100 may also be deployed at the network layer, while the first blockchain network 1110 may be deployed at a service layer located below the network layer. It is to be appreciated that the upper layer blockchain network 1100 and the first blockchain network 1110 can be deployed in any two adjacent layers of the multi-layer blockchain network architecture, respectively.
The first blockchain network 1110 may include a first routing node BR11 and a plurality of first common nodes X1, X2, X3, X4 in communication with each other. The first consensus nodes X1, X2, X3, and X4 may be used to implement specific services of the first blockchain network 1110, and are responsible for performing verification of transactions and consensus chaining. While the number of first consensus nodes X1, X2, X3, X4 is illustrated as 4, this is merely exemplary and not limiting, and an actual first blockchain network 1110 may include any number of consensus nodes. The first routing node BR11 may be used to communicate with a first upper routing node BR1 in the upper blockchain network 1100 that is trusted by the first blockchain network 1110, responsible for sending and receiving cross-chain messages.
The upper blockchain network 1100 may include a first upper routing node BR1 that is trusted by the first blockchain network 1110 and that communicates with a first routing node BR 11. An upper routing node (e.g., BR1) of upper blockchain network 1100 is a bridge that upper blockchain network 1100 communicates with its lower blockchain network, and may be responsible for forwarding inter-chain requests between lower blockchain networks and responding to requests by lower blockchain networks to upper blockchain network 1100. In addition, the upper layer blockchain network 1100 may also have its own common node to implement its own specific service.
As further shown in fig. 1, the system 100 may also include a first transit bridge network 1120 and a first heterogeneous blockchain network 1121. The first transit bridge network 1120 may be deployed at a lower level of the upper blockchain network 1100, i.e., at the same level as the first blockchain network 1110. The first transit bridge network 1120 may include a first transit bridge routing node BR21 and a plurality of first transit bridge consensus nodes I1, I2, I3, I4 in communication with each other. The first transit bridge routing node BR21 may communicate with a second upper layer routing node BR2 in the upper layer blockchain network 1100 that is trusted by the first transit bridge network 1120. The second upper level routing node BR2 may be in communication with the first upper level routing node BR 1. This can be achieved through a communication network dedicated to the block chain, or through other communication networks such as the internet. The first transit bridge 1120 is homogeneous with the upper blockchain 1100 and the first blockchain 1110. In some embodiments, the first transit bridge network 1120 may be a blockchain network. In some embodiments, the first transit bridge network 1120 may not form a blockchain network, but merely perform signature voting. Herein, for simplicity of description, a block chain or a block chain network that is homogeneous with the upper block chain network 1100 may be described as a homogeneous chain or a homogeneous chain network, and a block chain or a block chain network that is heterogeneous with the upper block chain network 1100 may be described as a heterogeneous chain or a heterogeneous chain network. Thus, the first handover bridge network 1120 and the first blockchain network 1110 may be homogeneous chain networks with respect to the upper blockchain network 1100.
Although the number of the first transfer bridge consensus nodes I1, I2, I3, I4 is illustrated as 4, this is merely exemplary and not limiting. In some examples, different first transit bridge consensus nodes I1, I2, I3, I4 may be provided in the first transit bridge network 1120 by different lower layer blockchain networks of the upper layer blockchain network 1100 that require cross-chain transactions with the first heterogeneous blockchain network 1121, such as first transit bridge consensus node I1 may be provided in the first transit bridge network 1120 by a first blockchain network 1110 and first transit bridge consensus node I2 may be provided in the first transit bridge network 1120 by another lower layer blockchain network of the upper layer blockchain network 1100 that is different from the first blockchain network 1110. This is because different underlying blockchain networks (behind which often, for example, different organizations) may not trust each other, so it is desirable to configure the first transit bridge consensus node in the first transit bridge network 1120 itself.
The first heterogeneous blockchain network 1121 may be deployed below the first transfer bridge network 1120 and includes a plurality of first heterogeneous consensus nodes P1, P2, P3, P4. The first heterogeneous blockchain network 1121 can also be considered a heterogeneous lower-level blockchain network of the upper blockchain network 1100, but is deployed in a layer one level lower than the first blockchain network 1110. The first heterogeneous consensus nodes P1, P2, P3, and P4 may be used to implement specific services of the first heterogeneous blockchain network 1121, which are responsible for performing transaction verification and uplink consensus. Although the number of first heterogeneous consensus nodes P1, P2, P3, P4 is illustrated as 4, this is merely exemplary and not limiting, and an actual first heterogeneous blockchain network 1121 may include any number of consensus nodes. The first heterogeneous blockchain network 1121 is heterogeneous from the upper blockchain network 1100 and the first blockchain network 1110, and thus the first heterogeneous blockchain network 1121 may be a heterogeneous chain network with respect to the upper blockchain network 1100. The plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 are in communication with first transfer bridge consensus nodes I1, I2, I3, I4. It is to be understood that in the drawings, for simplicity of illustration, only the first heterogeneous consensus node P1 is depicted in communication with the first transit bridge consensus nodes I1, I2, I3, I4, but in practice, although not shown, the other respective first heterogeneous consensus nodes P2, P3, P4 are also in communication with the first transit bridge consensus nodes I1, I2, I3, I4, respectively.
Each of the plurality of first transit bridge consensus nodes I1, I2, I3, I4 of the first transit bridge network 1120 may be configured with Simple Payment Validation (SPV) capabilities to monitor and verify block behavior in the first heterogeneous blockchain network 1121. For ease of understanding, each first transit bridge consensus node may be considered an upper layer routing node of the first heterogeneous blockchain network 1121. When the first heterogeneous blockchain network 1121 needs to initiate a cross-chain transaction, the cross-chain transaction may be packaged into a block, and then the first transit bridge consensus node may collect the blocks in the first heterogeneous blockchain network 1121, verify the blocks in the first heterogeneous blockchain network 1121, and a signature of the first heterogeneous consensus node.
Each of the first blockchain network 1110 and the first transit bridge network 1120 may register with a respective one of the first upper routing node BR1 and the second upper routing node BR2 when accessing the upper blockchain network 1100, and obtain a network identity allocated by the respective one of the first upper routing node BR1 and the second upper routing node BR2 after successful registration. The first heterogeneous blockchain network 1121 may register with the first transit bridge consensus node when accessing the first transit bridge network 1120, and obtain the network identifier allocated by the first transit bridge consensus node after the registration is successful. For example, when accessing the first transit bridge network 1120, the first heterogeneous blockchain network 1121 may submit a registration request to the first transit bridge common node to obtain a network identifier, or alternatively, the first transit bridge network 1120 may provide a network identifier allocated in advance to the first heterogeneous blockchain network 1121, and then the first heterogeneous blockchain network 1121 may perform binding registration using the obtained network identifier. Even if there are multiple first transit bridge common nodes in the first transit bridge network 1120, which causes the first heterogeneous blockchain network 1121 to perform multiple registrations, this does not cause a problem because it does not cause the first heterogeneous blockchain network 1121 to be unable to be addressed because at most, multiple network identities correspond to the first heterogeneous blockchain network 1121.
As a non-limiting example, four bytes may be used to represent the network identifier, where the first byte may represent the identifier of the uppermost (first layer) blockchain network (e.g., a relay chain network) node, and the subsequent bytes may represent the identifier of the lower layer network node (e.g., the second byte represents the identifier of the second layer network node, the third byte represents the identifier of the third layer network node, and the fourth byte represents the identifier of the fourth layer network node), and this way of identifying ensures the scalability of the network. Assuming that the identity of the BR1 is 81 and the identity of the BR2 is 82, the network identity of the first blockchain network 1110 registered in the first upper routing node BR1 may be 81000000, the network identity of the first transit bridge network 1120 registered in the second upper routing node BR2 may be 82000000, and the network identity of the first heterogeneous blockchain network 1121 registered in the first transit bridge consensus node may be 82000100. Assuming that the first blockchain network 1110 corresponds to blockchain X and the first heterogeneous blockchain network corresponds to blockchain P, a blockchain can be represented by means of URI (such as network id/chain id), for example, the URI of blockchain X is identified as 81000000/X and the URI of blockchain P is identified as 82000100/P. If a service is to be published in the upper blockchain network 1100 by the lower blockchain network, a service may also be represented by means of a URI (such as a network id/chain id/service id), for example, the URI of the blockchain X publishing contract C service is identified as 81000000/X/C, the URI of the blockchain P publishing contract D service is identified as 82000100/P/D, and after the service is published, a node registered in any lower blockchain network below the upper blockchain network 1100 (e.g., the first blockchain network 1110, the first heterogeneous blockchain network 1121) may invoke the service by the URI of the service.
The first upper routing node BR1 is provided in the upper blockchain network 1100 by the first blockchain network 1110, and the first routing node BR11 is provided in the first blockchain network 1110 by the first blockchain network 1110, so that the first upper routing node BR1 and the first routing node BR11 can be considered to have a strong trust relationship and will not be bad. The second upper layer routing node BR2 is provided in the upper layer blockchain network 1100 by the first transit bridge network 1120, and the first transit bridge routing node BR21 is provided in the first transit bridge network 1120 by the first transit bridge network 1120, so that the second upper layer routing node BR2 and the first transit bridge routing node BR21 can be considered to have a strong trust relationship and not to be malicious. Since the first blockchain network 1110 trusts the first upper routing node BR1, the first transfer bridge network 1120 trusts the second upper routing node BR2, the first upper routing node BR1 and the second upper routing node BR2 belong to the same blockchain network and trust each other, and the first heterogeneous blockchain network 1121 trusts the first transfer bridge common node of the first transfer bridge network 1120, trust transfer is achieved between the first blockchain network 1110 and the first heterogeneous blockchain network 1121 via the upper blockchain network 1100 and the first transfer bridge network 1120 without requiring the first blockchain network 1110 and the first heterogeneous blockchain network 1121 to directly trust each other. In addition, the first transit bridge common node may query and verify node information and block information in the first heterogeneous blockchain network 1121, and may perform format conversion on the cross-chain message to adapt to the first blockchain network 1110 or the first heterogeneous blockchain network 1121, so that the first blockchain network 1110 and the first heterogeneous blockchain network 1121 may verify each other's cross-chain message through the first transit bridge network 1120. In this way, it is able to promote cross-heterogeneous chain interaction between the first blockchain network 1110 and the first heterogeneous blockchain network 1121, and ensure information isolation between the first blockchain network 1110 and the first heterogeneous blockchain network 1121, so that the other party only needs to know information required for performing the requested cross-chain transaction and does not know other information of the other party.
Continuing next with reference to fig. 1, a cross-chain interaction process from the first blockchain network 1110 to the first heterogeneous blockchain network 1121 is described. As shown in fig. 1, when the first blockchain network 1110 initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network 1121, the first routing node BR11 may be configured to obtain the cross-chain transaction from the first blockchain network 1110 to be performed in the first heterogeneous blockchain network 1121. In some embodiments, the cross-chain transaction may be sent by a first common identification node of the first blockchain network 1110 to the first routing node BR 11. In some embodiments, cross-chain transactions in the first blockchain network 1110 may also be collected by the first routing node BR11 itself. For example, after a cross-chain request is generated in the first blockchain network 1110, the cross-chain request is consensus within the blockchain. After consensus is completed, a cross-chain transaction packaging out block is generated. The first routing node BR11 may then query the tiles for cross-chain transactions by monitoring the tiles. In some embodiments, the first routing node BR11 may also be configured to construct a cross-chain transaction into a particular cross-chain message format for cross-chain interaction.
The first routing node BR11 may be further configured to request the plurality of first consensus nodes X1, X2, X3, X4 of the first blockchain network 1110 to sign the cross-chain transaction, and transmit the cross-chain transaction and the received signature of the first consensus node to the first upper routing node BR1 when the number of received signatures of the first consensus node reaches a preset threshold. The preset threshold is configurable. In this context, the preset threshold may be any quantity related quantity, which may be expressed as a numerical value, or may be expressed as a proportion or percentage, for example. For example, in some embodiments, the first routing node BR11 may be required to transmit the cross-chain transaction and the received signature of the first consensus node to the first upper routing node BR1 after receiving the signatures of all the first consensus nodes X1, X2, X3, X4 in the first blockchain network 1110; in other embodiments, the first routing node BR11 may be required to transmit the cross-chain transaction and the received signature of the first consensus node to the first upper routing node BR1 after receiving the signature of the first consensus node in the first blockchain network 1110 above a predetermined percentage (e.g., more than two-thirds, more than one-half, etc.); in other embodiments, the first routing node BR11 may be required to transmit the cross-chain transaction and the received signature of the first consensus node to the first upper routing node BR1 only after receiving the signature of a predetermined number of or more (e.g., more than two, more than three, more than five, etc.) first consensus nodes in the first blockchain network 1110. The first routing node BR11 may only collect and forward signatures of the first consensus node without verifying whether the signatures are correct or not and without verifying the cross-chain transaction. In the example of fig. 1, the first routing node BR11 received and transmitted the signatures sign (X1, X2, X3, X4) of all the first common nodes X1, X2, X3, X4 to the first upper routing node BR1 together with the cross-chain transaction msg _ req.
The first upper level routing node BR1 may be configured to verify that the signature of the first common node received from the first routing node BR11 is correct and, when the verification is passed, to transmit the cross-chain transaction and the signature of the first upper level routing node BR1 to the second upper level routing node BR 2. A specific trust policy may be configured to determine when a received signature satisfies what conditions the verification passes. For example, the trust policy may require that the received signatures all be correct, or may require that the correct signatures in the received signatures be more than a predetermined percentage (e.g., more than two-thirds, more than one-half, etc.), and is not particularly limited herein. When the first upper layer routing node BR1 verifies the received signature of the first common node, the first upper layer routing node BR1 signs itself. The first upper level routing node BR1 may not need to authenticate the cross-chain transaction itself. Also, the first upper routing node BR1 may not need to transmit the signature of the first consensus node to the second upper routing node BR2, since the second upper routing node BR2 does not have a direct trust relationship with the first blockchain network 1110, and the second upper routing node BR2 does not recognize the first consensus node in the first blockchain network 1110. In the example of fig. 1, the first upper routing node BR1 transmits its own signature sign (BR1) to the second upper routing node BR2 along with the cross-chain transaction msg _ req.
The cross-chain transaction may include a network identification of the first blockchain network 1110 as the sender and a network identification of the first heterogeneous blockchain network 1121 as the receiver. The first upper layer routing node BR1 may be configured to query a first transit bridge network 1120, to which the first heterogeneous blockchain network 1121 is accessed, for a second upper layer routing node BR2 that is trusted in the upper layer blockchain network 1100 according to a network identification of the first heterogeneous blockchain network 1121 included in the cross-chain transaction, and to transmit the cross-chain transaction and a signature of the first upper layer routing node BR1 to the queried second upper layer routing node BR 2. For example, in the aforementioned example, the URI identifier of the contract D service issued by the blockchain P of the first heterogeneous blockchain network 1121 is 82000100/P/D, and assuming that the blockchain X of the first blockchain network 1110 wants to invoke the contract D service, its cross-chain transaction includes the URI identifier 82000100/P/D of the contract D service, then the first upper routing node BR1 may check the network identifier in the URI identifier of the target service, i.e., the contract D service, determine, according to the first node 82 of the network identifier, that the upper routing node trusted by the first transit bridge network 1120 to which the target blockchain network, i.e., the first heterogeneous blockchain network 1121, is the second upper routing node BR2, and then may transmit the cross-chain transaction and the signature of the first upper routing node BR1 to the queried second upper routing node BR 2.
The second upper level routing node BR2 may be configured to verify that the signature of the first upper level routing node BR1 received from the first upper level routing node BR1 is correct and to transmit the cross-chain transaction and the signature of the second upper level routing node BR2 to the first transit bridge routing node BR21 when the verification is passed. Likewise, a particular trust policy may be configured to determine when a received signature satisfies what conditions to verify, and is not particularly limited herein. When the second upper layer routing node BR2 verifies the received signature of the first upper layer routing node BR1, the second upper layer routing node BR2 signs itself. The second upper level routing node BR2 may not need to authenticate the cross-chain transaction itself. Also, the second upper level routing node BR2 may not need to transmit the signature of the first upper level routing node BR1 to the first transit bridge routing node BR21, since there is no direct trust relationship between the first transit bridge routing node BR21 and the first upper level routing node BR1, and the first upper level routing node BR1 is not known by the first transit bridge routing node BR 21. In the example of fig. 1, the second upper routing node BR2 transmits its own signature sign (BR2) to the first transit bridge routing node BR21 along with the cross-chain transaction msg _ req. In addition, the second upper layer routing node BR2 may be further configured to find the first transit bridge routing node BR21 of the first transit bridge network 1120 that is locally registered with itself according to the network identification (e.g., subsequent bytes) of the first heterogeneous blockchain network 1121 included in the cross-chain transaction, and transmit the cross-chain transaction and the signature of the second upper layer routing node BR2 to the found first transit bridge routing node BR21 when the signature of the first upper layer routing node BR1 is verified to pass.
The first transit bridge routing node BR21 may be configured to verify whether the signature of the second upper layer routing node BR2 received from the second upper layer routing node BR2 is correct, and when the verification is passed, broadcast the cross-chain transaction received from the second upper layer routing node BR2 in the first transit bridge network 1120, such that the plurality of first transit bridge consensus nodes I1, I2, I3, I4 of the first transit bridge network 1120 (e.g., without limitation, master nodes therein) receive and convert the cross-chain transaction to have a format that fits the first heterogeneous blockchain network 1121, and transmit the converted cross-chain transaction to the first heterogeneous blockchain network 1121, such that the plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 (e.g., without limitation, master nodes therein) receive and perform the converted cross-chain transaction. Likewise, a particular trust policy may be configured to determine when a received signature satisfies what conditions to verify, and is not particularly limited herein. The first transit bridge routing node BR21 may not need to verify the cross-chain transaction itself. In some embodiments, the plurality of first transit bridge consensus nodes I1, I2, I3, I4 of the first transit bridge network 1120 may be further configured to chain the received cross-chain transaction in the first transit bridge network 1120 for later querying. In addition, the master node in the first plurality of first transfer bridge common identification nodes I1, I2, I3, I4 of the first transfer bridge network 1120 may be determined by a specific common identification mechanism of the first transfer bridge network 1120, and the plurality of first heterogeneous common identification nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 may be determined by a specific common identification mechanism of the first heterogeneous blockchain network 1121. The cross-chain transaction may include a URI identification of a service that the first blockchain network 1110 wants to invoke, and the master node of the first heterogeneous blockchain network 1121 may execute the corresponding service according to the service identification. In the example of fig. 1, the first transit bridge routing node BR21 broadcasts the received cross-chain transaction msg _ req in the first transit bridge network 1120 upon verifying that the signature sign (BR2) of the second upper routing node BR2 passes, such that a master node of the plurality of first transit bridge consensus nodes I1, I2, I3, I4 of the first transit bridge network 1120 receives and converts the cross-chain transaction msg _ req into a format msg _ req ' having an adapted first heterogeneous blockchain network 1121, and transmits the converted cross-chain transaction msg _ req ' to the first heterogeneous blockchain network 1121, such that a master node of the plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 receives and executes the converted cross-chain transaction msg _ req '. Thus, cross-chain transactions requested by the first blockchain network 1110 are performed in the first heterogeneous blockchain network 1121.
In some embodiments, after the cross-chain transaction is performed in the first heterogeneous blockchain network 1121, the results of the performance of the cross-chain transaction (e.g., including, but not limited to, receipt messages) may also be transmitted from the first heterogeneous blockchain network 1121 to the first blockchain network 1110. Referring next to fig. 2, a cross-chain interaction process from the first heterogeneous blockchain network 1121 to the first blockchain network 1110 is described.
As shown in fig. 2, after the converted cross-chain transaction msg _ req 'is executed in the first heterogeneous blockchain network 1121, the plurality of first transfer bridge common nodes I1, I2, I3, I4 (e.g., without limitation, master nodes therein) of the first transfer bridge network 1120 may be configured to obtain and verify an execution result msg _ resp' from the first heterogeneous blockchain network 1121 indicating that the converted cross-chain transaction msg _ req 'is executed, and convert the execution result msg _ resp' into a format msg _ resp with an adaptation upper layer blockchain network 1100 or the first blockchain network 1110 (since the upper layer blockchain network 1100 is identical to the first blockchain network 1110, the adaptation formats thereof are identical). For example, the first transit bridge consensus node may be configured to monitor and validate the tiles in the first heterogeneous blockchain network 1121 to collect the execution result msg _ resp 'in the first heterogeneous blockchain network 1121 with respect to the converted cross-chain transaction msg _ req'.
The first transit bridge routing node BR21 may be configured to obtain a translated execution result msg _ resp'. In some examples, the translated execution result may be sent by a first transit bridge consensus node of the first transit bridge network 1120 to the first transit bridge routing node BR 21. In some examples, the results of the post-conversion execution in the first transit bridge network 1120 may also be collected by the first transit bridge routing node BR21 itself. For example, after the first transit bridge consensus node generates the translated execution result, the translated execution result is consensus within the first transit bridge network 1120. And packaging the blocks after the consensus is completed. The first transit bridge routing node BR21 may then query the execution results in the tile by monitoring the tile. In some embodiments, the first transit bridge routing node BR21 may be further configured to construct the translated execution results into a specific cross-chain message format for cross-chain interaction.
The first transit bridge routing node BR21 may be further configured to request the plurality of first transit bridge consensus nodes I1, I2, I3, I4 of the first transit bridge network 1120 to sign the converted execution result msg _ resp ', and transmit the converted execution result msg _ resp' and the received signature of the first transit bridge consensus node to the second upper routing node BR2 when the number of received signatures of the first transit bridge consensus node reaches a preset threshold. The preset threshold is configurable. For example, in some embodiments, the first transit bridge routing node BR21 may be required to transmit the translated execution result and the received signature of the first transit bridge consensus node to the second upper layer routing node BR2 after receiving the signatures of all the first transit bridge consensus nodes I1, I2, I3, I4 in the first transit bridge network 1120; in other embodiments, the first transit bridge routing node BR21 may also be required to transmit the converted execution result and the received signature of the first transit bridge consensus node to the second upper routing node BR2 after receiving the signature of the first transit bridge consensus node in the first transit bridge network 1120 above a predetermined percentage (e.g., more than two-thirds, more than one-half, etc.); in other embodiments, the first transit bridge routing node BR21 may be required to transmit the converted execution result and the received signature of the first transit bridge common node to the second upper routing node BR2 as long as the signature of a preset number of or more (e.g., more than two, more than three, more than five, etc.) first transit bridge common nodes in the first transit bridge network 1120 is received. The first transit bridge routing node BR21 may only collect and forward signatures of first transit bridge consensus nodes without verifying whether the signatures are correct or not and without verifying the translated execution results. In the example of fig. 2, the first transit bridge routing node BR21 has received the signatures sign (I1, I2, I3, I4) of all the first transit bridge common nodes I1, I2, I3, I4 and transmitted it to the second upper layer routing node BR2 together with the translated execution result msg _ resp.
The second upper level routing node BR2 may be configured to verify whether the signature of the first transit bridge consensus node received from the first transit bridge routing node BR21 is correct, and transmit the converted execution result msg _ resp and the signature sign (BR2) of the second upper level routing node BR2 to the first upper level routing node BR1 when the verification passes. Likewise, a particular trust policy may be configured to determine when a received signature satisfies what conditions to verify, and is not particularly limited herein. When the second upper layer routing node BR2 passes the verification of the received signature of the first transit bridge consensus node, the second upper layer routing node BR2 signs itself. The second upper layer routing node BR2 may not need to validate the converted execution result msg _ resp itself. Also, the second upper layer routing node BR2 may not need to transmit the signature of the first transit bridge consensus node to the first upper layer routing node BR1, since there is no direct trust relationship between the first upper layer routing node BR1 and the first transit bridge network 1120, the first upper layer routing node BR1 does not recognize the first transit bridge consensus node in the first transit bridge network 1120. In some embodiments, the converted execution result msg _ resp may include a network identification of the first heterogeneous blockchain network 1121 as the transmitting side and a network identification of the first blockchain network 1110 as the receiving side, and the second upper layer routing node BR2 may be configured to query the first upper layer routing node BR1, which is trusted by the first blockchain network 1110 in the upper layer blockchain network 1100, according to the network identification of the first blockchain network 1110 included in the converted execution result, and transmit the converted execution result and the signature of the second upper layer routing node BR2 to the queried first upper layer routing node BR 1. For example, in the aforementioned example, the block chain X of the first block chain network 1110 invoked the contract D service, and the block chain P executed the contract D service in response thereto, then the converted execution result may include the URI identification 81000000/X of the block chain X, then the second upper routing node BR2 may check the network identification in the URI identification of the target block chain, i.e., the block chain X, determine from the first byte 81 of the network identification that the upper routing node trusted by the target block chain network, i.e., the first block chain network 1110, is the first upper routing node BR1, and then may transmit the execution result and the signature of the second upper routing node BR2 to the queried first upper routing node BR 1.
The first upper routing node BR1 may be configured to verify whether the signature of the second upper routing node BR2 received from the second upper routing node BR2 is correct, and transmit the converted execution result msg _ resp and the signature sign (BR1) of the first upper routing node BR1 to the first routing node BR11 when the verification passes. Likewise, a particular trust policy may be configured to determine when a received signature satisfies what conditions to verify, and is not particularly limited herein. When the first upper layer routing node BR1 verifies the received signature of the second upper layer routing node BR2, the first upper layer routing node BR1 signs itself. The first upper layer routing node BR1 may not need to validate the converted execution result msg _ resp itself. Also, the first upper level routing node BR1 may not need to transmit the signature of the second upper level routing node BR2 to the first routing node BR11, since there is no direct trust relationship between the first routing node BR11 and the second upper level routing node BR2, and the second upper level routing node BR2 is not known to the first routing node BR 11.
The first routing node BR11 may be configured to verify whether the signature of the first upper layer routing node BR1 received from the first upper layer routing node BR1 is correct, and to broadcast the converted execution result msg _ resp in the first blockchain network 1110 when the verification passes. Likewise, a particular trust policy may be configured to determine when a received signature satisfies what conditions to verify, and is not particularly limited herein. The first routing node BR11 may not need to validate the translated execution result msg _ resp itself. Here, since the first blockchain network 1110 is heterogeneous to the first heterogeneous blockchain network 1121, the plurality of first common nodes X1, X2, X3, X4 of the first blockchain network 1110 do not have any knowledge of the execution result of the cross-chain transaction generated in the first heterogeneous blockchain network 1121. Since the plurality of first common identification nodes X1, X2, X3, X4 of the first blockchain network 1110 verify the signature of the first upper layer routing node BR1 by the first routing node BR11, the first upper layer routing node BR1 verifies the signature of the second upper layer routing node BR2, the second upper layer routing node BR2 verifies the signature of the first transit bridge common identification node, the first transit bridge common identification node verifies the blockchain behavior of the first heterogeneous blockchain network 1121, thereby believing that the cross-chain transaction it initiated was successfully performed in the first heterogeneous blockchain network 1121. Thus, the first blockchain network 1110 does not need to query the first heterogeneous blockchain network 1121. The first blockchain network 1110 may then perform subsequent processing on the received execution result msg _ resp converted by the first transfer bridge network 1120 after trusting it, such as linking it up for chain storage in the first blockchain network 1110, or for subsequent contract operations. The process of the first heterogeneous blockchain network 1121 initiating a cross-chain transaction in the first blockchain network 1110 is similar to the above, and is not described herein again.
In the example of fig. 1, the first blockchain network 1110 is provided with one first routing node BR11, but in some other examples, the first blockchain network 1110 may be provided with a plurality of first routing nodes. For example, the a and B agencies are participating in the blockchain X of the first blockchain network 1110 together, but the a and B agencies, while having some degree of trust with each other, may not have as much trust in each other, and therefore the a and B agencies may each set their own first routing node in the first blockchain network 1110 for communicating with the upper blockchain network 1100. Thus, in some embodiments, the first blockchain network 1110 may comprise a plurality of said first routing nodes, each of which may be in communication with a first upper level routing node BR 1. When the first blockchain network 1110 initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network 1121, each of the first routing nodes may be configured to separately obtain a cross-chain transaction from the first blockchain network 1110 to be performed in the first heterogeneous blockchain network 1121, request the plurality of first common nodes to sign the cross-chain transaction, and transmit the cross-chain transaction and the received signature of the first common node to the first upper routing node BR1 when the number of received signatures of the first common node reaches a preset threshold, and the first upper level routing node BR1 may be configured to verify that the signature of the first consensus node received from each first routing node is correct, and when the number of verified first routing nodes in the plurality of first routing nodes reaches a preset threshold, the cross-chain transaction and the signature of the first upper routing node BR1 are transmitted to a second upper routing node BR 2. Also, the preset threshold is configurable. For example, in some embodiments, the first upper level routing node BR1 may be required to transmit the cross-chain transaction and the signature of the first upper level routing node BR1 to the second upper level routing node BR2 after all first routing nodes have been verified; in other embodiments, the first upper routing node BR1 may be required to transmit the cross-chain transaction and the signature of the first upper routing node BR1 to the second upper routing node BR2 after the first routing node above a predetermined percentage (e.g., more than two-thirds, more than one-half, etc.) is verified; in other embodiments, the first upper level routing node BR1 may be further required to transmit the cross-chain transaction and the signature of the first upper level routing node BR1 to the second upper level routing node BR2 after a predetermined number (e.g., more than two, more than three, more than five, etc.) of first routing nodes are verified. In some embodiments, the first upper level routing node BR1 may be further configured to verify whether the hash values of the cross-chain transactions received from each first routing node are consistent, and to transmit the cross-chain transaction that is passed through the deduplication and the signature of the first upper level routing node BR1 to the second upper level routing node BR2 when the verification passes. In other words, the first upper routing node BR1 may receive the same cross-chain transaction from multiple first routing nodes multiple times in a repeat, but the first upper routing node BR1 may deduplicate the received cross-chain transaction and transmit the deduplicated cross-chain transaction to the second upper routing node BR 2. In some embodiments, the first upper layer routing node BR1 may return a failure message to the first routing node when the first upper layer routing node BR1 verifies that the hash values of the cross-chain transactions received from each first routing node are inconsistent (i.e., the hash verifications fail).
For example, referring to fig. 3, the first blockchain network 1110 is provided with two first routing nodes BR11 and BR 12. Each first routing node BR11, BR12 separately obtains a cross-chain transaction msg _ req from the first blockchain network 1110 to be executed in the first heterogeneous blockchain network 1121, requests the plurality of first common identifying nodes X1, X2, X3, X4 to sign the cross-chain transaction msg _ req, and transmits the cross-chain transaction msg _ req and the received signature sign (X1, X2, X3, X4) of the first common identifying node to the first upper routing node BR1 upon receiving the signatures of all the first common identifying nodes X1, X2, X3, X4. The first upper routing node BR1, after verifying that the sign (X1, X2, X3, X4) received from each of the first routing nodes BR11 and BR12 passes, signs its own signature, and transmits its own signature (BR1) and the deduplicated cross-chain transaction msg _ req to the second upper routing node BR 2. Similarly, if the first transit bridge network 1120 is also provided with a plurality of first transit bridge routing nodes at this time, the second upper layer routing node BR2 may transmit its signature sign (BR2) and the cross-chain transaction msg _ req to each of the first transit bridge routing nodes after verifying that the signature of the first upper layer routing node BR1 is correct.
In the example of fig. 2, the first transit bridge network 1120 is provided with one first transit bridge routing node BR21, but in some other examples, the first transit bridge network 1120 may be provided with a plurality of first transit bridge routing nodes. For example, C and D agencies jointly participate in the first relay-bridging network 1120, but may not trust each other very much, although they trust each other to some extent, and thus may each provide their own first relay-bridging routing node in the first relay-bridging network 1120 for communicating with the upper-level blockchain network 1100. Thus, in some embodiments, the first transit bridge network 1120 may comprise a plurality of said first transit bridge routing nodes, each of which may be in communication with a second upper layer routing node BR 2. After the converted cross-chain transaction msg _ req is executed in the first heterogeneous blockchain network 1121, each first transfer bridge routing node may be configured to separately obtain a converted execution result msg _ resp, request the plurality of first transfer bridge consensus nodes to sign the converted execution result msg _ resp, and transmit the converted execution result msg _ resp and the received signature of the first transfer bridge consensus node to the second upper routing node BR2 when the number of received signatures of the first transfer bridge consensus node reaches a preset threshold, and the second upper routing node BR2 may be configured to verify whether the signature of the first transfer bridge consensus node received from each first transfer bridge routing node is correct, and when the number of verified first transfer bridge routing nodes among the plurality of first transfer bridge routing nodes reaches a preset threshold, the converted execution result msg _ resp and signature sign (BR2) of the second upper layer routing node BR2 are transmitted to the first upper layer routing node BR 1. Also, the preset threshold is configurable. For example, in some embodiments, the second upper level routing node BR2 may be required to transmit the translated execution result msg _ resp and the signature of the second upper level routing node BR2 to the first upper level routing node BR1 after all first transit bridge routing nodes have passed verification; in other embodiments, the second upper layer routing node BR2 may be required to transmit the converted execution result msg _ resp and the signature of the second upper layer routing node BR2 to the first upper layer routing node BR1 after the verification of the first upper layer routing node BR2 is completed; in other embodiments, the second upper layer routing node BR2 may be further required to transmit the converted execution result msg _ resp and the signature of the second upper layer routing node BR2 to the first upper layer routing node BR1 after the first upper layer routing node BR2 passes the verification for more than a preset number (e.g., more than two, more than three, more than five, etc.). In some embodiments, the second upper level routing node BR2 is further configured to verify whether the hash values of the translated execution results received from each first transit bridge routing node are consistent, and to transmit the de-duplicated translated execution results and the signature of the second upper level routing node BR2 to the first upper level routing node BR1 when the verification passes. In other words, the second upper level routing node BR2 may receive the same translated execution results multiple times from multiple first transit bridge routing nodes, but the second upper level routing node BR2 may deduplicate the received translated execution results and transmit the deduplicated translated execution results to the first upper level routing node BR 1. In some embodiments, the second upper layer routing node BR2 may return a failure message to the first transit bridge routing node when the second upper layer routing node BR2 verifies that the hash values of the translated execution results received from each first transit bridge routing node are inconsistent (i.e., the hash verifications fail).
For example, referring to fig. 4, the first transit bridge network 1120 is provided with two first transit bridge routing nodes BR21 and BR 22. Each first transfer bridge routing node BR21, BR22 individually obtains the converted execution result msg _ resp, requests the plurality of first transfer bridge consensus nodes I1, I2, I3, I4 to sign the converted execution result msg _ resp, and transmits the converted execution result msg _ resp and the received signature sign (I1, I2, I3, I4) of the first transfer bridge consensus node to the second upper routing node BR2 when the signatures of all the first transfer bridge consensus nodes I1, I2, I3, I4 are received. The second upper routing node BR2, after verifying that the sign (I1, I2, I3, I4) received from each of the first transit bridge routing nodes BR21, BR22 passes, signs itself, and transmits the signature sign (BR2) itself and the execution result msg _ resp after the deduplicated conversion to the first upper routing node BR 1. Similarly, if the first blockchain network 1110 is also provided with a plurality of first routing nodes at this time, the first upper layer routing node BR1 may transmit its signature sign (BR1) and the converted execution result msg _ resp to each first routing node after verifying that the signature of the second upper layer routing node BR2 is correct.
Additionally, in the example of fig. 1, the first blockchain network 1110 sets a trusted first upper level routing node BR1 in the upper level blockchain network 1100. Considering that a first upper routing node may have a problem of unreliable single point of failure, the problem can be solved by setting a cluster. That is, the first blockchain network 1110 may set a set of trust nodes in the upper blockchain network 1100, and such a set of trust nodes may include a plurality of first upper routing nodes that are trusted by the first blockchain network 1110.
In some embodiments, the upper blockchain network 1100 may include a plurality of said first upper routing nodes trusted by the first blockchain network 1110 and in communication with the first routing node BR 11. When the first blockchain network 1110 initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network 1121, the first routing node BR11 may be configured to transmit the cross-chain transaction and a received signature of the first common node to each of the plurality of first upper routing nodes, each of the first upper routing nodes may be configured to individually verify whether the signature of the first common node received from the first routing node BR11 is correct and transmit the cross-chain transaction and the signature of the first upper routing node to the second upper routing node BR2 when verified, and the second upper routing node BR2 may be configured to verify whether the signature of the first upper routing node received from each of the first upper routing nodes is correct and sign the BR2 of the cross-chain transaction and the signature of the second upper routing node BR2 when the number of verified first upper routing nodes of the plurality of first upper routing nodes reaches a preset threshold value To the first transit bridge routing node BR 21. Also, the preset threshold is configurable, and is not particularly limited herein. In some embodiments, the second upper level routing node BR2 is further configured to verify whether the hash values of the cross-chain transactions received from each first upper level routing node are consistent, and to transmit the cross-chain transactions that have passed through the duplication and the signature of the second upper level routing node BR2 to the first transit bridge routing node BR21 when the verification passes. It is to be appreciated that while the above describes a cross-chain interaction process from the first blockchain network 1110 to the first heterogeneous blockchain network 1121, the cross-chain interaction process from the first heterogeneous blockchain network 1121 to the first blockchain network 1110 is similar, for example the second upper level routing node BR2 may send the translated execution result and the signature of the second upper level routing node BR2 to each first upper level routing node, and verifying the signature of the second upper layer routing node BR2 by each first upper layer routing node individually and transmitting the converted execution result and the signature of the first upper layer routing node to the first routing node BR11 when the verification passes, the first routing node BR11 may verify whether the signature of each first upper layer routing node is correct and broadcast the converted execution result in the first blockchain network 1110 when the number of verified first upper layer routing nodes reaches a preset threshold. Also, the preset threshold is configurable, and is not particularly limited herein.
For example, referring to fig. 5, the upper blockchain network 1100 comprises two first upper routing nodes BR1 and BR1 ' trusted by the first blockchain network 1110 and communicating with the first routing node BR11, the first routing node BR11 transmits the cross-chain transaction msg _ req and the received signature sign of the first common node (X1, X2, X3, X4) to each first upper routing node BR1, BR1 ', each first upper routing node BR1, BR1 ' individually verifies whether the signature of the first common node received from the first routing node BR11 is correct and transmits the cross-chain transaction and the signature of the first upper routing node to the second upper routing node BR2 when verified to pass, and the second upper routing node BR 5 verifies whether the signature of the first upper routing node BR 24, BR1 ' received from each first upper routing node BR 639, BR 6959 ' and the signature of the cross-chain transaction is correct and the signature of the second upper routing node BR 8228 when verified to pass (BR 82 2, BR 6959, BR 8228, BR 6959, and again pass) To the first transit bridge routing node BR 21.
Alternatively, when the upper-layer blockchain network 1100 includes a plurality of first upper-layer routing nodes that are trusted by the first blockchain network 1110 and communicate with the first routing node BR11, it is also possible not to cause each of the first upper-layer routing nodes to individually perform both the authentication and the transceiving of data, but to cause one or more of the first upper-layer routing nodes to perform the transceiving of data and another one or more of the first upper-layer routing nodes to perform the authentication of data. Therefore, the method can prevent the single point failure from being unreliable and can save the computing resources. In particular, in some embodiments, the plurality of first upper level routing nodes trusted by the first blockchain network 1110 and in communication with the first routing node BR11 may include a first upper level routing node and a second first upper level routing node. When the first blockchain network 1110 initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network 1121, the first routing node BR11 may be configured to transmit the cross-link transaction and the received signature of the first common node to a first upper routing node, the second first upper routing node may be configured to receive the cross-link transaction from the first routing node and the received signature of the first common node from the first routing node, verify whether the received signature of the first common node is correct, and transmit the cross-link transaction and the signature of the second first upper routing node to the first upper routing node when the verification passes, and the first upper routing node may be configured to transmit the cross-link transaction and the signature of the second first upper routing node and the signature of the first upper routing node to the second upper routing node. The second upper routing node may be configured to verify whether the signature of the second first upper routing node and the signature of the first upper routing node are correct and transmit the cross-chain transaction and the signature of the second upper routing node to the first transit bridge routing node when the verification passes. It will be appreciated that although a cross-chain interworking procedure from the first heterogeneous blockchain network 1110 to the first heterogeneous blockchain network 1121 is described above, a cross-chain interworking procedure from the first heterogeneous blockchain network 1121 to the first blockchain network 1110 is also similar, for example, the second upper routing node BR2 may transmit the converted execution result and the signature of the second upper routing node BR2 to the first upper routing node and from the first upper routing node to the second first upper routing node, the second first upper routing node verifies the signature of the second upper routing node BR2 and transmits the converted execution result and the signature of the second first upper routing node to the first upper routing node when the verification passes, the first upper routing node transmits the converted execution result and the signature of the second upper routing node and the signature of the first upper routing node BR11, the first routing node BR11 may broadcast the translated execution result in the first blockchain network 1110 upon verifying that the signature of the second first upper layer routing node and the signature of the first upper layer routing node are correct.
For example, referring to fig. 6, the upper level blockchain network 1100 comprises a first upper level routing node BR1 and a second first upper level routing node BR1 'trusted by the first blockchain network 1110 and communicating with the first routing node BR11, the first routing node BR11 transmits the cross-chain transaction msg _ req and the received signature sign of the first common node (X1, X2, X3, X4) to the first upper level routing node BR1, the first upper level routing node BR1 transmits the cross-chain transaction msg _ req and the received signature sign of the first common node (X1, X2, X3, X4) to the second first upper level routing node BR 1', the second first upper level routing node BR1 'receives from the first upper level routing node BR1 the cross-chain transaction msg _ req and the received signature of the first common node BR11, the first upper level routing node BR 3646, X3, X3646' and the received signature of the cross-chain transaction msg _ req (X3884, X4, X3872), x2, X3, X4) is correct and, if the verification is passed, transmits the cross-chain transaction msg _ req and the signature sign (BR1 ') of the second first upper routing node to the first upper routing node BR1, and the first upper routing node BR1 transmits the cross-chain transaction msg _ req and the signature sign (BR 1') of the second first upper routing node and the signature sign (BR1) of the first upper routing node to the second upper routing node BR 2. The second upper routing node may transmit the cross-chain transaction msg _ req and the signature sign (BR2) of the second upper routing node to the first transit bridge routing node BR21 after verifying that the signature sign (BR 1') of the second first upper routing node and the signature sign (BR1) of the first upper routing node are correct.
Although it is described above that only one upper routing node of the first blockchain network 1110 is responsible for data transceiving and another upper routing node is responsible for data verification in the set of trusted nodes deployed in the upper blockchain network 1100, this is merely exemplary and not limiting. For example, the first blockchain network 1110 may also be configured to have a set of trusted nodes deployed in the upper blockchain network 1100 including one or more groups of trusted upper-layer routing nodes, each group including one or more transceiving routing nodes responsible for data transceiving and one or more verification routing nodes responsible for data verification, and data from the first routing node BR11 or the second upper layer routing node BR2 would be transmitted to one or more transceiving routing nodes in each group, the respective transceiving routing nodes in each group will then transmit data to each validating routing node in the group individually for validation, after passing the verification, the respective verification routing nodes in the group transmit data to each transceiving routing node in the group, and then the respective transceiving routing nodes in each group transmit data to the second upper layer routing node BR2 or the first routing node BR 11.
Additionally, in the example of fig. 1, the first transit bridge network 1120 provides a trusted second upper level routing node BR2 in the upper level blockchain network 1100. Considering that a second upper routing node may have a problem of unreliable single point of failure, the problem can be solved by setting a cluster. That is, the first transit bridge network 1120 may set up a set of trust nodes in the upper tier blockchain network 1100, and such set of trust nodes may include a plurality of second upper tier routing nodes that are trusted by the first transit bridge network 1120.
In some embodiments, the upper layer blockchain network 1100 may include a plurality of said second upper layer routing nodes trusted by the first transit bridge network 1120 and in communication with the first transit bridge routing node BR 21. When the first blockchain network 1110 initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network 1121, the first upper routing node BR1 may be configured to transmit the cross-chain transaction and a signature of the first upper routing node BR1 to each of the plurality of second upper routing nodes, each of the second upper routing nodes may be configured to individually verify whether the signature of the first upper routing node BR1 received from the first upper routing node BR1 is correct and transmit the cross-chain transaction and the signature of the second upper routing node to the first transit bridge routing node BR21 when verified, and the first transit bridge routing node BR21 may be configured to verify whether the signature of the second upper routing node received from each of the second upper routing nodes is correct and to set a predetermined threshold in the first transit network when the number of the second upper routing nodes that are verified reaches the predetermined threshold in the plurality of the second upper routing nodes 1120 Broadcasting the received cross-chain transaction such that the plurality of first transfer bridge consensus nodes I1, I2, I3, I4 of the first transfer bridge network 1120 receive and convert the cross-chain transaction to have a format that fits the first heterogeneous blockchain network 1121, and transmitting the converted cross-chain transaction to the first heterogeneous blockchain network 1121 such that the plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 receive and execute the converted cross-chain transaction. Also, the preset threshold is configurable, and is not particularly limited herein. In some embodiments, the first transit bridge routing node BR21 may be further configured to verify whether the hash values of the cross-chain transactions received from each of the second upper routing nodes are consistent, and to broadcast the cross-chain transactions that are subject to the deduplication in the first transit bridge network 1120 when the verification passes. It will be appreciated that although the above describes a cross-chain interworking process from the first blockchain network 1110 to the first heterogeneous blockchain network 1121, the cross-chain interworking process from the first heterogeneous blockchain network 1121 to the first blockchain network 1110 is also similar, for example, the first transit bridge routing node BR21 may transmit the converted execution result and the received signature of the first transit bridge consensus node to each second upper routing node, and each second upper routing node separately verifies whether the signature of the first transit bridge consensus node is correct and transmits the converted execution result and the signature of the second upper routing node to the first upper routing node BR1 when the verification passes, and the first upper routing node BR1 may verify whether the signature of each second upper routing node is correct and transmit the converted execution result and the signature of the first upper routing node BR1 to the first upper routing node BR1 when the number of verified second upper routing nodes reaches a preset threshold Node BR 11. Also, the preset threshold is configurable, and is not particularly limited herein.
For example, referring to fig. 7, the upper layer blockchain network 1100 comprises two second upper layer routing nodes BR2 and BR2 'trusted by the first transit bridge network 1120 and communicating with the first transit bridge routing node BR21, the first upper layer routing node BR1 transmits the cross-chain transaction msg _ req and the signature sign (BR1) of the first upper layer routing node BR1 to each of the second upper layer routing nodes BR2, BR 2', each of the second upper layer routing nodes BR2, BR2 'individually verifies whether the signature sign (BR1) of the first upper layer routing node BR1 received from the first upper layer routing node BR1 is correct and transmits the cross-chain transaction and the signature of the second upper layer routing node to the first transit bridge routing node BR21 when verified to be correct, and the first transit bridge routing node BR21 verifies whether the signature of the second upper layer routing node BR 2' received from each of the second upper layer routing nodes BR 6866, BR21 is correct and signs the BR2 'received at the first upper layer routing node BR2 and signs the first upper layer routing node BR 2' when verified to be correct, The BR2 'broadcasts the cross-chain transaction msg _ req in the first transit bridge network 1120 when the verification is passed, so that the master node in the plurality of first transit bridge consensus nodes I1, I2, I3, I4 of the first transit bridge network 1120 receives and converts the cross-chain transaction msg _ req into a format msg _ req' adapted to the first heterogeneous blockchain network 1121, and transmits the converted cross-chain transaction msg _ req 'to the first heterogeneous blockchain network 1121, so that the master node in the plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 receives and executes the converted cross-chain transaction msg _ req'.
Alternatively, when the upper-layer blockchain network 1100 includes a plurality of second upper-layer routing nodes that are trusted by the first transit bridge network 1120 and communicate with the first transit bridge routing node BR21, it is also possible that, instead of each of the second upper-layer routing nodes individually performing both the authentication and the transceiving of data, one or more of the second upper-layer routing nodes may be caused to perform the transceiving of data and the other one or more second upper-layer routing nodes are caused to perform the authentication of data. Therefore, the method can prevent the single point failure from being unreliable and can save the computing resources. In particular, in some embodiments, the plurality of second upper level routing nodes trusted by the first transit bridge network 1120 and in communication with the first transit bridge routing node BR21 may include a first second upper level routing node and a second upper level routing node. When the first blockchain network 1110 initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network 1121, the first upper routing node BR1 may be configured to transmit the cross-link transaction and the signature of the first upper routing node BR1 to a first second upper routing node, the second upper routing node may be configured to receive the cross-link transaction and the signature of the first upper routing node BR1 from the first upper routing node BR1 from the first upper routing node BR, verify whether the received signature of the first upper routing node BR1 is correct, and transmit the cross-link transaction and the signature of the second upper routing node to the first second upper routing node when the verification is passed, the first second upper routing node may be configured to transmit the cross-link transaction and the signature of the second upper routing node and the signature of the first second upper routing node to a first transit bridge routing node BR 21. The first transit bridge routing node BR21 may be configured to verify that the signature of the second upper level routing node and the signature of the first second upper level routing node are correct and broadcast the received cross-chain transaction in the first transit bridge network 1120 when the verification passes. It is to be appreciated that although a cross-chain interworking process from the first heterogeneous blockchain network 1110 to the first heterogeneous blockchain network 1121 is described above, a cross-chain interworking process from the first heterogeneous blockchain network 1121 to the first blockchain network 1110 is also similar, for example, the first transfer bridge routing node BR21 may transmit the converted execution result and the received signature of the first transfer bridge consensus node to a first second upper routing node and by the first second upper routing node to a second upper routing node, the second upper routing node may verify the signature of the first transfer bridge consensus node and transmit the converted execution result and the signature of the second upper routing node to the first second upper routing node when the verification passes, the first second upper routing node may transmit the converted execution result and the signature of the second upper routing node and the signature of the first second upper routing node to the first upper routing node BR1, the first upper layer routing node BR1 may transmit the converted execution result and the signature of the first upper layer routing node BR1 to the first routing node BR1 upon verifying that the signature of the second upper layer routing node and the signature of the first upper layer routing node are correct, and the first routing node BR11 may broadcast the converted execution result in the first blockchain network 1110 upon verifying that the signature of the first upper layer routing node is correct.
For example, referring to fig. 8, the upper layer blockchain network 1100 includes a first second upper layer routing node BR2 and a second upper layer routing node BR2 'trusted by the first transit bridge network 1120 and in communication with the first transit bridge routing node BR21, the first upper layer routing node BR1 transmits the cross-chain transaction msg _ req and the signature sign (BR1) of the first upper layer routing node BR 84 to the first second upper layer routing node BR2, the first second upper layer routing node BR2 transmits the cross-chain transaction msg _ req and the signature sign (BR 6326) of the first upper layer routing node BR1 to the second upper layer routing node BR 2', the second upper layer routing node BR2 receives from the first second upper layer routing node BR2 the cross-chain transaction msg _ req from the first upper layer routing node BR1 and the signature sign (BR 3527) of the first upper layer routing node BR1, and verifies whether the signature (BR1) of the first upper layer routing node BR 3527 is correctly received from the first upper layer routing node BR2, And transmits the cross-chain transaction msg _ req and the signature sign (BR2 ') of the second upper routing node to the first and second upper routing nodes BR2 when the verification is passed, and the first and second upper routing nodes BR2 transmit the cross-chain transaction msg _ req and the signature sign (BR 2') of the second upper routing node and the signature sign (BR2) of the first and second upper routing nodes to the first transit bridge routing node BR 21. The first transit bridge routing node BR21 may broadcast a cross-chain transaction msg _ req in the first transit bridge network 1120 upon verifying that the signature sign of the second upper routing node (BR2 ') and the signature sign of the first second upper routing node (BR2) are correct, such that a master node of the plurality of first transit bridge consensus nodes I1, I2, I3, I4 of the first transit bridge network 1120 receives and converts the cross-chain transaction msg _ req into a format msg _ req' having an adapted first heterogeneous blockchain network 1121, and transmits the converted cross-chain transaction msg _ req 'to the first heterogeneous blockchain network 1121, such that a master node of the plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 receives and performs the converted cross-chain transaction msg _ req'.
Although it is described above that only one upper routing node of the first transit bridge network 1120 in the set of trusted nodes deployed in the upper blockchain network 1100 is responsible for data transceiving and another upper routing node is responsible for data verification, this is merely exemplary and not limiting. For example, the first transit bridge network 1120 may also be configured to include one or more groups of trusted upper-layer routing nodes deployed in the upper-layer blockchain network 1100, each group including one or more transceiving routing nodes responsible for data transceiving and one or more verification routing nodes responsible for data verification, and data from the first upper routing node BR1 or the first transit bridge routing node BR21 would be transmitted to one or more transceiving routing nodes in each group, the respective transceiving routing nodes in each group will then transmit data to each validating routing node in the group individually for validation, the respective verification routing nodes in the group transmit data to each transceiving routing node in the group after verification is passed, and then the respective transceiving routing nodes in each group transmit data to the first transit bridge routing node BR21 or the first upper layer routing node BR 1.
Although the number of first routing nodes, first upper level routing nodes, second upper level routing nodes, and first transit bridge routing nodes are illustrated as one or two in the examples of fig. 1-8, this is merely exemplary and not limiting, and system 100 may include any suitable number of first routing nodes, first upper level routing nodes, second upper level routing nodes, and first transit bridge routing nodes, and one or more of the foregoing embodiments may be correspondingly combined in any combination to implement various alternative cross-chain interaction processes.
Although the system 100 is illustrated in the examples of fig. 1-8 as including one homogeneous lower-layer blockchain network, i.e., the first blockchain network 1110, under the same upper-layer blockchain network 1100, this is merely exemplary and not limiting, the system 100 is laterally scalable, two or more homogeneous lower-layer blockchain networks may be registered under the same upper-layer blockchain network 1100, and any one of these homogeneous lower-layer blockchain networks may implement cross-chain interaction with the first heterogeneous blockchain network 1121 through a process similar to the aforementioned process. Furthermore, cross-chain interaction between any two of these homogeneous lower layer blockchain networks may also be achieved by a process similar to the previous process.
Although the system 100 is illustrated as a two-layer blockchain network architecture on a branch of the first blockchain network 1110 in the example of fig. 1-8, this is merely exemplary and not limiting. The system 100 is scalable in the vertical direction, and the system 100 may be deployed as a two-layer or more layer blockchain network architecture, for example, the first blockchain network 1110 may be used as an upper layer blockchain network of one or more other blockchain networks, and any lower layer blockchain network of the first blockchain network 1110 may implement cross-chain interaction with the first heterogeneous blockchain 1121 through the aforementioned process. A system 100 having a three-tier blockchain network architecture is illustratively described below in conjunction with fig. 9-10.
In some embodiments, for example as shown in fig. 9, system 100 may also include a first sub-blockchain network 1111. The first blockchain network 1110 is an upper blockchain network of the first blockchain network 1111, in other words, the first blockchain network 1111 is deployed below the first blockchain network 1110 and is a lower blockchain network of the first blockchain network 1110. Thus, the first sub-blockchain network 1111 and the first blockchain network 1110 form a two-layer blockchain network architecture, and the first sub-blockchain network 1111 and the first blockchain network 1110 and the upper blockchain network 1100 form a three-layer blockchain network architecture. The first sub-blockchain network 1111 is homogeneous with the first blockchain network 1110 and the upper blockchain network 1100, and is heterogeneous with the first heterogeneous blockchain network 1121.
The first sub-blockchain network 1111 may include a plurality of first sub-consensus nodes N1, N2, N3, N4 in communication with each other. The first sub-consensus nodes N1, N2, N3, N4 may be used to implement specific services of the first sub-blockchain network 1111, and are responsible for performing verification of transactions and uplink consensus. Although the number of first sub-consensus nodes N1, N2, N3, N4 is illustrated as 4, this is merely exemplary and not limiting, and an actual first sub-blockchain network 1111 may include any number of consensus nodes.
In some embodiments, the first blockchain network 1111 may trust the first routing node BR11 of the first blockchain network 1110, and the plurality of first sub consensus nodes N1, N2, N3, N4 each communicate with the first routing node BR 11. The first blockchain network 1111 may register with the first routing node BR11 when accessing the first blockchain network 1110, and obtain the network identifier allocated by the first routing node BR11 after successful registration. For example, the network id of the first sub-blockchain network 1111 may be 81000100, and the URI id of the corresponding blockchain N of the first sub-blockchain network 1111 may be 81000100/N. If the URI of the service G published by the block chain N in the upper block chain network 1100 is identified as 81000100/N/G, a node registered in any lower block chain network (e.g., the first block chain network 1110, the first heterogeneous block chain network 1121, the first sub-block chain network 1111) below the upper block chain network 1100 can invoke the service through the URI identification of the service.
Since the first sub-blockchain network 1111 trusts the first routing node BR11 of the first blockchain network 1110, a trust transfer is achieved between the first sub-blockchain network 1111 and the first heterogeneous blockchain network 1121 via the first blockchain network 1110, the upper blockchain network 1100 and the first hub bridge network 1120 without requiring the first sub-blockchain network 1111 and the first heterogeneous blockchain network 1121 to trust each other. In this way, it is able to promote cross heterogeneous chain interaction between the first sub-blockchain network 1111 and the first heterogeneous blockchain network 1121, and ensure information isolation between the first sub-blockchain network 1111 and the first heterogeneous blockchain network 1121, so that the other party only needs to know information required for performing the requested cross-chain transaction, but does not know other information of the other party.
Referring next to fig. 9, a cross-chain interaction process from the first sub-blockchain network 1111 to the first heterogeneous blockchain network 1121 is described. It is understood that the cross-chain interaction process from the first heterogeneous blockchain network 1121 to the first subblockchain network 1111 is similar and will not be described herein. In the example of fig. 9, when the first sub-blockchain network 1111 initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network 1121, the first routing node BR11 may be configured to obtain a cross-chain transaction to be performed in the first heterogeneous blockchain network 1121 from the first sub-blockchain network 1111, request and verify a signature of the plurality of first sub-common identification nodes N1, N2, N3, N4 on the cross-chain transaction, and transmit the cross-chain transaction and the signature of the first routing node BR11 to the first upper routing node BR1 when the verification passes (again, a specific trust policy may be configured to determine what condition the received signature satisfies, which is not described herein). The first upper level routing node BR1 may be configured to verify that the signature of the first routing node BR11 received from the first routing node BR11 is correct and to transmit the cross-chain transaction and the signature of the first upper level routing node BR1 to the second upper level routing node BR2 when the verification is passed. The second upper level routing node BR2 may be configured to verify that the signature of the first upper level routing node BR1 received from the first upper level routing node BR1 is correct and to transmit the cross-chain transaction and the signature of the second upper level routing node BR2 to the first transit bridge routing node BR21 when the verification is passed. The first transit bridge routing node BR21 may be configured to verify whether the signature of the second upper layer routing node BR2 received from the second upper layer routing node BR2 is correct, and when the verification is passed, broadcast the cross-chain transaction received from the second upper layer routing node BR2 in the first transit bridge network 1120, such that the plurality of first transit bridge consensus nodes I1, I2, I3, I4 of the first transit bridge network 1120 (e.g., without limitation, master nodes therein) receive and convert the cross-chain transaction to have a format that fits the first heterogeneous blockchain network 1121, and transmit the converted cross-chain transaction to the first heterogeneous blockchain network 1121, such that the plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 (e.g., without limitation, master nodes therein) receive and perform the converted cross-chain transaction. It is to be understood that, similar to the embodiments described above with respect to fig. 3 to 8, the first blockchain network 1110 and the first transit bridge network 1120 may each have one or more upper layer routing nodes that are trusted by themselves in the upper layer blockchain network 1100, and may also each include a plurality of routing nodes, and the cross-chain interaction process between the first blockchain network 1110 and the first heterogeneous blockchain network 1121 may be performed in a similar manner, and will not be described again here.
In some embodiments, for example referring to fig. 10, the first sub-blockchain network 1111 may further comprise a first sub-routing node BR111 in communication with the plurality of first sub-consensus nodes N1, N2, N3, N4, the first sub-blockchain network 1111 trusts the first routing node BR11 of the first blockchain network 1110, and the first sub-routing node BR111 is in communication with the first routing node BR 11. When the first sub-blockchain network 1111 initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network 1121, the first sub-routing node BR111 may be configured to obtain the cross-chain transaction to be performed in the first heterogeneous blockchain network 1121 from the first sub-blockchain network 1111, request the plurality of first sub-consensus nodes N1, N2, N3, N4 to sign the cross-chain transaction, and transmit the cross-chain transaction and the received signature of the first sub-consensus node to the first routing node BR11 when the number of received signatures of the first sub-block chain network 1111 reaches a preset threshold. The first routing node BR11 may be configured to verify whether the signature of the first sub-consensus node received from the first sub-routing node BR111 is correct and to transmit the cross-chain transaction and the first routing node BR11 signature to the first upper routing node BR1 when the verification passes. The first upper level routing node BR1 may be configured to verify that the signature of the first routing node BR11 received from the first routing node BR11 is correct and to transmit the cross-chain transaction and the signature of the first upper level routing node BR1 to the second upper level routing node BR2 when the verification is passed. The second upper level routing node BR2 may be configured to verify that the signature of the first upper level routing node BR1 received from the first upper level routing node BR1 is correct and to transmit the cross-chain transaction and the signature of the second upper level routing node BR2 to the first transit bridge routing node BR21 when the verification is passed. The first transit bridge routing node BR21 may be configured to verify whether the signature of the second upper layer routing node BR2 received from the second upper layer routing node BR2 is correct, and when the verification is passed, broadcast the cross-chain transaction received from the second upper layer routing node BR2 in the first transit bridge network 1120, such that the plurality of first transit bridge consensus nodes I1, I2, I3, I4 of the first transit bridge network 1120 (e.g., without limitation, master nodes therein) receive and convert the cross-chain transaction to have a format that fits the first heterogeneous blockchain network 1121, and transmit the converted cross-chain transaction to the first heterogeneous blockchain network 1121, such that the plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 (e.g., without limitation, master nodes therein) receive and perform the converted cross-chain transaction. It is to be understood that, similar to the embodiments described above with respect to fig. 3 to 8, the first blockchain network 1110 and the first transfer bridge network 1120 may each have one or more upper layer routing nodes that are trusted by themselves in the upper layer blockchain network 1100, and may also each include a plurality of routing nodes, and the first subblockchain network 1111 may also include a plurality of sub-routing nodes, so that the cross-link interaction process between the first subblockchain network 1110 and the first heterogeneous blockchain network 1121 may be performed in a similar manner, and will not be described again here.
It is to be appreciated that while fig. 9-10 illustrate the first blockchain network 1110 as including one lower-tier blockchain network, this is merely exemplary and not limiting, the first blockchain network 1110 can include any number of lower-tier blockchain networks, and any two lower-tier blockchain networks (not necessarily in the same layer, homogeneous or heterogeneous) having a common highest-tier blockchain network (e.g., the highest-tier blockchain network can be an upper-tier blockchain network 1100 in the figures herein) can have cross-chain interaction therebetween as described herein. In addition, when the first sub-area block chain network 1111 includes a sub-routing node, a corresponding lower area block chain network may be further extended. In some embodiments, if the first blockchain network 1110 does not extend the lower layer blockchain network (e.g., without the first blockchain network 1111), it may also not include the corresponding first routing node, but rather have each of the common nodes directly coupled to the corresponding upper layer routing node, similar to fig. 9.
When multiple heterogeneous blockchain networks are to be accessed in the system 100, multiple transit bridge networks may be constructed accordingly. Fig. 11 depicts an example scenario in which two heterogeneous blockchain networks are accessed in system 100. In fig. 11, for simplicity of illustration, the first blockchain network 1110 has been omitted, such that fig. 11 focuses on cross-chain interactions between the first heterogeneous blockchain network 1121 and the second heterogeneous blockchain network 1131. It is to be appreciated that the second heterogeneous blockchain network 1131 can also cross-chain interact with the first blockchain network 1110 or other lower blockchain networks of the upper blockchain network 1100 (not limited to which layer below the upper blockchain network 1100) as described above. Specifically, as shown in fig. 11, the system 100 may further include a second transit bridge network 1130 and a second heterogeneous blockchain network 1131.
The second transit bridge network 1130 may be deployed below the upper-layer blockchain network 1100, i.e., on the same layer as the first blockchain network 1110 and the first transit bridge network 1120. The second transit bridge network 1130 may include a second transit bridge in communication with each other, and a plurality of second transit bridge common nodes J1, J2, J3, J4 by the node BR 31. The second transit bridge routing node BR31 may communicate with a third upper layer routing node BR3 in the upper layer blockchain network 1100 that is trusted by the second transit bridge network 1130. The second transit bridge network 1130 may register with the third upper layer routing node BR3 when accessing the upper layer blockchain network 1100, and obtain the network identifier allocated by the third upper layer routing node BR3 after successful registration. The second transit bridge 1130 and the upper blockchain network 1100, the first blockchain network 1110, and the first transit bridge 1120 are homogeneous. In some embodiments, second transit bridge network 1130 may be a blockchain network. In some embodiments, the second transit bridge network 1130 may not form a blockchain network, but merely perform signature voting.
The second heterogeneous blockchain network 1131 may be deployed at a lower level of the second transit bridge network 1130 and include a plurality of second heterogeneous consensus nodes Q1, Q2, Q3, Q4. The second heterogeneous consensus nodes Q1, Q2, Q3, Q4 may be used to implement specific services of the second heterogeneous blockchain network 1131, and are responsible for transaction verification and uplink consensus. Although the number of second heterogeneous consensus nodes Q1, Q2, Q3, Q4 is illustrated as 4, this is merely exemplary and not limiting, and an actual second heterogeneous blockchain network 1131 may include any number of consensus nodes.
The second heterogeneous blockchain network 1131 is heterogeneous from the upper blockchain network 1100 and the first blockchain network 1110. In some embodiments, the second heterogeneous blockchain network 1131 is heterogeneous from the first heterogeneous blockchain network 1121. In other embodiments, the second heterogeneous blockchain network 1131 and the first heterogeneous blockchain network 1121 may be homogeneous, but in such cases it may be more preferable to have the second heterogeneous blockchain network 1131 and the first heterogeneous blockchain network 1121 interact across homogeneous chains via their common upper blockchain network. Therefore, in the following, the second heterogeneous blockchain network 1131 and the first heterogeneous blockchain network 1121 may be heterogeneous to each other for example. The plurality of second heterogeneous consensus nodes Q1, Q2, Q3, Q4 of the second heterogeneous blockchain network 1131 are in communication with a second transit bridge consensus node J1, J2, J3, J4. It is to be understood that in fig. 11, for simplicity of illustration, only the second heterogeneous consensus node Q1 is depicted in communication with the second transit bridge consensus nodes J1, J2, J3, J4, but in practice, although not shown, the other respective second heterogeneous consensus nodes Q2, Q3, Q4 are likewise in communication with the second transit bridge consensus nodes J1, J2, J3, J4, respectively. Although the number of the second transit bridge consensus nodes J1, J2, J3, J4 is illustrated as 4, this is merely exemplary and not limiting. In some examples, different second transit bridge consensus nodes J1, J2, J3, J4 may be provided in the second transit bridge network 1130 by different lower layer blockchain networks of the upper blockchain network 1100 that require cross-chain transactions with the second heterogeneous blockchain network 1131, such as second transit bridge consensus node J1 may be provided in the second transit bridge network 1130 by the first blockchain network 1110 and second transit bridge consensus node J2 may be provided in the second transit bridge network 1130 by the first heterogeneous blockchain network 1121. This is because different underlying blockchain networks (often behind, for example, different agencies) may not trust each other, so it is desirable to configure the second transit bridge consensus node in the second transit bridge network 1130 itself. The second heterogeneous blockchain network 1131 may submit a registration request to the second transit bridge common node when accessing the second transit bridge network 1130 to obtain a network identifier, or alternatively, the second transit bridge network 1130 provides the network identifier allocated in advance to the second heterogeneous blockchain network 1131, and then the second heterogeneous blockchain network 1131 may perform binding registration using the obtained network identifier. Even if there are multiple second transit bridge common nodes in the second transit bridge network 1130 causing the second heterogeneous blockchain network 1131 to register multiple times, this does not cause a problem because it does not cause the second heterogeneous blockchain network 1131 to be unaddressed because multiple network identities correspond to the second heterogeneous blockchain network 1131 at most.
Each of the plurality of second transit bridge consensus nodes J1, J2, J3, J4 of the second transit bridge network 1130 may be configured with simple payment confirmation (SPV) capabilities to monitor and verify tile behavior in the second heterogeneous blockchain network 1131. For ease of understanding, each second transit-bridge consensus node may be considered an upper-layer routing node of the second heterogeneous blockchain network 1131. When the second heterogeneous blockchain network 1131 needs to initiate a cross-chain transaction, the cross-chain transaction may be packaged into a block, and then the second transit bridge consensus node may collect the blocks in the second heterogeneous blockchain network 1131, verify the blocks in the second heterogeneous blockchain network 1131, and a signature of the second heterogeneous consensus node.
Continuing next with fig. 11, an example cross-chain interaction process from the first heterogeneous blockchain network 1121 to the second heterogeneous blockchain network 1131 is described. In the example of fig. 10, when the first heterogeneous blockchain network 1121 initiates a cross-chain transaction to be performed in the second heterogeneous blockchain network 1131, the plurality of first transfer bridge consensus nodes I1, I2, I3, I4 of the first transfer bridge network 1120 (e.g., without limitation, master nodes therein) are configured to obtain and validate the cross-chain transaction msq _ req' from the first heterogeneous blockchain network 1121 to be performed in the second heterogeneous blockchain network 1131 and convert the cross-chain transaction msq _ req into a format msq _ req with an adapted upper layer blockchain network 1100. The first transit bridge routing node BR21 may be configured to obtain a converted cross-chain transaction msq _ req, request the plurality of first transit bridge consensus nodes I1, I2, I3, I4 to sign the converted cross-chain transaction msq _ req, and transmit the converted cross-chain transaction msq _ req and the received signature of the first transit bridge consensus node to the second upper routing node BR2 when the number of received signatures of the first transit bridge consensus node reaches a preset threshold. The second upper level routing node BR2 may be configured to verify that the signature of the first transit bridge consensus node received from the first transit bridge routing node BR21 is correct, and to transmit the converted cross-link transaction msq _ req and the signature of the second upper level routing node BR2 to the third upper level routing node BR3 when the verification is passed. The third upper routing node BR3 may be configured to verify that the signature of the second upper routing node BR2 received from the second upper routing node BR2 is correct and to transmit the converted cross-link transaction msq _ req and the signature BR3 of the third upper routing node to the second transit bridge routing node BR31 when the verification passes. The second transit bridge may be configured by the node BR31 to verify whether the signature of the third upper routing node BR3 received from the third upper routing node BR3 is correct and, when verified, broadcast the converted cross-link transaction msq _ req received from the third upper routing node BR3 in the second transit bridge network 1130 such that the plurality of second transit bridge consensus nodes J1, J2, J3, J4 of the second transit bridge network 1130 (e.g., without limitation, a master node therein (which may be determined by a specific consensus mechanism of the second transit bridge network 1130)) receive and further convert the converted cross-link transaction msq _ req to a format msq _ req "having an adapted second heterogeneous blockchain network 1131 and transmit a further converted cross-link transaction msq _ req" to the second heterogeneous blockchain network 1131 such that the plurality of second heterogeneous blockchain networks 1131 agree to the second heterogeneous blockchain network 1Q 47 Q2, Q3, Q4 (e.g., without limitation, a master node therein (which may be determined by the specific consensus mechanism of the second blockchain network 1131)) receive and execute a further converted cross-chain transaction msq _ req ". In some embodiments, the second transit bridge network 1130 may be further configured to chain the converted cross-chain transaction msq _ req in the second transit bridge network 1130 for later querying. In some embodiments, after the further converted cross-chain transaction msq _ req "is executed in the second heterogeneous blockchain network 1131, the plurality of second transit bridge consensus nodes J1, J2, J3, J4 (e.g., without limitation, master nodes therein) of the second transit bridge network 1131 may be configured to obtain and validate execution results msq _ resq" from the second heterogeneous blockchain network 1131 indicating that the further converted cross-chain transaction msq _ req "is executed, and convert the execution results msq _ resq" to have a format msq _ resq that fits the upper layer blockchain network 1100. The second transit bridge may be configured by the node BR31 to obtain the converted execution result msq _ resq, request the plurality of second transit bridge consensus nodes J1, J2, J3, J4 to sign the converted execution result msq _ resq, and transmit the converted execution result msq _ resq and the received signature of the second transit bridge consensus node to the third upper routing node BR3 when the number of received signatures of the second transit bridge consensus node reaches a preset threshold. The third upper layer routing node BR3 may be configured to verify whether the signature of the second transit bridge consensus node received from the second transit bridge routing node BR31 is correct and to transmit the translated execution result msq _ resq and the signature of the third upper layer routing node BR3 to the second upper layer routing node BR2 when the verification is passed. The second upper level routing node BR2 may be configured to verify whether the signature of the third upper level routing node BR3 received from the third upper level routing node BR3 is correct and to transmit the translated execution result msq _ resq and the signature of the second upper level routing node BR2 to the first translation bridge routing node BR21 when the verification passes. The first transit bridge routing node BR21 may be configured to verify whether the signature of the second upper layer routing node BR2 received from the second upper layer routing node BR2 is correct, and to broadcast the converted execution result msq _ resq received from the second upper layer routing node BR2 in the first transit bridge network 1120 when the verification is passed, such that the plurality of first transit bridge common nodes I1, I2, I3, I4 (e.g., without limitation, master nodes therein) of the first transit bridge network 1120 receive and further convert the converted execution result msq _ resq to have a format msq _ resq 'adapted to the first heterogeneous blockchain network, and to transmit a further converted execution result msq _ resq' to the first heterogeneous blockchain network 1121.
Here, since the first heterogeneous blockchain network 1121 is heterogeneous to the second heterogeneous blockchain network 1131, the plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 are not aware of the execution result of the cross-chain transaction generated in the second heterogeneous blockchain network 1131. Since the plurality of first heterogeneous consensus nodes P1, P2, P3, P4 of the first heterogeneous blockchain network 1121 verify the signature of the second upper layer routing node BR2 through the first transit bridge consensus node, the second upper layer routing node BR2 verifies the signature of the third upper layer routing node BR3, the third upper layer routing node BR3 verifies the signature of the second transit bridge consensus node, and the second transit bridge consensus node verifies the blockchain behavior of the second heterogeneous blockchain network 1131, it is believed that the cross-chain transaction it initiated was successfully performed in the second heterogeneous blockchain network 1131. Thus, the first heterogeneous blockchain network 1121 need not query the second heterogeneous blockchain network 1131. Then, the first heterogeneous blockchain network 1121 may perform subsequent processing on the received execution result msg _ resp' converted by the first transfer bridge network 1120 after trusting it, for example, to chain up the certificate in the first heterogeneous blockchain network 1121 or to use for a subsequent contract operation. The process of the second heterogeneous blockchain network 1131 initiating the cross-chain transaction in the first heterogeneous blockchain network 1121 is similar to the above, and is not described herein again.
Systems for cross blockchain interaction according to various embodiments of the present disclosure can be easily extended in landscape and portrait and can efficiently implement cross heterogeneous chain interaction in large-scale networks.
Referring to fig. 12, the present disclosure provides in yet another aspect a method 200 for inter-blockchain interaction. The method 200 may include: at step S202, obtaining, by a first routing node of a first blockchain network, a cross-chain transaction from the first blockchain network to be executed in a first heterogeneous blockchain network, requesting a plurality of first common nodes of the first blockchain network to sign the cross-chain transaction, and transmitting the cross-chain transaction and the received signature of the first common node to a first upper routing node of an upper blockchain network of the first blockchain network that is trusted by the first blockchain network when the number of received signatures of the first common node reaches a preset threshold, the first heterogeneous blockchain network being disposed at a lower layer of a first transit bridge network that is disposed at a lower layer of the upper blockchain network; at step S204, verifying, by the first upper layer routing node, whether the signature of the first common node received from the first routing node is correct, and transmitting, when the verification is passed, the cross-chain transaction and the signature of the first upper layer routing node to a second upper layer routing node of the upper layer block chain network that is trusted by the first transit bridge network; at step S206, verifying, by the second upper layer routing node, whether the signature of the first upper layer routing node received from the first upper layer routing node is correct, and transmitting the cross-link transaction and the signature of the second upper layer routing node to the first transit bridge routing node of the first transit bridge network when the verification is passed; and at step S208, verifying, by the first transit bridge routing node, whether the signature of the second upper routing node received from the second upper routing node is correct, and broadcasting, in the first transit bridge network, the cross-link transaction received from the second upper routing node when the verification is passed, so that a plurality of first transit bridge consensus nodes of the first transit bridge network receive and convert the cross-link transaction into a format adapted to the first heterogeneous blockchain network, and transmitting the converted cross-link transaction to the first heterogeneous blockchain network, so that the plurality of first heterogeneous consensus nodes of the first heterogeneous blockchain network receive and execute the converted cross-link transaction. The first transfer bridge network is isomorphic with the upper block chain network and the first block chain network, and the first heterogeneous block chain network is heterogeneous with the upper block chain network and the first block chain network. Each of the plurality of first transit bridge consensus nodes is configured with simple payment confirmation capabilities to monitor and verify block behavior in a first heterogeneous blockchain network. The embodiment of the method 200 is substantially similar to the embodiment of the system for inter-blockchain interaction, and therefore, the detailed description thereof is omitted, and the related points can be referred to the description of the system embodiment.
Referring to fig. 13, the present disclosure provides in yet another aspect an apparatus 300 for interacting across a blockchain. The apparatus 300 may include a collection module 302, a transmission module 304, and an execution module 306. The collection module 302 may be configured to obtain, by a first routing node of a first blockchain network, a cross-chain transaction from the first blockchain network to be performed in a first heterogeneous blockchain network, the first heterogeneous blockchain network being deployed at a lower level of a first transit bridge network deployed at a lower level of the upper-level blockchain network, request a plurality of first common nodes of the first blockchain network to sign the cross-chain transaction. The transmission module 304 may be configured to: transmitting, by the first routing node, the cross-chain transaction and the received signature of the first consensus node to a first upper routing node of an upper blockchain network of the first blockchain network that is trusted by the first blockchain network when the number of received signatures of the first consensus node reaches a preset threshold; verifying whether the signature of the first common identification node received from the first routing node is correct or not through the first upper routing node, and transmitting the cross-chain transaction and the signature of the first upper routing node to a second upper routing node, trusted by the first transit bridge network, of the upper block-chain network when the signature passes the verification; and verifying whether the signature of the first upper layer routing node received from the first upper layer routing node is correct or not through the second upper layer routing node, and transmitting the cross-link transaction and the signature of the second upper layer routing node to the first transfer bridge routing node of the first transfer bridge network when the verification is passed. The execution module 306 may be configured to verify, by the first transit bridge routing node, whether a signature of the second upper routing node received from the second upper routing node is correct, and when the verification is passed, broadcast the cross-link transaction received from the second upper routing node in the first transit bridge network, cause a plurality of first transit bridge consensus nodes of the first transit bridge network to receive and convert the cross-link transaction to have a format that fits the first heterogeneous blockchain network, and transmit the converted cross-link transaction to the first heterogeneous blockchain network, cause the plurality of first heterogeneous consensus nodes of the first heterogeneous blockchain network to receive and execute the converted cross-link transaction. The first transfer bridge network is isomorphic with the upper block chain network and the first block chain network, and the first heterogeneous block chain network is heterogeneous with the upper block chain network and the first block chain network. Wherein each of the plurality of first transit bridge consensus nodes is configured with simple payment confirmation capabilities to monitor and verify block behavior in a first heterogeneous blockchain network. The embodiment of the apparatus 300 is substantially similar to the embodiment of the system and method for inter-blockchain interaction described above, and therefore, the detailed description is omitted here, and reference may be made to the description of the system embodiment and method embodiment section for the relevant points.
Fig. 14 is a schematic block diagram illustrating a computer system 600 upon which one or more exemplary embodiments of the present disclosure may be implemented. Computer system 600 includes a bus 602 or other communication mechanism for communicating information, and a processing device 604 coupled with bus 602 for processing information. Computer system 600 also includes a memory 606, which may be a Random Access Memory (RAM) or other dynamic storage device, coupled to bus 602 for storing instructions to be executed by processing device 604. Memory 606 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processing device 604. Computer system 600 also includes a Read Only Memory (ROM)608 or other static storage device coupled to bus 602 for storing static information and instructions for processing apparatus 604. A storage device 610, such as a magnetic disk or optical disk, is provided and coupled to bus 602 for storing information and instructions. Computer system 600 may be coupled via bus 602 to an output device 612, such as, but not limited to, a display, such as a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD), speakers, etc., for providing output to a user. An input device 614, such as a keyboard, mouse, microphone, or the like, is coupled to bus 602 for communicating information and command selections to processing apparatus 604. Computer system 600 may perform embodiments of the present disclosure. Consistent with certain implementations of the present disclosure, the results are provided by computer system 600 in response to processing device 604 executing one or more sequences of one or more instructions contained in memory 606. Such instructions may be read into memory 606 from another computer-readable medium, such as storage device 610. Execution of the sequences of instructions contained in memory 606 causes processing device 604 to perform the methods described herein. Alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement the teachings. Thus, implementations of the present disclosure are not limited to any specific combination of hardware circuitry and software. In various embodiments, computer system 600 may be connected across a network to one or more other computer systems, such as computer system 600, via network interface 616 to form a networked system. The network may comprise a private network or a public network such as the internet. In a networked system, one or more computer systems may store data and supply data to other computer systems. The term "computer-readable medium" as used herein refers to any medium that participates in providing instructions to processing device 604 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 610. Volatile media includes dynamic memory, such as memory 606. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 602. Common forms of computer-readable media or computer program products include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, Digital Video Disk (DVD), blu-ray disk, any other optical medium, thumb drives, memory cards, a RAM, a PROM, and EPROM, a flash EPROM, any other memory chip or cartridge, or any other tangible medium from which a computer can read. Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processing device 604 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 600 can receive the data on the telephone line and use an infra-red transmitter to convert the data to an infra-red signal. An infrared detector coupled to bus 602 can receive the data carried in the infrared signal and place the data on bus 602. The bus 602 carries the data to the memory 606, and the processing device 604 retrieves instructions from the memory 606 and executes the instructions. Alternatively, the instructions received by memory 606 may be stored on storage device 610 either before or after execution by processing device 604.
According to various embodiments, instructions configured to be executed by a processing device to perform a method are stored on a computer-readable medium. The computer readable medium may be a device that stores digital information. For example, the computer readable medium includes a compact disk read only memory (CD-ROM) for storing software as is known in the art. The computer readable medium is accessed by a processor adapted to execute instructions configured to be executed.
For example, the present disclosure may also provide a computing device that may include one or more processors and a memory storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform a method according to any of the preceding embodiments of the present disclosure. As shown in fig. 15, the computing device 700 may include processor(s) 701 and memory 702 storing computer-executable instructions that, when executed by the processor(s) 701, cause the processor(s) 701 to perform a method according to any of the preceding embodiments of the present disclosure. The processor(s) 701 may be, for example, a Central Processing Unit (CPU) of the computing device 700. Processor(s) 701 may be any type of general-purpose processor, or may be a processor specially designed for interacting across a chain of blocks, such as an application specific integrated circuit ("ASIC"). Memory 702 can include a variety of computer-readable media that can be accessed by processor(s) 701. In various embodiments, memory 702 described herein may include volatile and nonvolatile media, removable and non-removable media. For example, memory 702 may include any combination of the following: random access memory ("RAM"), dynamic RAM ("DRAM"), static RAM ("SRAM"), read-only memory ("ROM"), flash memory, cache memory, and/or any other type of non-transitory computer-readable medium. The memory 702 may be stored to cause the processor 701 to perform a method according to any of the preceding embodiments of the present disclosure when executed by the processor 701.
Additionally, the present disclosure may also provide a non-transitory storage medium having stored thereon computer-executable instructions that, when executed by a computer, cause the computer to perform a method according to any of the preceding embodiments of the present disclosure.
One or more exemplary embodiments of the present disclosure are described above. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a server system. Of course, this application does not exclude that with future developments in computer technology, the computer implementing the functionality of the above described embodiments may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device or a combination of any of these devices.
Although one or more embodiments of the present description provide method operational steps as described in the embodiments or flowcharts, more or fewer operational steps may be included based on conventional or non-inventive approaches. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. 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, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded. For example, if the terms first, second, etc. are used to denote names, they do not denote any particular order.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, when implementing one or more of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, etc. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
As will be appreciated by one skilled in the art, one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description of the specification, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
The above description is merely exemplary of one or more embodiments of the present disclosure and is not intended to limit the scope of one or more embodiments of the present disclosure. Various modifications and alterations to one or more embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of the present specification should be included in the scope of the claims.
Claims (53)
1. A system for interacting across blockchains, comprising:
a first blockchain network comprising a first routing node and a plurality of first consensus nodes in communication with each other;
an upper blockchain network of the first blockchain network, the upper blockchain network comprising a first upper routing node trusted by the first blockchain network and in communication with the first routing node;
a first transit bridge network deployed at a lower level of the upper layer blockchain network and including a first transit bridge routing node and a plurality of first transit bridge consensus nodes in communication with each other, the first transit bridge routing node communicating with a second upper layer routing node in the upper layer blockchain network that is trusted by the first transit bridge network, the second upper layer routing node communicating with the first upper layer routing node; and
a first heterogeneous blockchain network deployed at a lower level of the first transit bridge network and including a plurality of first heterogeneous consensus nodes in communication with the first transit bridge consensus node,
wherein the first transfer bridge network is isomorphic with the upper zone block chain network and the first zone block chain network, and the first heterogeneous zone block chain network is heterogeneous with the upper zone block chain network and the first zone block chain network, and
wherein each of the plurality of first transit bridge consensus nodes is configured with simple payment confirmation capabilities to monitor and verify block behavior in a first heterogeneous blockchain network.
2. The system of claim 1, wherein the first transit bridge network is a blockchain network.
3. The system of claim 1, wherein, when the first blockchain network initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network:
the first routing node is configured to obtain a cross-chain transaction from a first blockchain network to be executed in the first heterogeneous blockchain network, request the plurality of first common identification nodes to sign the cross-chain transaction, and transmit the cross-chain transaction and the received signature of the first common identification node to a first upper routing node when the number of received signatures of the first common identification node reaches a preset threshold;
the first upper routing node is configured to verify whether the signature of the first common identification node received from the first routing node is correct or not, and transmit the cross-link transaction and the signature of the first upper routing node to the second upper routing node when the verification is passed;
the second upper routing node is configured to verify whether the signature of the first upper routing node received from the first upper routing node is correct, and transmit the cross-chain transaction and the signature of the second upper routing node to the first transit bridge routing node when the verification is passed; and
the first transit bridge routing node is configured to verify whether a signature of a second upper routing node received from the second upper routing node is correct, and when the verification passes, broadcast a cross-link transaction received from the second upper routing node in the first transit bridge network, so that the plurality of first transit bridge consensus nodes of the first transit bridge network receive and convert the cross-link transaction into a format adapted to the first heterogeneous blockchain network, and transmit the converted cross-link transaction to the first heterogeneous blockchain network, so that the plurality of first heterogeneous consensus nodes of the first heterogeneous blockchain network receive and execute the converted cross-link transaction.
4. The system of claim 3, wherein the plurality of first transit bridge consensus nodes of the first transit bridge network are further configured to chain credit the received cross-chain transaction in the first transit bridge network.
5. The system of claim 3, wherein after the converted cross-chain transaction is performed in the first heterogeneous blockchain network:
the plurality of first transit bridge consensus nodes of the first transit bridge network are configured to obtain and verify execution results from the first heterogeneous blockchain network indicating that the converted cross-chain transaction is executed, and convert the execution results to have a format that is adapted to the upper layer blockchain network;
the first transfer bridge routing node is configured to obtain a converted execution result, request the plurality of first transfer bridge common identification nodes to sign the converted execution result, and transmit the converted execution result and the received signature of the first transfer bridge common identification node to the second upper layer routing node when the number of the received signatures of the first transfer bridge common identification node reaches a preset threshold;
the second upper routing node is configured to verify whether the signature of the first transfer bridge consensus node received from the first transfer bridge routing node is correct or not, and transmit the converted execution result and the signature of the second upper routing node to the first upper routing node when the verification is passed;
the first upper routing node is configured to verify whether the signature of the second upper routing node received from the second upper routing node is correct, and transmit the converted execution result and the signature of the first upper routing node to the first routing node when the verification is passed; and
the first routing node is configured to verify whether a signature of the first upper routing node received from the first upper routing node is correct, and to broadcast the converted execution result in the first blockchain network when the verification is passed.
6. The system of claim 3, wherein the first blockchain network includes a plurality of the first routing nodes, each of the first routing nodes in communication with a first upper level routing node, and wherein when the first blockchain network initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network:
each of the first routing nodes is configured to individually obtain a cross-chain transaction obtained from a first blockchain network to be performed in the first heterogeneous blockchain network, request the plurality of first common nodes to sign the cross-chain transaction, and transmit the cross-chain transaction and the received signature of the first common node to a first upper routing node when the number of received signatures of the first common node reaches a preset threshold, and
the first upper routing node is configured to verify whether the signature of the first common identification node received from each of the first routing nodes is correct, and transmit the cross-link transaction and the signature of the first upper routing node to a second upper routing node when the number of verified first routing nodes in the plurality of first routing nodes reaches a preset threshold.
7. The system of claim 6, wherein the first upper routing node is further configured to verify whether the hash values of the received cross-chain transactions from each of the first routing nodes are consistent, and to transmit the cross-chain transactions that have passed over duplication and the signature of the first upper routing node to the second upper routing node when the verification passes.
8. The system of claim 5, wherein the first transit bridge network comprises a plurality of the first transit bridge routing nodes, each of the first transit bridge routing nodes in communication with a second upper layer routing node, and wherein, after the converted cross-chain transaction is performed in the first heterogeneous blockchain network:
each of the first transit bridge routing nodes is configured to individually obtain a converted execution result, request the plurality of first transit bridge consensus nodes to sign the converted execution result, and transmit the converted execution result and the received signature of the first transit bridge consensus node to a second upper routing node when the number of received signatures of the first transit bridge consensus node reaches a preset threshold, and
the second upper layer routing node is configured to verify whether the signature of the first transit bridge consensus node received from each of the first transit bridge routing nodes is correct, and transmit the converted execution result and the signature of the second upper layer routing node to the first upper layer routing node when the number of verified first transit bridge routing nodes in the plurality of first transit bridge routing nodes reaches a preset threshold.
9. The system of claim 8, wherein the second upper level routing node is further configured to verify whether the hash values of the translated execution results received from each of the first transit bridge routing nodes are consistent, and to transmit the de-duplicated translated execution results and the signature of the second upper level routing node to the first upper level routing node when the verification passes.
10. The system of claim 3, wherein the upper blockchain network comprises a plurality of the first upper routing nodes that are trusted by the first blockchain network and that communicate with the first routing node.
11. The system of claim 10, wherein when the first blockchain network initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network:
the first routing node is configured to transmit the cross-chain transaction and the received signature of the first consensus node to each of the plurality of the first upper routing nodes;
each first upper routing node is configured to individually verify whether the signature of the first common identification node received from the first routing node is correct, and transmit the cross-chain transaction and the signature of the first upper routing node to the second upper routing node when the verification is passed; and is
The second upper routing node is configured to verify whether the signature of the first upper routing node received from each of the first upper routing nodes is correct, and transmit the cross-chain transaction and the signature of the second upper routing node to the first transit bridge routing node when the number of verified first upper routing nodes in the plurality of first upper routing nodes reaches a preset threshold.
12. The system of claim 11, wherein the second upper routing node is further configured to verify whether the hash values of the cross-chain transactions received from each of the first upper routing nodes are consistent, and to transmit the cross-chain transactions that are passed through the deduplication and the signature of the second upper routing node to the first transit bridge routing node when the verification passes.
13. The system of claim 10, wherein the plurality of first upper level routing nodes comprises a first upper level routing node and a second first upper level routing node, and wherein when the first blockchain network initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network: the first routing node is configured to transmit the cross-link transaction and the received signature of the first common node to the first upper routing node, the second first upper routing node is configured to receive the cross-link transaction from the first routing node and the received signature of the first common node from the first upper routing node, verify whether the received signature of the first common node is correct, and transmit the cross-link transaction and the signature of the second first upper routing node to the first upper routing node when the verification passes, the first upper routing node is configured to transmit the cross-link transaction and the signature of the second first upper routing node and the signature of the first upper routing node to the second upper routing node, and the second upper routing node is configured to verify whether the received signature of the second first upper routing node and the signature of the first upper routing node are correct and transmit the cross-link transaction and the signature of the second upper routing node when the verification passes Is transmitted to the first transit bridge routing node.
14. The system of claim 3, wherein the upper zone blockchain network includes a plurality of the second upper routing nodes that are trusted by the first transit bridge network and that communicate with the first transit bridge routing node.
15. The system of claim 14, wherein when the first blockchain network initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network:
the first upper routing node is configured to transmit a cross-chain transaction and a signature of the first upper routing node to each of the plurality of the second upper routing nodes;
each second upper routing node is configured to individually verify whether the signature of the first upper routing node received from the first upper routing node is correct and transmit the cross-chain transaction and the signature of the second upper routing node to the first transit bridge routing node when the verification is passed; and is
The first transit bridge routing node is configured to verify whether a signature of a second upper routing node received from each of the second upper routing nodes is correct, and broadcast the received cross-link transaction in the first transit bridge network when a number of verified second upper routing nodes in the plurality of second upper routing nodes reaches a preset threshold, such that the plurality of first transit bridge common identification nodes of the first transit bridge network receive and convert the cross-link transaction to have a format that fits the first heterogeneous blockchain network, and transmit the converted cross-link transaction to the first heterogeneous blockchain network, such that the plurality of first heterogeneous common identification nodes of the first heterogeneous blockchain network receive and execute the converted cross-link transaction.
16. The system of claim 15, wherein the first transit bridge routing node is further configured to verify whether the hash values of the cross-chain transactions received from each of the second upper routing nodes are consistent, and to broadcast the cross-chain transactions that are subject to the deduplication in the first transit bridge network when the verification passes.
17. The system of claim 14, wherein the plurality of second upper level routing nodes comprises a first second upper level routing node and a second upper level routing node, and wherein when the first blockchain network initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network: the first upper routing node is configured to transmit the cross-link transaction and the signature of the first upper routing node to a first second upper routing node, the second upper routing node is configured to receive the cross-link transaction and the signature of the first upper routing node from the first second upper routing node, verify whether the received signature of the first upper routing node is correct, and transmit the cross-link transaction and the signature of the second upper routing node to the first second upper routing node when the verification passes, the first second upper routing node is configured to transmit the cross-link transaction and the signature of the second upper routing node and the signature of the first second upper routing node to the first transit bridge routing node, the first transit bridge routing node is configured to verify whether the signature of the second upper routing node and the signature of the first upper routing node received from the first second upper routing node are correct, and broadcasting the received cross-chain transaction in the first transit bridge network when the authentication is passed.
18. The system of claim 1, wherein each of the first blockchain network and the first transit bridge network registers with a respective one of the first upper routing node and the second upper routing node upon accessing the upper blockchain network, and obtains a network identification assigned by the respective one of the first upper routing node and the second upper routing node after successful registration.
19. The system of claim 18, wherein the first heterogeneous blockchain network registers with the first transit bridge consensus node when accessing the first transit bridge network, and obtains the network identification assigned by the first transit bridge consensus node after successful registration.
20. The system of claim 19, wherein the cross-chain transaction includes a network identification of the first blockchain network as the sender and a network identification of the first heterogeneous blockchain network as the receiver, and the first upper routing node is configured to query a second upper routing node trusted by the first transit bridge network accessed by the first heterogeneous blockchain network in the upper blockchain network according to the network identification of the first heterogeneous blockchain network included in the cross-chain transaction, and transmit the cross-chain transaction and a signature of the first upper routing node to the queried second upper routing node.
21. The system of claim 1, further comprising: a first sub-blockchain network that is an underlying blockchain network of the first blockchain network and that includes a plurality of first sub-consensus nodes in communication with each other.
22. The system of claim 21, wherein the first sub-blockchain network trusts a first routing node of the first blockchain network and the plurality of first sub-consensus nodes each communicate with the first routing node, and wherein when the first sub-blockchain network initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network:
the first routing node is configured to obtain a cross-chain transaction from the first sub-blockchain network to be performed in the first heterogeneous blockchain network, request and verify a signature of the plurality of first sub-consensus nodes on the cross-chain transaction, and transmit the cross-chain transaction and the signature of the first routing node to the first upper routing node when the verification passes;
the first upper routing node is configured to verify whether the signature of the first routing node received from the first routing node is correct, and transmit the cross-link transaction and the signature of the first upper routing node to the second upper routing node when the verification is passed;
the second upper routing node is configured to verify whether the signature of the first upper routing node received from the first upper routing node is correct, and transmit the cross-link transaction and the signature of the second upper routing node to the first transit bridge routing node when the verification is passed; and
the first transit bridge routing node is configured to verify whether a signature of a second upper routing node received from the second upper routing node is correct, and when the verification passes, broadcast a cross-link transaction received from the second upper routing node in the first transit bridge network, so that the plurality of first transit bridge consensus nodes of the first transit bridge network receive and convert the cross-link transaction into a format adapted to the first heterogeneous blockchain network, and transmit the converted cross-link transaction to the first heterogeneous blockchain network, so that the plurality of first heterogeneous consensus nodes of the first heterogeneous blockchain network receive and execute the converted cross-link transaction.
23. The system of claim 21, wherein the first sub-blockchain network further comprises a first sub-routing node in communication with the plurality of first sub-consensus nodes, the first sub-blockchain network trusting a first routing node of the first blockchain network and the first sub-routing node is in communication with the first routing node, and wherein when the first sub-blockchain network initiates a cross-chain transaction to be performed in the first heterogeneous blockchain network:
the first sub routing node is configured to obtain a cross-chain transaction from the first sub-blockchain network to be performed in the first heterogeneous blockchain network, request the plurality of first sub consensus nodes to sign the cross-chain transaction, and transmit the cross-chain transaction and the received signature of the first sub consensus node to the first routing node when the number of received signatures of the first sub consensus node reaches a preset threshold;
the first routing node is configured to verify whether the signature of the first sub-consensus node received from the first sub-routing node is correct or not, and transmit the cross-chain transaction and the signature of the first routing node to the first upper routing node when the verification is passed;
the first upper routing node is configured to verify whether the signature of the first routing node received from the first routing node is correct, and transmit the cross-link transaction and the signature of the first upper routing node to the second upper routing node when the verification is passed;
the second upper routing node is configured to verify whether the signature of the first upper routing node received from the first upper routing node is correct, and transmit the cross-link transaction and the signature of the second upper routing node to the first transit bridge routing node when the verification is passed; and
the first transit bridge routing node is configured to verify whether a signature of a second upper routing node received from the second upper routing node is correct, and when the verification passes, broadcast a cross-link transaction received from the second upper routing node in the first transit bridge network, so that the plurality of first transit bridge consensus nodes of the first transit bridge network receive and convert the cross-link transaction into a format adapted to the first heterogeneous blockchain network, and transmit the converted cross-link transaction to the first heterogeneous blockchain network, so that the plurality of first heterogeneous consensus nodes of the first heterogeneous blockchain network receive and execute the converted cross-link transaction.
24. The system of claim 1, further comprising:
a second transit bridge network deployed below the upper block-link network and comprising a plurality of second transit bridge consensus nodes and a second transit bridge routing node in communication with each other, the second transit bridge routing node in communication with a third upper routing node in the upper block-link network that is trusted by the second transit bridge network; and
a second heterogeneous blockchain network deployed at a lower level of the second transit bridge network and including a plurality of second heterogeneous consensus nodes in communication with a second transit bridge consensus node,
wherein the second transit bridge network is homogeneous with the upper zone block chain network, the first zone block chain network and the first transit bridge network, and the second heterogeneous zone block chain network is heterogeneous with the upper zone block chain network, the first zone block chain network and the first heterogeneous zone block chain network,
wherein each of the plurality of second transit bridge consensus nodes is configured with simple payment confirmation capabilities to monitor and verify block behavior in a second heterogeneous blockchain network.
25. The system of claim 24, wherein when the first heterogeneous blockchain network initiates a cross-chain transaction to be performed in the second heterogeneous blockchain network:
the plurality of first transfer bridge consensus nodes of the first transfer bridge network are configured to obtain and validate a cross-chain transaction from the first heterogeneous blockchain network to be performed in the second heterogeneous blockchain network and convert the cross-chain transaction to have a format that is adapted to the upper layer blockchain network;
the first transfer bridge routing node is configured to obtain the converted cross-link transaction, request the plurality of first transfer bridge common identification nodes to sign the converted cross-link transaction, and transmit the converted cross-link transaction and the received signature of the first transfer bridge common identification node to the second upper routing node when the number of the received signatures of the first transfer bridge common identification node reaches a preset threshold value;
the second upper routing node is configured to verify whether the signature of the first transfer bridge consensus node received from the first transfer bridge routing node is correct or not, and transmit the converted cross-link transaction and the signature of the second upper routing node to the third upper routing node when the verification is passed;
the third upper routing node is configured to verify whether the signature of the second upper routing node received from the second upper routing node is correct, and transmit the converted cross-link transaction and the signature of the third upper routing node to the second transit bridge routing node when the verification is passed; and
the second transit bridge is configured by the node to verify whether a signature of a third upper routing node received from the third upper routing node is correct, and to broadcast a converted cross-link transaction received from the third upper routing node in the second transit bridge network when the verification is passed, such that the plurality of second transit bridge consensus nodes of the second transit bridge network receive and further convert the converted cross-link transaction to have a format that is adapted to the second heterogeneous blockchain network, and to transmit the further converted cross-link transaction to the second heterogeneous blockchain network, such that the plurality of second heterogeneous consensus nodes of the second heterogeneous blockchain network receive and perform the further converted cross-link transaction.
26. The system of claim 25, wherein after the further converted cross-chain transaction is performed in the second heterogeneous blockchain network:
the plurality of second transit bridge consensus nodes of the second transit bridge network are configured to obtain and verify execution results from the second heterogeneous blockchain network indicating that a further converted cross-chain transaction is performed, and convert the execution results to have a format that is adapted to the upper blockchain network;
the second transit bridge common node is configured to obtain the converted execution result, request the plurality of second transit bridge common node to sign the converted execution result, and transmit the converted execution result and the received signature of the second transit bridge common node to a third upper layer routing node when the number of the received signatures of the second transit bridge common node reaches a preset threshold;
the third upper routing node is configured to verify whether the signature of the second transit bridge consensus node received from the second transit bridge routing node is correct or not, and transmit the converted execution result and the signature of the third upper routing node to the second upper routing node when the verification is passed;
the second upper routing node is configured to verify whether the signature of the third upper routing node received from the third upper routing node is correct, and transmit the converted execution result and the signature of the second upper routing node to the first conversion bridge routing node when the verification is passed; and
the first transit bridge routing node is configured to verify whether a signature of the second upper layer routing node received from the second upper layer routing node is correct, and to broadcast a converted execution result received from the second upper layer routing node in the first transit bridge network when the verification is passed, so that the plurality of first transit bridge common identification nodes of the first transit bridge network receive and further convert the converted execution result into a format adapted to the first heterogeneous blockchain network, and to transmit the further converted execution result to the first heterogeneous blockchain network.
27. A method for interacting across blockchains, comprising:
obtaining, by a first routing node of a first blockchain network, a cross-chain transaction from the first blockchain network to be executed in a first heterogeneous blockchain network, requesting a plurality of first common identification nodes of the first blockchain network to sign the cross-chain transaction, and transmitting the cross-chain transaction and the received signature of the first common identification node to a first upper routing node of an upper blockchain network of the first blockchain network that is trusted by the first blockchain network when the number of received signatures of the first common identification nodes reaches a preset threshold value, the first heterogeneous blockchain network being disposed at a lower layer of a first transit bridge network that is disposed at a lower layer of the upper blockchain network;
verifying whether the signature of the first common identification node received from the first routing node is correct or not through the first upper routing node, and transmitting the cross-chain transaction and the signature of the first upper routing node to a second upper routing node, trusted by the first transit bridge network, of the upper block-chain network when the signature passes the verification;
verifying whether the signature of the first upper layer routing node received from the first upper layer routing node is correct or not through the second upper layer routing node, and transmitting the cross-link transaction and the signature of the second upper layer routing node to the first transfer bridge routing node of the first transfer bridge network when the signature passes the verification; and
verifying whether a signature of a second upper routing node received from the second upper routing node is correct by the first transit bridge routing node, broadcasting a cross-chain transaction received from the second upper routing node in the first transit bridge network when the signature is passed, so that a plurality of first transit bridge common identification nodes of the first transit bridge network receive and convert the cross-chain transaction into a format adapted to the first heterogeneous blockchain network, and transmitting the converted cross-chain transaction to the first heterogeneous blockchain network, so that a plurality of first heterogeneous common identification nodes of the first heterogeneous blockchain network receive and execute the converted cross-chain transaction,
wherein the first transfer bridge network is isomorphic with the upper zone block chain network and the first zone block chain network, and the first heterogeneous zone block chain network is heterogeneous with the upper zone block chain network and the first zone block chain network, and
wherein each of the plurality of first transit bridge consensus nodes is configured with simple payment confirmation capabilities to monitor and verify block behavior in a first heterogeneous blockchain network.
28. The method of claim 27, wherein the first transit bridge network is a blockchain network.
29. The method of claim 27, further comprising: the received cross-chain transaction is chain-credited in the first transit bridge network by the plurality of first transit bridge consensus nodes of the first transit bridge network.
30. The method of claim 27, further comprising:
obtaining and validating, by the plurality of first transit bridge consensus nodes of a first transit bridge network, execution results from a first heterogeneous blockchain network indicating that a converted cross-chain transaction is executed, and converting the execution results to have a format that is adapted to the upper layer blockchain network;
obtaining a converted execution result through a first transfer bridge routing node, requesting the plurality of first transfer bridge common identification nodes to sign the converted execution result, and transmitting the converted execution result and the received signature of the first transfer bridge common identification node to a second upper layer routing node when the number of the received signatures of the first transfer bridge common identification node reaches a preset threshold value;
verifying whether the signature of the first transfer bridge consensus node received from the first transfer bridge routing node is correct or not through the second upper routing node, and transmitting the converted execution result and the signature of the second upper routing node to the first upper routing node when the verification is passed;
verifying whether the signature of the second upper layer routing node received from the second upper layer routing node is correct or not through the first upper layer routing node, and transmitting the converted execution result and the signature of the first upper layer routing node to the first routing node when the verification is passed; and
verifying whether the signature of the first upper layer routing node received from the first upper layer routing node is correct through the first routing node, and broadcasting the converted execution result in the first block chain network when the verification is passed.
31. The method of claim 27, wherein a first blockchain network includes a plurality of the first routing nodes, each of the first routing nodes in communication with a first upper level routing node, and wherein the method comprises:
obtaining, by each of the first routing nodes, a cross-chain transaction to be performed in a first heterogeneous blockchain network obtained from a first blockchain network separately, requesting the plurality of first common nodes to sign the cross-chain transaction, and transmitting the cross-chain transaction and the received signature of the first common node to a first upper routing node when the number of received signatures of the first common node reaches a preset threshold;
verifying whether the signature of the first common identification node received from each first routing node is correct through the first upper routing node, and transmitting the cross-link transaction and the signature of the first upper routing node to a second upper routing node when the number of the verified first routing nodes in the plurality of first routing nodes reaches a preset threshold value.
32. The method of claim 31, further comprising: verifying whether the hash values of the cross-chain transactions received from each first routing node are consistent or not through the first upper routing node, and transmitting the cross-chain transactions subjected to the past weight and the signature of the first upper routing node to a second upper routing node when the verification is passed.
33. The method of claim 30, wherein a first transit bridge network comprises a plurality of the first transit bridge routing nodes, each of the first transit bridge routing nodes in communication with a second upper level routing node, and wherein the method comprises:
the method comprises the steps that each first transfer bridge routing node independently obtains a converted execution result, requests the plurality of first transfer bridge common identification nodes to sign the converted execution result, and transmits the converted execution result and the received signature of the first transfer bridge common identification node to a second upper layer routing node when the number of the received signatures of the first transfer bridge common identification nodes reaches a preset threshold value;
and verifying whether the signature of the first transfer bridge common identification node received from each first transfer bridge routing node is correct or not through a second upper layer routing node, and transmitting the converted execution result and the signature of the second upper layer routing node to the first upper layer routing node when the number of the verified first transfer bridge routing nodes in the plurality of first transfer bridge routing nodes reaches a preset threshold value.
34. The method of claim 33, further comprising: and verifying whether the hash values of the converted execution results received from each first transfer bridge routing node are consistent or not through a second upper layer routing node, and transmitting the repeated converted execution results and the signature of the second upper layer routing node to the first upper layer routing node when the verification is passed.
35. The method of claim 27, wherein the upper blockchain network includes a plurality of the first upper routing nodes that are trusted by the first blockchain network and that communicate with the first routing node.
36. The method of claim 35, comprising:
transmitting, by a first routing node, a cross-chain transaction and a received signature of a first consensus node to each of the plurality of first upper routing nodes;
separately verifying, by each of the first upper routing nodes, whether the signature of the first common identification node received from the first routing node is correct, and transmitting the cross-chain transaction and the signature of the first upper routing node to a second upper routing node when the verification is passed;
and verifying whether the signature of the first upper layer routing node received from each first upper layer routing node is correct or not through a second upper layer routing node, and transmitting the cross-link transaction and the signature of the second upper layer routing node to the first transfer bridge routing node when the number of the verified first upper layer routing nodes in the plurality of first upper layer routing nodes reaches a preset threshold value.
37. The method of claim 36, further comprising: and verifying whether the hash value of the cross-chain transaction received from each first upper routing node is consistent or not through a second upper routing node, and transmitting the cross-chain transaction subjected to the weight passing and the signature of the second upper routing node to the first transfer bridge routing node when the verification is passed.
38. The method of claim 35, wherein the plurality of first upper routing nodes comprises a first upper routing node and a second first upper routing node, and wherein the method comprises:
transmitting, by the first routing node, the cross-chain transaction and the received signature of the first consensus node to a first upper routing node;
transmitting the cross-chain transaction and the received signature of the first common node to a second first upper routing node through the first upper routing node;
verifying whether the received signature of the first common identification node is correct or not through the second first upper routing node, and transmitting the cross-link transaction and the signature of the second first upper routing node to the first upper routing node when the signature passes the verification;
transmitting, by the first upper routing node, the cross-chain transaction and the signature of the second upper routing node and the signature of the first upper routing node received from the second first upper routing node to the second upper routing node;
and verifying whether the received signature of the second first upper routing node and the signature of the first upper routing node are correct or not by the second upper routing node and transmitting the cross-link transaction and the signature of the second upper routing node to the first transfer bridge routing node when the verification is passed.
39. The method of claim 27 wherein the upper zone blockchain network includes a plurality of the second upper routing nodes that are trusted by the first transit bridge network and that communicate with the first transit bridge routing node.
40. The method of claim 39, comprising:
transmitting, by a first upper routing node, a cross-chain transaction and a signature of the first upper routing node to each of the plurality of second upper routing nodes;
individually verifying, by each said second upper routing node, whether the signature of the first upper routing node received from the first upper routing node is correct and transmitting the cross-chain transaction and the signature of the second upper routing node to the first transit bridge routing node when the verification is passed;
verifying, by the first transit bridge routing node, whether the signature of the second upper routing node received from each of the second upper routing nodes is correct, and broadcasting the received cross-link transaction in the first transit bridge network when the number of verified second upper routing nodes in the plurality of second upper routing nodes reaches a preset threshold value, so that the plurality of first transit bridge common identification nodes of the first transit bridge network receive and convert the cross-link transaction into a format adapted to the first heterogeneous blockchain network, and transmitting the converted cross-link transaction to the first heterogeneous blockchain network, so that the plurality of first heterogeneous common identification nodes of the first heterogeneous blockchain network receive and execute the converted cross-link transaction.
41. The method of claim 40, further comprising: verifying whether the hash values of the cross-chain transactions received from each second upper routing node are consistent through the first transit bridge routing node, and broadcasting the cross-chain transactions subjected to the past duplication in the first transit bridge network when the verification is passed.
42. The method of claim 39, wherein the plurality of second upper routing nodes comprises a first second upper routing node and a second upper routing node, and wherein the method comprises:
transmitting, by the first upper routing node, the cross-chain transaction and the signature of the first upper routing node to a first second upper routing node;
transmitting, by the first second upper routing node, the cross-chain transaction and the signature of the first upper routing node to a second upper routing node;
verifying whether the received signature of the first upper routing node is correct or not through a second upper routing node, and transmitting the cross-link transaction and the signature of the second upper routing node to the first upper routing node when the signature of the first upper routing node is verified to be correct;
transmitting, by the first second upper routing node, the cross-link transaction and the signature of the second upper routing node and the signature of the first second upper routing node to the first transit bridge routing node;
and verifying whether the received signature of the second upper layer routing node and the signature of the first upper layer routing node are correct or not through the first transit bridge routing node, and broadcasting the received cross-link transaction in the first transit bridge network when the verification is passed.
43. The method of claim 27, wherein each of the first blockchain network and the first transit bridge network registers with a respective one of the first upper routing node and the second upper routing node when accessing the upper blockchain network, and obtains a network identification assigned by the respective one of the first upper routing node and the second upper routing node after successful registration.
44. The method of claim 43, wherein the first heterogeneous blockchain network registers with the first transit bridge consensus node when accessing the first transit bridge network, and obtains the network identity assigned by the first transit bridge consensus node after successful registration.
45. The method of claim 44, wherein the cross-chain transaction includes a network identification of a first blockchain network as a sender and a network identification of a first heterogeneous blockchain network as a receiver, and wherein the method comprises: and querying a second upper layer routing node which is trusted by a first transfer bridge network accessed by the first heterogeneous blockchain network in the upper layer blockchain network through the first upper layer routing node according to the network identification of the first heterogeneous blockchain network included in the cross-chain transaction, and transmitting the cross-chain transaction and the signature of the first upper layer routing node to the queried second upper layer routing node.
46. The method of claim 27, wherein the lower layer blockchain network of the first blockchain network comprises a first sub-blockchain network comprising a plurality of first sub-consensus nodes in communication with each other.
47. The method of claim 46, wherein the first blockchain network trusts a first routing node of the first blockchain network and the plurality of first sub-consensus nodes each communicate with the first routing node, and wherein the method comprises:
obtaining, by a first routing node, a cross-chain transaction from a first sub-blockchain network to be performed in a first heterogeneous blockchain network, requesting and verifying a signature of the plurality of first sub-consensus nodes for the cross-chain transaction, and transmitting the cross-chain transaction and the signature of the first routing node to a first upper routing node when the verification passes;
verifying whether the signature of the first routing node received from the first routing node is correct or not through the first upper routing node, and transmitting the cross-link transaction and the signature of the first upper routing node to a second upper routing node when the signature passes the verification;
verifying whether the signature of the first upper routing node received from the first upper routing node is correct or not through the second upper routing node, and transmitting the cross-link transaction and the signature of the second upper routing node to the first transfer bridge routing node when the signature passes the verification; and
verifying whether the signature of the second upper layer routing node received from the second upper layer routing node is correct through the first transfer bridge routing node, broadcasting the cross-chain transaction received from the second upper layer routing node in the first transfer bridge network when the signature is passed, enabling the plurality of first transfer bridge common identification nodes of the first transfer bridge network to receive and convert the cross-chain transaction into a format matched with the first heterogeneous blockchain network, and transmitting the converted cross-chain transaction to the first heterogeneous blockchain network, enabling the plurality of first heterogeneous common identification nodes of the first heterogeneous blockchain network to receive and execute the converted cross-chain transaction.
48. The method of claim 46, wherein the first sub-blockchain network further comprises a first sub-routing node in communication with the plurality of first sub-consensus nodes, the first sub-blockchain network trusting a first routing node of the first blockchain network and the first sub-routing node is in communication with the first routing node, and wherein the method comprises:
obtaining, by a first sub-routing node, a cross-chain transaction to be executed in a first heterogeneous blockchain network from the first sub-blockchain network, requesting the plurality of first sub-consensus nodes to sign the cross-chain transaction, and transmitting the cross-chain transaction and the received signature of the first sub-consensus node to the first routing node when the number of received signatures of the first sub-consensus node reaches a preset threshold;
verifying whether the signature of the first sub common identification node received from the first sub routing node is correct or not through the first routing node, and transmitting the cross-link transaction and the signature of the first routing node to the first upper routing node when the verification is passed;
verifying whether the signature of the first routing node received from the first routing node is correct or not through the first upper routing node, and transmitting the cross-link transaction and the signature of the first upper routing node to a second upper routing node when the signature passes the verification;
verifying whether the signature of the first upper routing node received from the first upper routing node is correct or not through the second upper routing node, and transmitting the cross-link transaction and the signature of the second upper routing node to the first transfer bridge routing node when the signature passes the verification; and
verifying whether the signature of the second upper layer routing node received from the second upper layer routing node is correct through the first transfer bridge routing node, broadcasting the cross-chain transaction received from the second upper layer routing node in the first transfer bridge network when the signature is passed, enabling the plurality of first transfer bridge common identification nodes of the first transfer bridge network to receive and convert the cross-chain transaction into a format matched with the first heterogeneous blockchain network, and transmitting the converted cross-chain transaction to the first heterogeneous blockchain network, enabling the plurality of first heterogeneous common identification nodes of the first heterogeneous blockchain network to receive and execute the converted cross-chain transaction.
49. The method of claim 27, comprising:
obtaining and validating, by the plurality of first transit bridge consensus nodes of a first transit bridge network, a cross-chain transaction from a first heterogeneous blockchain network to be performed in a second heterogeneous blockchain network deployed at a lower level of the second transit bridge network, and converting the cross-chain transaction to have a format that is adapted to the upper layer blockchain network;
the converted cross-link transaction is obtained through the first transfer bridge routing node, the plurality of first transfer bridge common identification nodes are requested to sign the converted cross-link transaction, and the converted cross-link transaction and the received signature of the first transfer bridge common identification node are transmitted to the second upper layer routing node when the number of the received signatures of the first transfer bridge common identification node reaches a preset threshold value;
verifying whether the signature of the first transit bridge consensus node received from the first transit bridge routing node is correct or not through the second upper routing node, and transmitting the converted cross-link transaction and the signature of the second upper routing node to a third upper routing node of the upper block link network, which is trusted by the second transit bridge network, when the signature passes the verification;
verifying whether the signature of the second upper layer routing node received from the second upper layer routing node is correct or not through the third upper layer routing node, and transmitting the converted cross-link transaction and the signature of the third upper layer routing node to a second transit bridge routing node of a second transit bridge network when the signature passes the verification; and
verifying, by the second transit bridge routing node, whether the signature of the third upper routing node received from the third upper routing node is correct, and broadcasting in the second transit bridge network the converted cross-link transaction received from the third upper routing node when the verification is passed, so that a plurality of second transit bridge common identification nodes of the second transit bridge network receive and further convert said converted cross-link transaction into a format adapted to the second heterogeneous blockchain network, and transmit the further converted cross-link transaction to the second heterogeneous blockchain network, so that a plurality of second heterogeneous common identification nodes of the second heterogeneous blockchain network receive and execute the further converted cross-link transaction,
wherein the second transit bridge network is homogeneous with the upper zone block chain network, the first zone block chain network and the first transit bridge network, and the second heterogeneous zone block chain network is heterogeneous with the upper zone block chain network, the first zone block chain network and the first heterogeneous zone block chain network,
wherein each of the plurality of second transit bridge consensus nodes is configured with simple payment confirmation capabilities to monitor and verify block behavior in a second heterogeneous blockchain network.
50. The method of claim 49, further comprising:
obtaining and verifying, by the plurality of second transit bridge consensus nodes of a second transit bridge network, an execution result from a second heterogeneous blockchain network indicating that a further converted cross-chain transaction is executed, and converting the execution result to have a format that is adapted to the upper blockchain network;
the plurality of second transit bridge common identification nodes are requested to sign the converted execution result through the second transit bridge routing node, and the converted execution result and the received signature of the second transit bridge common identification node are transmitted to a third upper layer routing node when the number of the received signatures of the second transit bridge common identification node reaches a preset threshold value;
verifying whether the signature of the second transit bridge consensus node received from the second transit bridge routing node is correct or not through the third upper routing node, and transmitting the converted execution result and the signature of the third upper routing node to the second upper routing node when the signature passes the verification;
verifying whether the signature of the third upper layer routing node received from the third upper layer routing node is correct or not through the second upper layer routing node, and transmitting the converted execution result and the signature of the second upper layer routing node to the first conversion bridge routing node when the verification is passed; and
verifying whether the signature of the second upper layer routing node received from the second upper layer routing node is correct through the first transfer bridge routing node, broadcasting the converted execution result received from the second upper layer routing node in the first transfer bridge network when the signature passes through, enabling the plurality of first transfer bridge common identification nodes of the first transfer bridge network to receive and further convert the converted execution result into a format adapted to the first heterogeneous blockchain network, and transmitting the further converted execution result to the first heterogeneous blockchain network.
51. An apparatus for interacting across a blockchain, comprising:
a collection module configured to obtain, by a first routing node of a first blockchain network, a cross-chain transaction from the first blockchain network to be performed in a first heterogeneous blockchain network, request a plurality of first common identification nodes of the first blockchain network to sign the cross-chain transaction, the first heterogeneous blockchain network being deployed at a lower layer of a first transit bridge network, the first transit bridge network being deployed at a lower layer of the upper layer blockchain network;
a transmission module configured to:
transmitting, by the first routing node, the cross-chain transaction and the received signature of the first consensus node to a first upper routing node of an upper blockchain network of the first blockchain network that is trusted by the first blockchain network when the number of received signatures of the first consensus node reaches a preset threshold;
verifying whether the signature of the first common identification node received from the first routing node is correct or not through the first upper routing node, and transmitting the cross-chain transaction and the signature of the first upper routing node to a second upper routing node which is trusted by the first transfer bridge network of the upper block chain network when the signature passes the verification;
verifying whether the signature of the first upper layer routing node received from the first upper layer routing node is correct or not through the second upper layer routing node, and transmitting the cross-link transaction and the signature of the second upper layer routing node to the first transfer bridge routing node of the first transfer bridge network when the signature passes the verification; and
an execution module configured to verify, by the first transit bridge routing node, whether a signature of the second upper routing node received from the second upper routing node is correct, and to broadcast, in the first transit bridge network, a cross-link transaction received from the second upper routing node when the verification is passed, such that a plurality of first transit bridge consensus nodes of the first transit bridge network receive and convert the cross-link transaction to have a format that fits the first heterogeneous blockchain network, and to transmit the converted cross-link transaction to the first heterogeneous blockchain network, such that the plurality of first heterogeneous consensus nodes of the first heterogeneous blockchain network receive and execute the converted cross-link transaction,
wherein the first transfer bridge network is isomorphic with the upper zone block chain network and the first zone block chain network, and the first heterogeneous zone block chain network is heterogeneous with the upper zone block chain network and the first zone block chain network, and
wherein each of the plurality of first transit bridge consensus nodes is configured with simple payment confirmation capabilities to monitor and verify block behavior in a first heterogeneous blockchain network.
52. A computing device for interacting across blockchains, comprising:
one or more processors; and
memory storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform the method of any one of claims 27 to 50.
53. A non-transitory storage medium having stored thereon computer-executable instructions that, when executed by a computer, cause the computer to perform the method of any of claims 27-50.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210465226.3A CN114844905B (en) | 2022-04-29 | 2022-04-29 | System and method for cross-blockchain interactions |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210465226.3A CN114844905B (en) | 2022-04-29 | 2022-04-29 | System and method for cross-blockchain interactions |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114844905A true CN114844905A (en) | 2022-08-02 |
| CN114844905B CN114844905B (en) | 2024-03-29 |
Family
ID=82567435
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210465226.3A Active CN114844905B (en) | 2022-04-29 | 2022-04-29 | System and method for cross-blockchain interactions |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114844905B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110266655A (en) * | 2019-05-30 | 2019-09-20 | 中国工商银行股份有限公司 | A kind of across chain interconnected method, equipment and system based on block chain |
| WO2019211225A1 (en) * | 2018-05-01 | 2019-11-07 | International Business Machines Corporation | Blockchain implementing cross-chain transactions |
| CN110430235A (en) * | 2019-06-28 | 2019-11-08 | 阿里巴巴集团控股有限公司 | The method and apparatus that message can be certified based on across the chain transmission of processing module |
| CN112488679A (en) * | 2020-12-03 | 2021-03-12 | 陈鹏 | Cross-link contract analysis method of block chain, relay chain and cross-link system |
| CN112615838A (en) * | 2020-12-10 | 2021-04-06 | 浙商银行股份有限公司 | Extensible block chain cross-chain communication method |
| CN112651046A (en) * | 2020-12-30 | 2021-04-13 | 杭州趣链科技有限公司 | Data synchronization method, device and system for cross-chain transaction and terminal equipment |
| WO2021136251A1 (en) * | 2019-12-30 | 2021-07-08 | 北京金山云网络技术有限公司 | Cross-blockchain communication method and apparatus, cross-chain service system and cross-chain transaction system |
| CN114221972A (en) * | 2020-09-03 | 2022-03-22 | 中国电信股份有限公司 | Relay blockchain system and cross-chain transaction method |
-
2022
- 2022-04-29 CN CN202210465226.3A patent/CN114844905B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2019211225A1 (en) * | 2018-05-01 | 2019-11-07 | International Business Machines Corporation | Blockchain implementing cross-chain transactions |
| CN110266655A (en) * | 2019-05-30 | 2019-09-20 | 中国工商银行股份有限公司 | A kind of across chain interconnected method, equipment and system based on block chain |
| CN110430235A (en) * | 2019-06-28 | 2019-11-08 | 阿里巴巴集团控股有限公司 | The method and apparatus that message can be certified based on across the chain transmission of processing module |
| WO2021136251A1 (en) * | 2019-12-30 | 2021-07-08 | 北京金山云网络技术有限公司 | Cross-blockchain communication method and apparatus, cross-chain service system and cross-chain transaction system |
| CN114221972A (en) * | 2020-09-03 | 2022-03-22 | 中国电信股份有限公司 | Relay blockchain system and cross-chain transaction method |
| CN112488679A (en) * | 2020-12-03 | 2021-03-12 | 陈鹏 | Cross-link contract analysis method of block chain, relay chain and cross-link system |
| CN112615838A (en) * | 2020-12-10 | 2021-04-06 | 浙商银行股份有限公司 | Extensible block chain cross-chain communication method |
| CN112651046A (en) * | 2020-12-30 | 2021-04-13 | 杭州趣链科技有限公司 | Data synchronization method, device and system for cross-chain transaction and terminal equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114844905B (en) | 2024-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111416808B (en) | Cross-block-chain data mutual storage method, device, equipment and storage medium | |
| CN114793235B (en) | System and method for cross-blockchain interactions | |
| CN111163182B (en) | Block chain-based device registration method and apparatus, electronic device, and storage medium | |
| WO2020258912A1 (en) | Blockchain consensus method, device and system | |
| JP2022500742A (en) | Block processing method, blockchain node, block processing system and computer program | |
| CN114785804B (en) | System and method for cross-blockchain interactions | |
| WO2021073202A1 (en) | Intelligent contract processing method, computer device and storage medium | |
| CN111314172B (en) | Block chain-based data processing method, device, equipment and storage medium | |
| WO2021082340A1 (en) | Data processing method, apparatus, system, and storage medium | |
| CN110866289B (en) | Block chain-based data processing method, device, server and storage medium | |
| JP2024505692A (en) | Data processing methods, devices and computer equipment based on blockchain networks | |
| CN113570479B (en) | Block chain transmission method, system and storage medium for real estate transaction data | |
| CN112714158A (en) | Transaction processing method, relay network, cross-link gateway, system, medium, and device | |
| WO2023160089A1 (en) | Message broadcasting method for blockchain network, and blockchain node and blockchain system | |
| CN115514608A (en) | Block consensus method, device, equipment and storage medium | |
| CN114567643A (en) | Cross-block-chain data transfer method, device and related equipment | |
| CN113409047B (en) | Data processing method, device and equipment based on block chain and readable storage medium | |
| CN114374699A (en) | Cross-chain interaction method and cross-chain interaction auditing method | |
| CN114844904B (en) | System and method for cross-blockchain interactions | |
| CN112887199A (en) | Gateway, cloud platform, configuration method and device thereof, and computer-readable storage medium | |
| CN114844905B (en) | System and method for cross-blockchain interactions | |
| WO2023019903A1 (en) | Cross-chain transaction system and method, and device and storage medium | |
| CN117319412A (en) | Management method of block chain network and related equipment | |
| CN115766038A (en) | Transaction sending method in block chain and block chain link point | |
| CN112037062B (en) | Transaction consensus method, device, electronic equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |