Cross-blockchain transaction method and system supporting cross-blockchain transaction

Through the multi-level cross-chain communication protocol and security verification between the main blockchain system and the sub-blockchain system, the difficulties of cross-chain transactions between different blockchains are solved, and safe and reliable cross-chain transactions are achieved.

CN114255030BActive Publication Date: 2025-09-23CHINA TELECOM CORP LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202011003218.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-09-22
Publication Date
2025-09-23
Estimated Expiration
2040-09-22

AI Technical Summary

Technical Problem

Cross-chain transactions between different blockchains are difficult, leading to the problem of value islands.

Method used

The main blockchain system is used as a relay and connected to the sub-blockchain system through the Multi-level Inter-Blockchain Communication Protocol (MIBCP) to achieve the storage and transmission of cross-blockchain transaction information, and ensure transaction security through certificate and hash verification.

Benefits of technology

It enables cross-chain transactions between different blockchain systems, improves the security and reliability of transactions, and ensures the integrity and non-tamperability of transaction information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114255030B_ABST
    Figure CN114255030B_ABST
Patent Text Reader

Abstract

The present disclosure relates to a method for cross-blockchain transactions and a system supporting cross-blockchain transactions, and relates to the field of computer technology. The method includes: a main blockchain system receiving a cross-blockchain transaction request from a first sub-blockchain system, wherein the cross-blockchain transaction request includes: cross-blockchain transaction information between the first sub-blockchain system and a second sub-blockchain system, and an identifier of the second sub-blockchain system; the main blockchain system generating a block based on the cross-blockchain transaction information and uploading it to the main blockchain for storage; and the main blockchain system forwarding the cross-blockchain transaction request to the second sub-blockchain system based on the identifier of the second sub-blockchain system, so that the second sub-blockchain system executes the transaction based on the cross-blockchain transaction information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method for cross-blockchain transactions and a system supporting cross-blockchain transactions. Background Art

[0002] The development and application of data are changing the world today. Data resources have become data assets. The production, circulation and application of data have made the secure sharing of data an important means to solve the problem of data transforming from resources to assets and maximize the value of data.

[0003] The traditional data sharing model centrally collects, processes, stores, and applies data through a unified data warehouse or big data platform. This model works well within centralized institutions, significantly improving operational efficiency and promoting their digital transformation. However, when data needs to be shared between peer-to-peer organizations, adopting a centralized sharing model can present a series of problems. Blockchain-based data sharing models effectively address many of these issues with data sharing between peer organizations through mechanisms such as distributed ledgers and data ownership verification.

[0004] At present, the application of blockchain technology has gradually been carried out, but different users have built blockchains separately for different services, resulting in the coexistence of multiple types and large numbers of blockchains. Summary of the Invention

[0005] The inventors discovered that a large number of independent blockchains may form "value islands" and that there will be a large number of cross-chain requests between different chains now and in the future.

[0006] A technical problem to be solved by the present disclosure is to propose a cross-blockchain transaction method to realize cross-blockchain transactions between different blockchains.

[0007] According to some embodiments of the present disclosure, a cross-blockchain transaction method is provided, comprising: a main blockchain system receiving a cross-blockchain transaction request sent by a first sub-blockchain system, wherein the cross-blockchain transaction request includes: cross-blockchain transaction information between the first sub-blockchain system and a second sub-blockchain system, and an identifier of the second sub-blockchain system; the main blockchain system generating a block based on the cross-blockchain transaction information and uploading it to the main blockchain for storage; and the main blockchain system forwarding the cross-blockchain transaction request to the second sub-blockchain system based on the identifier of the second sub-blockchain system, so that the second sub-blockchain system executes the transaction based on the cross-blockchain transaction information.

[0008] According to other embodiments of the present disclosure, a system supporting cross-blockchain transactions is provided, comprising: a main blockchain system and multiple sub-blockchain systems; wherein the multiple sub-blockchain systems are divided into one or more levels, and when the sub-blockchain systems are divided into multiple levels, the sub-blockchain system at the highest level is directly connected to the main blockchain system via an interface, and the two sub-blockchain systems directly connected via the interface belong to one or two levels respectively, which are one level and two levels apart; the multiple sub-blockchain systems include a first sub-blockchain system and a second sub-blockchain system; the first sub-blockchain system is configured to send a cross-blockchain transaction request, wherein the cross-blockchain transaction request includes: cross-blockchain transaction information between the first sub-blockchain system and the second sub-blockchain system, and an identifier of the second sub-blockchain system; the main blockchain system is configured to receive the cross-blockchain transaction request sent by the first sub-blockchain system; generate a block based on the cross-blockchain transaction information and upload it to the main blockchain for storage; forward the cross-blockchain transaction request to the second sub-blockchain system based on the identifier of the second sub-blockchain system; and the second sub-blockchain system is configured to execute the transaction based on the cross-blockchain transaction information.

[0009] According to yet other embodiments of the present disclosure, an electronic device is provided, comprising: a processor; and a memory coupled to the processor, for storing instructions, which, when executed by the processor, causes the processor to perform the steps of the method for cross-blockchain transactions as described in any of the aforementioned embodiments.

[0010] According to further embodiments of the present disclosure, a non-transitory computer-readable storage medium is provided, on which a computer program is stored, wherein when the program is executed by a processor, the steps of the method for cross-blockchain transactions of any of the aforementioned embodiments are implemented.

[0011] In the present disclosure, a first sub-blockchain system initiates a cross-blockchain transaction request to a second sub-blockchain system. The request includes cross-blockchain transaction information and is transmitted through the main blockchain. During the transmission process, the main blockchain system stores the cross-blockchain transaction information on the main blockchain and witnesses the cross-blockchain transaction as a third party. After receiving the cross-blockchain transaction request, the second sub-blockchain system executes the transaction, completing the transaction between the first sub-blockchain system and the second sub-blockchain system, thereby realizing cross-blockchain transactions between different blockchain systems and ensuring the security of cross-blockchain transactions.

[0012] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0014] Figure 1 A schematic diagram illustrating the structure of a system supporting cross-blockchain transactions according to some embodiments of the present disclosure is shown.

[0015] Figure 2 A schematic diagram illustrating the architecture of a system supporting cross-blockchain transactions according to some embodiments of the present disclosure.

[0016] Figure 3 A flowchart illustrating a method for cross-blockchain transactions according to some embodiments of the present disclosure is provided.

[0017] Figure 4 A flowchart illustrating a method for cross-blockchain transactions according to other embodiments of the present disclosure is provided.

[0018] Figure 5A A schematic diagram illustrating a method for cross-blockchain transactions according to some embodiments of the present disclosure.

[0019] Figure 5B A schematic diagram illustrating a method for cross-blockchain transactions according to other embodiments of the present disclosure.

[0020] Figure 6 A schematic diagram illustrating the structure of a system supporting cross-blockchain transactions according to other embodiments of the present disclosure.

[0021] Figure 7 A schematic structural diagram of an electronic device according to some embodiments of the present disclosure is shown.

[0022] Figure 8 Schematic diagrams showing the structure of electronic devices according to other embodiments of the present disclosure. DETAILED DESCRIPTION

[0023] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is in no way intended to limit the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

[0024] The following first describes the architecture of the system supporting cross-blockchain transactions disclosed in the present invention.

[0025] Figure 1 This is a structural diagram of some embodiments of the system supporting cross-blockchain transactions disclosed in the present invention. Figure 1 As shown, the system 10 of this embodiment includes: a main blockchain system 110 and multiple sub-blockchain systems 120. The multiple sub-blockchain systems 120 are divided into one or more levels (e.g., L1, L2, etc.). When the sub-blockchain systems are divided into multiple levels, the sub-blockchain system 120 at the highest level (L1) is directly connected to the main blockchain system 110 via an interface. The two sub-blockchain systems directly connected via the interface are at different levels, one or two levels apart. An interface can be set at any node in the two blockchain systems to connect the two blockchain systems.

[0026] The system supporting cross-blockchain transactions disclosed in this disclosure is consistent with the future BVI (the concept of the Internet of Value) and can also be called the BVI blockchain network. Figure 1 As shown, system 10 consists of a main blockchain system (BVI parent blockchain network) and sub-blockchain systems (sub-chain networks), each of which contains multiple blockchain nodes. These sub-blockchain systems can be isomorphic to the main blockchain system or heterogeneous. The entire system forms a one-level or multi-level chain network architecture, supporting cross-chain communication between different sub-chains (sub-blockchain systems), and the sub-chains can be infinitely extended.

[0027] The main blockchain system can be hosted on a cloud network infrastructure and comprised of several supernodes. It serves as a global service chain, providing services such as full configuration (e.g., interface information and protocol configuration), consensus, and scheduling (e.g., scheduling access between different chains). Heterogeneous sub-blockchain systems within the sub-blockchain system can be composed of networks such as Ethereum and Hyperledger. While these heterogeneous sub-blockchain systems serve as lower-level blockchain systems directly connected to the main blockchain system, they can further connect to lower-level sub-blockchain systems to adapt to different business scenarios. Sub-blockchain systems within the sub-blockchain system, heterogeneous from the main blockchain, can be viewed as customized sharded networks, consisting of chains for various business models, divided according to business scenarios, isolation mechanisms, and performance overhead. Within this system, each layer is an independent micro-ecosystem, all of which form a complete ecosystem. These micro-ecosystems are interconnected through the BVI mother blockchain network, forming a single super-ecosystem.

[0028] The following combination Figure 2 The architecture of the system supporting cross-blockchain transactions disclosed herein is further described. Figure 2 Figure 1 is a structural diagram of another embodiment of the system supporting cross-blockchain transactions disclosed herein. Figure 2As shown, the system 10 of this embodiment is divided into three layers: BVI main chain (main blockchain system), BVI SDK, and BVI ecological chain (sub-blockchain system).

[0029] The BVI main chain serves as a relay for all ecosystem chains (sub-blockchain systems), forwarding and verifying all cross-chain messages. It supports smart contracts and the Multilevel Inter-Blockchain Communicate Protocol (MIBCP), a new protocol proposed in this disclosure and described in subsequent embodiments. The message pipeline is a communication medium that collects and forwards messages exchanged between different chains. The core business modules of the BVI main chain support P2P networks, consensus algorithms, permission control, smart contracts, transaction pools, permission control, cryptographic components, cross-network consistency monitoring, and ledger storage. Permission control provides an access mechanism to verify access to and integration into sub-blockchain systems, ensuring the security of nodes in one or more connected chain networks. This will be described in subsequent embodiments. Cryptographic components can include security algorithms such as national security and homomorphic encryption. Smart contracts can include a smart contract execution engine with a secure sandbox environment, providing a vehicle for executing main-chain and cross-chain contracts. The transaction pool can be used to cache packaged transactions to prevent network congestion. Cross-network consistency supervision: The BVI main chain provides final consistency confirmation for each ecosystem chain. For example, the latest block information generated by each ecosystem chain is uploaded to the main chain for supervision and storage. This will be described in detail in subsequent embodiments. The Docker cluster management tool refers to the containerized deployment of the BVI main chain, with nodes deployed and running as Docker images. Reference is made to existing technologies and will not be elaborated here.

[0030] BVI SDK: Other ecosystems and BVI applications can use the SDK to connect to the main chain. The SDK defines the MIBCP protocol and some basic logic functions.

[0031] BVI Ecosystem: This can include both isomorphic and heterogeneous subchains. These can be registered and linked to the main chain through the SDK to participate in cross-chain transactions. Furthermore, these ecosystems can also expand their own subchains to conduct one or more levels of cross-chain transactions.

[0032] The blockchain system mentioned in this disclosure includes multiple nodes and a blockchain for storing data.

[0033] This paper proposes a cross-blockchain transaction method. Figure 3 Provide a description.

[0034] Figure 3 Flowchart of some embodiments of the cross-blockchain transaction method disclosed in this disclosure. Figure 3As shown, the method of this embodiment includes steps S302 to S306.

[0035] In step S302, the main blockchain system receives the cross-blockchain transaction request sent by the first sub-blockchain system.

[0036] When a first sub-blockchain system initiates a cross-blockchain transaction request with a second sub-blockchain system, it can first generate a block with the cross-blockchain transaction information and store it on its own blockchain. The block generation and on-chain processes can be referenced in existing technologies, including, for example, broadcasting transaction information, consensus, and block generation, and are not detailed here. The cross-blockchain transaction request, for example, includes the cross-blockchain transaction information between the first and second sub-blockchain systems and the identifier of the second sub-blockchain system. Furthermore, the cross-blockchain transaction request also includes the identifier of the first sub-blockchain system. For example, a cross-blockchain transaction initiated from the tourism sub-chain to the data exchange sub-chain might include redemption information, such as: 10 travel points -> 20 data exchange points.

[0037] Depend on Figure 1 It can be understood that the first sub-blockchain system can be a blockchain system directly connected to the main blockchain system, and the main blockchain system receives cross-blockchain transaction requests sent by the first sub-blockchain system through an interface with the first sub-blockchain system. In some embodiments, when the main blockchain system and the first sub-blockchain system are connected through one or more tiers of blockchain systems, the main blockchain system receives cross-blockchain transaction requests sent by the first sub-blockchain system and forwarded through the one or more tiers of blockchain systems. The main blockchain system is the highest level, and the levels decrease from the main blockchain system to the first sub-blockchain system. Each tier of the tiers in the tiers receives cross-blockchain transaction requests from the connected lower-level blockchain system, generates blocks based on the cross-blockchain transaction information, uploads them to the own blockchain for storage, and forwards the cross-blockchain transaction requests to the connected higher-level blockchain system based on the identifier of the second sub-blockchain system.

[0038] In step S304, the main blockchain system generates a block based on the cross-blockchain transaction information and uploads it to the main blockchain for storage.

[0039] The main blockchain stores and records all cross-blockchain transaction information, improving the security of cross-blockchain transactions.

[0040] In step S306, the main blockchain system forwards the cross-blockchain transaction request to the second sub-blockchain system according to the identifier of the second sub-blockchain system, so that the second sub-blockchain system executes the transaction according to the cross-blockchain transaction information.

[0041] Depend on Figure 1It can be understood that the second sub-blockchain system can be a blockchain system directly connected to the main blockchain system, and the main blockchain system sends a cross-blockchain transaction request to the second sub-blockchain system through an interface with the second sub-blockchain system. In some embodiments, when the main blockchain system and the second sub-blockchain system are connected through one or more blockchain systems, the main blockchain system, based on the identifier of the second sub-blockchain system, queries the identifier of the blockchain system below the main blockchain system that the second sub-blockchain system passed through before reaching the main blockchain system. This identifier is used as the next-hop identifier, and the main blockchain system forwards the cross-blockchain transaction request to the blockchain system corresponding to the next-hop identifier. Each blockchain system in the one or more blockchain systems receives the cross-blockchain transaction request from the connected higher-level blockchain system, generates a block based on the cross-blockchain transaction information, uploads it to its own blockchain for storage, and forwards the cross-blockchain transaction request to the connected lower-level blockchain system based on the identifier of the second sub-blockchain system.

[0042] In some embodiments, the cross-blockchain transaction request is encapsulated using a preset multi-level cross-chain communication protocol (MIBCP); each blockchain system decapsulates the cross-blockchain transaction request according to the preset multi-level cross-chain communication protocol, obtains the identifier of the first sub-blockchain system in the source identification field, the identifier of the second sub-blockchain system in the destination identification field, and the cross-blockchain transaction information in the transaction packaging field.

[0043] Each blockchain system in the disclosed system supporting cross-blockchain transactions (the BVI blockchain network) is configured with a corresponding identifier based on the MIBCP protocol. Each blockchain system's identifier is a concatenation of the identifier of the higher-level blockchain system to which it is connected and the unique identifiers assigned to each blockchain system at the same level. The identifier of the higher-level blockchain system and the assigned unique identifier are separated by a delimiter. For example, each blockchain system has a unique ID. The ID is a single or multi-level code separated by ' / ' and carries link routing information. Each blockchain system is assigned a primary ID, which can be chained together to identify and locate the subchain. For example, if the primary blockchain system has an identifier of 0, and the sub-blockchain systems directly connected to the primary blockchain system are assigned different identifiers, such as 1, 2, etc., then the identifiers of the sub-blockchain systems directly connected to the primary blockchain system are 0 / 1, 0 / 2, and so on. This identification format allows each blockchain system to easily identify the identifier of the next-hop blockchain system.

[0044] MIBCP, or Multi-level Inter-chain Communication Protocol, is a key protocol in the disclosed system. All blockchain systems use the MIBCP protocol for message routing and cross-chain conversion. The protocol is defined as follows. The ID field is the ID of the transaction request initiator, which is the source identification field mentioned above. The TargetID field is the ID of the transaction request recipient, which is the destination identification field mentioned above. The Msg Info field is the information field of the message, including: MIBCPTxPacker field is the transaction packaging field, which can include cross-blockchain transaction information and can also include: the identifier and transaction hash of the block in which the cross-blockchain transaction information is stored in the blockchain system, which will be described in detail later. The MIBCPSenderBlock field is the block sending field, which contains information such as the latest block generated by the first sub-blockchain system, which will be described in detail later. Information exchanged between different blockchain systems in this disclosure is encapsulated and routed according to the MIBCP protocol.

[0045] On the path between the first and second sub-blockchain systems, each blockchain system that a cross-blockchain transaction request passes through generates a block from the cross-blockchain transaction information and uploads it to its own blockchain. This ensures the traceability of subsequent cross-blockchain transactions and improves the security of block chain transactions. To further enhance the security of cross-blockchain transactions, this disclosure incorporates a verification process during the transmission of cross-blockchain transaction requests. Some examples are described below.

[0046] In some embodiments, each of the primary blockchain system, the primary or multi-level blockchain system, and the second sub-blockchain system receives a cross-blockchain transaction request that also includes: an identifier of the first sub-blockchain system, and an identifier and transaction hash of the block in which the cross-blockchain transaction information is stored in the previous blockchain system. The identifier of the first sub-blockchain system can be set in the ID field according to MIBCP, and the identifier and transaction hash of the block in which the cross-blockchain transaction information is stored in the previous blockchain system can be set in the MIBCPTxPacker field according to MIBCP.

[0047] Furthermore, each blockchain system queries the transaction hash in the block stored in the previous blockchain system based on the identifier of the block, and matches it with the transaction hash in the cross-blockchain transaction request. If the match is consistent, the step of generating a block based on the cross-blockchain transaction information and uploading it to the current blockchain for storage is executed; otherwise, the verification fails and the cross-blockchain transaction request sent by the previous blockchain system is rejected. For each blockchain system, the previous blockchain system is the blockchain system located at the previous hop of the blockchain system on the path from the first sub-blockchain system to the second sub-blockchain system.

[0048] Based on the identifier of the second sub-blockchain system, each blockchain system along the path from the first sub-blockchain system to the second sub-blockchain system will sequentially transmit a cross-blockchain transaction request. After receiving the cross-blockchain transaction request from the previous blockchain system, each blockchain system verifies the transaction hash according to the aforementioned method. Since the transaction hash is generated based on the cross-blockchain transaction information, this verification ensures the security of the cross-blockchain transaction information. Once verified, the blockchain system generates a block based on the cross-blockchain transaction information and uploads it to the current blockchain for storage. After storage, the current blockchain system obtains the identifier and transaction hash of the block storing the cross-blockchain transaction information within its own blockchain system, adds these to the cross-blockchain transaction request, and sends it to the next blockchain system.

[0049] In some embodiments, each blockchain system in the primary blockchain system, the primary or secondary blockchain system, and the secondary sub-blockchain system receives a cross-blockchain transaction request that includes the certificate of the previous blockchain system. Each blockchain system also receives the signature of the previous blockchain system in response to the cross-blockchain transaction request. Each blockchain system's certificate is issued by the primary blockchain system. A hierarchical mechanism can be used for these certificates, with different levels of certificates having varying permissions, which can be configured based on actual needs.

[0050] Furthermore, each blockchain system verifies the signature result based on the public key of the previous blockchain system, and verifies whether the previous blockchain system has the authority to issue a cross-blockchain transaction request based on the certificate of the previous blockchain system. If the verification is successful and the previous blockchain system has the authority to issue a cross-blockchain transaction request, a block is generated based on the cross-blockchain transaction information and uploaded to this blockchain for storage.

[0051] Before sending a cross-blockchain transaction request, each blockchain system adds its own certificate to the request, signs the request, and then sends it. By verifying the signature and certificate of the previous blockchain system, each blockchain system ensures the legitimate identity and authority of the sender of the cross-blockchain transaction request, improving security.

[0052] The sub-blockchain system that can interact directly with the main blockchain system can be heterogeneous with the main blockchain system. When a sub-blockchain system that is directly connected to the main blockchain system and is heterogeneous sends a cross-blockchain transaction request to the main blockchain system (which can be initiated by itself or initiated by other blockchains and sent through the sub-blockchain system), the data structure of the cross-blockchain transaction request is adjusted according to the transaction data structure of the main blockchain system, and the cross-blockchain transaction request is signed according to the signature method of the main blockchain system, so that the main blockchain system can accurately parse and verify the data. When a sub-blockchain system that is directly connected to the main blockchain system and is heterogeneous sends any message to the main blockchain system, it can adjust the data structure of the message according to the transaction data structure of the main blockchain system and sign the message according to the signature method of the main blockchain system. These messages include archiving requests, registration requests, etc. in subsequent embodiments, which will not be described in detail later. As Figure 2 As shown, the sub-blockchain system can adjust the data structure of the above message and sign the message through the BVI SDK.

[0053] After receiving the cross-blockchain transaction request, the second sub-blockchain system executes the transaction, that is, broadcasts the cross-blockchain transaction information, and performs consensus, block generation and other operations.

[0054] like Figure 5A Shown are some application examples of cross-blockchain transactions. Figure 5A The data exchange subchain 0 / 1 / 1 issues a cross-blockchain transaction to the tourism subchain 0 / 2: (1) The data exchange subchain 0 / 1 / 1 packages the cross-blockchain transaction and generates a block on its own blockchain; (2) After generating the block, the cross-blockchain transaction request is sent to the data exchange parent chain 0 / 1 (Ethereum network); (3) The parent chain 0 / 1 verifies the cross-blockchain transaction request and then sends it to the BVI main chain; (4) The main chain sends the cross-blockchain transaction request to the tourism subchain based on the target routing information 0 / 2. (5) The tourism subchain verifies the cross-blockchain transaction request and executes the transaction.

[0055] In the above embodiment, the first sub-blockchain system initiates a cross-blockchain transaction request to the second sub-blockchain system. The request includes cross-blockchain transaction information and is transmitted through the main blockchain. During the transmission process, the main blockchain system stores the cross-blockchain transaction information on the main blockchain and witnesses the cross-blockchain transaction as a third party. After receiving the cross-blockchain transaction request, the second sub-blockchain system executes the transaction, completing the transaction between the first sub-blockchain system and the second sub-blockchain system, realizing cross-blockchain transactions between different blockchain systems and ensuring the security of cross-blockchain transactions.

[0056] When describing the system architecture, it was mentioned that the main blockchain system (BVI main chain) can achieve cross-network consistency supervision. In addition to the storage, verification and other supervision methods for cross-blockchain transactions in the above embodiments, the following will also describe some embodiments of the main blockchain system's supervision of the block information of each sub-blockchain system, which is also part of cross-network consistency supervision.

[0057] Figure 4 Flowcharts of other embodiments of the cross-blockchain transaction method disclosed herein. Figure 4 As shown, the method of this embodiment includes: steps S402 to S404.

[0058] In step S402, the main blockchain system receives the archiving request sent by the first sub-blockchain system.

[0059] The archive request, for example, includes: information about the most recently generated block in the first sub-blockchain system, a hash value of the most recently generated block, and the main blockchain system's identifier. The block information may include various information stored in blocks as known in the art, and will not be further elaborated. The archive request is encapsulated using a pre-defined multi-level cross-chain communication protocol. The main blockchain system and each of the first or multiple blockchain systems decapsulate the cross-blockchain transaction request according to the pre-defined multi-level cross-chain communication protocol, obtaining the identifier of the first sub-blockchain system in the source identifier field, the identifier of the main blockchain system in the destination identifier field, and information about the most recently generated block in the first sub-blockchain system and the hash value of the most recently generated block in the block sent field.

[0060] That is, the information of the latest generated block and the hash value of the latest generated block can be set in the MIBCPBlockSender field according to MIBCP. The identifier of the main blockchain system can be set in the TargetID field according to MIBCP.

[0061] The first sub-blockchain system can be a blockchain system directly connected to the main blockchain system. The main blockchain system receives the archive request sent by the first sub-blockchain system through an interface with the first sub-blockchain system. In some embodiments, when the main blockchain system and the first sub-blockchain system are connected via one or more tiers of blockchain systems, each tier of the tiers of blockchain systems receives the archive request sent by the connected lower-tier blockchain system, generates a block based on the hash value of the most recently generated block, uploads it to the own blockchain for storage, and forwards the archive request to the connected higher-tier blockchain system based on the identifier of the main blockchain system.

[0062] Each blockchain system passed through from the first sub-blockchain system to the main blockchain system records the hash value of the latest generated block in the archive request to improve the security of transactions in these blocks.

[0063] In step S404, the main blockchain system generates a block based on the hash value of the latest generated block and uploads it to the main blockchain for storage.

[0064] The main blockchain stores and records all blocks generated by all sub-blockchain systems, which can supervise and trace all blocks in the entire network, thereby improving security.

[0065] In some embodiments, to improve security, the main blockchain system and each blockchain system in the first-level or multi-level blockchain system calculates the hash value of the block based on the information of the latest generated block, matches it with the hash value in the archive request, and if the match is consistent, executes the step of generating a block based on the hash value of the latest generated block and uploading it to the current blockchain for storage.

[0066] Based on the main blockchain system's identifier, each blockchain system along the path from the first sub-blockchain system to the main blockchain system will sequentially transmit an archive request. After receiving the archive request from the previous blockchain system, each blockchain system verifies the block's hash using the aforementioned method. Because the block's hash is generated based on the information within the block, this verification ensures the security of the transaction information within the block. Once verification is successful, the blockchain system generates a block based on the block's hash value and uploads it to its own blockchain for storage.

[0067] In some embodiments, the archive request received by the primary blockchain system and each of the primary or multi-level blockchain systems also includes: the certificate of the previous blockchain system; each blockchain system also receives the signature result of the previous blockchain system in response to the archive request. Each blockchain system verifies the signature result using the public key of the previous blockchain system and verifies whether the previous blockchain system has the authority to issue the archive request using the certificate of the previous blockchain system. If the signature verification is successful and the previous blockchain system has the authority to issue the archive request, it generates a block based on the hash value of the most recently generated block and uploads it to the current blockchain for storage.

[0068] Before sending an archive request, each blockchain system adds its own certificate to the request, signs the request, and then sends it. By verifying the signature and certificate of the previous blockchain system, each blockchain system ensures the legitimate identity and authority of the sender of the archive request, improving security.

[0069] like Figure 5BAs shown in the figure, some embodiments of each sub-blockchain system uploading the latest generated block to the main blockchain system. The sub-blockchain system needs to continuously submit the latest block hash to the BVI main chain (main blockchain system). The main chain confirms the consistency of the block hash of each sub-blockchain system and archives the block hash of each sub-blockchain system to ensure the consistency and immutability of the sub-chain. Figure 5B As shown, the block (n-1) hash, block (n) hash of the Ethereum chain, the block (n-1) hash, and the block (n) hash of the tourism sub-chain are continuously submitted to the BVI main chain.

[0070] In the above embodiment, the blocks generated by the sub-blockchain system are uploaded to the main blockchain system for storage, which realizes the unified supervision of the transaction information of the entire network, can realize the traceability of the transaction information of the entire network, and improves the security of the transaction information of the entire network.

[0071] In some embodiments, each sub-blockchain system can register with the main blockchain system, which then assigns permissions and issues certificates to the sub-blockchain systems. For example, the main blockchain system receives a registration request from a first sub-blockchain system, where the registration request includes the identity of the first sub-blockchain system and the identity of the main blockchain system. The main blockchain system verifies the first sub-blockchain system based on the identity of the first sub-blockchain system. If the verification is successful, the main blockchain system sends a registration response to the first sub-blockchain system, which includes the identity and certificate assigned by the main blockchain system to the first sub-blockchain system, as well as the identity of the first sub-blockchain system.

[0072] The first sub-blockchain system can be a blockchain system directly connected to the main blockchain system. The main blockchain system receives a registration request or sends a registration response from the first sub-blockchain system via an interface with the first sub-blockchain system. In some embodiments, when the main blockchain system and the first sub-blockchain system are connected via one or more blockchain systems, the main blockchain system receives a registration request from the first sub-blockchain system, which is forwarded by the one or more blockchain systems. Each blockchain system in the one or more blockchain systems receives a registration request from a connected lower-level blockchain system, generates a block based on the registration request, uploads it to its own blockchain for storage, and forwards the registration request to the connected higher-level blockchain system based on the main blockchain system's identifier.

[0073] In some embodiments, the main blockchain system forwards the registration response to the first sub-blockchain system through one or more levels of blockchain systems; each level of blockchain system in the one or more levels of blockchain systems receives the registration response sent by the connected higher-level blockchain system, generates a block based on the registration response, and uploads it to the current blockchain for storage, and forwards the registration response to the connected lower-level blockchain system based on the identifier of the first sub-blockchain system.

[0074] The main blockchain system also generates blocks for registration requests and responses and uploads them to the main blockchain for storage. The above-described method enables unified management and allocation of permissions across all sub-blockchains in the entire network, ensuring the legitimacy and security of each sub-blockchain system and improving transaction security.

[0075] The disclosed solution can provide efficient and reliable value conversion capabilities for owners of resources such as data, algorithms, and computing power. It can also provide a powerful basic platform and high-speed pipeline for resource positioning and discovery, value transfer and conversion, and the free and secure circulation of data assets within and between blockchains around the world, thereby realizing trusted value circulation and cross-chain transactions between heterogeneous industry chains and seizing the commanding heights of ecological governance in the era of ubiquitous intelligent interconnection.

[0076] Figure 6 This is a structural diagram of some embodiments of the system supporting cross-blockchain transactions disclosed in the present invention. Figure 6 As shown, the system 60 of this embodiment includes: a main blockchain system 610 and multiple sub-blockchain systems; wherein the multiple sub-blockchain systems are divided into one or more levels. When the sub-blockchain systems are divided into multiple levels, the sub-blockchain system at the highest level is directly connected to the main blockchain system through an interface, and the two sub-blockchain systems directly connected through the interface belong to two levels that are one level apart; the multiple sub-blockchain systems include a first sub-blockchain system 620 and a second sub-blockchain system 630.

[0077] The first sub-blockchain system 620 is configured to send a cross-blockchain transaction request, wherein the cross-blockchain transaction request includes: cross-blockchain transaction information between the first sub-blockchain system 620 and the second sub-blockchain system 630, and an identifier of the second sub-blockchain system 630.

[0078] The main blockchain system 610 is configured to receive a cross-blockchain transaction request sent by the first sub-blockchain system 620; generate a block based on the cross-blockchain transaction information and upload it to the main blockchain for storage; and forward the cross-blockchain transaction request to the second sub-blockchain system 630 based on the identifier of the second sub-blockchain system 630;

[0079] The second sub-blockchain system 630 is configured to execute transactions based on the cross-blockchain transaction information.

[0080] In some embodiments, when the main blockchain system 610 and the first sub-blockchain system 620 are connected via one or more blockchain systems 640, the main blockchain system 610 is configured to receive a cross-blockchain transaction request sent by the first sub-blockchain system 620 and forwarded via the one or more blockchain systems 640;

[0081] Among them, the main blockchain system 610 has the highest level, and the levels decrease in sequence from the main blockchain system 610 to the first sub-blockchain system 620. Each level of the blockchain system in the first or multi-level blockchain system 620 is configured to receive a cross-blockchain transaction request sent by a connected lower-level blockchain system, generate a block based on the cross-blockchain transaction information, and upload it to the current blockchain for storage, and forward the cross-blockchain transaction request to the connected higher-level blockchain system according to the identifier of the second sub-blockchain system 630.

[0082] In some embodiments, when the main blockchain system 610 and the second sub-blockchain system are connected via one or more blockchain systems 640, the main blockchain system 610 is configured to query the identifier of the blockchain system at a lower level of the main blockchain system 610 that the second sub-blockchain system 630 passed through to reach the second sub-blockchain system 630 based on the identifier of the second sub-blockchain system 630, and use the identifier as the next-hop identifier, and forward the cross-blockchain transaction request to the blockchain system corresponding to the next-hop identifier;

[0083] Each level of the primary or multi-level blockchain system 640 is configured to receive a cross-blockchain transaction request sent by a connected higher-level blockchain system, generate a block based on the cross-blockchain transaction information, upload it to the current blockchain for storage, and forward the cross-blockchain transaction request to a connected lower-level blockchain system based on the identifier of the second sub-blockchain system 630.

[0084] In some embodiments, the cross-blockchain transaction request received by each blockchain system in the main blockchain system 610, the primary or multi-level blockchain system 640, and the second sub-blockchain system 630 also includes: the identifier of the first sub-blockchain system, the identifier of the block in which the cross-blockchain transaction information is stored in the previous blockchain system, and the transaction hash. Each blockchain system is configured to query the transaction hash in the block based on the identifier of the block stored in the previous blockchain system, match it with the transaction hash in the cross-blockchain transaction request, and if there is a match, execute the step of generating a block based on the cross-blockchain transaction information and uploading it to the current blockchain for storage; wherein, for each blockchain system, the previous blockchain system is the blockchain system located one hop before the current blockchain system on the path from the first sub-blockchain system to the second sub-blockchain system;

[0085] In some embodiments, each blockchain system in the primary blockchain system 610, the primary or multi-level blockchain system 640, and the second sub-blockchain system 630 receives a cross-blockchain transaction request that also includes: the certificate of the previous blockchain system; each blockchain system also receives the signature result of the previous blockchain system in response to the cross-blockchain transaction request. Each blockchain system is configured to verify the signature result using the public key of the previous blockchain system and verify whether the previous blockchain system has the authority to issue the cross-blockchain transaction request using the certificate of the previous blockchain system. If the signature verification is successful and the previous blockchain system has the authority to issue the cross-blockchain transaction request, a block is generated based on the cross-blockchain transaction information and uploaded to the current blockchain for storage.

[0086] In some embodiments, the cross-blockchain transaction request is encapsulated using a preset multi-level cross-chain communication protocol; each blockchain system in the main blockchain system 610, the first or multi-level blockchain system 640, and the second sub-blockchain system 630 is configured to decapsulate the cross-blockchain transaction request according to the preset multi-level cross-chain communication protocol, obtain the identifier of the first sub-blockchain system 620 in the source identifier field, the identifier of the second sub-blockchain system 630 in the destination identifier field, and the cross-blockchain transaction information in the transaction packaging field.

[0087] In some embodiments, each blockchain system is configured with a corresponding identifier. The identifier of each blockchain system is composed of the identifier of the higher-level blockchain system to which the blockchain system is connected and the unique identifier assigned to each blockchain system at the same level by the blockchain system. A separator is used to separate the identifier of the higher-level blockchain system and the assigned unique identifier.

[0088] In some embodiments, the main blockchain system 610 is further configured to receive an archiving request sent by the first sub-blockchain system 620, wherein the archiving request includes: information about the latest block generated by the first sub-blockchain system, a hash value of the latest block, and an identifier of the main blockchain system; generate a block based on the hash value of the latest block, and upload it to the main blockchain for storage.

[0089] In some embodiments, when the main blockchain system 610 and the first sub-blockchain system 620 are connected via one or more primary blockchain systems 640, the main blockchain system 610 is configured to receive an archive request sent by the first sub-blockchain system 620 and forwarded by the one or more primary blockchain systems 640. Each blockchain system in the one or more primary blockchain systems 640 is configured to receive an archive request sent by a connected lower-level blockchain system, generate a block based on the hash value of the most recently generated block, upload it to the current blockchain for storage, and forward the archive request to the connected higher-level blockchain system based on the identifier of the main blockchain system 610.

[0090] In some embodiments, the main blockchain system 610 and each of the primary or multi-level blockchain systems 640 calculates a hash value of the block based on the information of the most recently generated block, matches it with the hash value in the archive request, and if they match, generates a block based on the hash value of the most recently generated block and uploads it to the current blockchain for storage.

[0091] In some embodiments, the archiving request received by each blockchain system in the main blockchain system 610 and the first-level or multi-level blockchain system 640 also includes: the certificate of the previous blockchain system; each blockchain system also receives the signature result of the previous blockchain system for the archiving request; each blockchain system is configured to verify the signature result according to the public key of the previous blockchain system, and verify whether the previous blockchain system has the authority to issue the archiving request according to the certificate of the previous blockchain system. If the verification is successful and the previous blockchain system has the authority to issue the archiving request, a block is generated according to the hash value of the latest generated block and uploaded to the current blockchain for storage; wherein, for each blockchain system, the previous blockchain system is the blockchain system located at the previous hop of the blockchain system on the path from the first sub-blockchain system 620 to the main blockchain system.

[0092] In some embodiments, the archive request is encapsulated using a preset multi-level cross-chain communication protocol; the main blockchain system 610 and each blockchain system in the first or multi-level blockchain system 640 are configured to decapsulate the cross-blockchain transaction request according to the preset multi-level cross-chain communication protocol, obtain the identifier of the first sub-blockchain system in the source identifier field, the identifier of the main blockchain system in the destination identifier field, and the information of the latest block generated by the first sub-blockchain system 620 in the block sending field and the hash value of the latest generated block.

[0093] In some embodiments, the main blockchain system 610 is further configured to receive a registration request sent by the first sub-blockchain system 620, wherein the registration request includes: the identity of the first sub-blockchain system 620 and the identity of the main blockchain system 610; the first sub-blockchain system 620 is verified according to the identity of the first sub-blockchain system 620; if the verification is successful, the main blockchain system 610 sends a registration response to the first sub-blockchain system 620, and the registration response includes: the identity and certificate assigned by the main blockchain system to the first sub-blockchain system 620, and the identity of the first sub-blockchain system 620.

[0094] In some embodiments, when the main blockchain system 610 and the first sub-blockchain system 620 are connected through one or more levels of blockchain systems, the main blockchain system 610 receives a registration request sent by the first sub-blockchain system 620 and forwarded by the one or more levels of blockchain systems 640; each level of blockchain system in the one or more levels of blockchain systems 640 is configured to receive a registration request sent by a connected lower-level blockchain system, generate a block according to the registration request, upload it to the current blockchain for storage, and forward the registration request to the connected higher-level blockchain system according to the identifier of the main blockchain system 610.

[0095] In some embodiments, the main blockchain system 610 is configured to forward the registration response to the first sub-blockchain system 620 through the primary or multi-level blockchain system 640; wherein, each level blockchain system in the primary or multi-level blockchain system 640 is configured to receive the registration response sent by the connected higher-level blockchain system, generate a block based on the registration response, upload it to the current blockchain for storage, and forward the registration response to the connected lower-level blockchain system based on the identifier 620 of the first sub-blockchain system.

[0096] The electronic device in the embodiment of the present disclosure can be a node in any blockchain system in a system that supports cross-blockchain transactions, and can be implemented by various computing devices or computer systems. Figure 7 as well as Figure 8 Provide a description.

[0097] Figure 7 Figure 1 is a structural diagram of some embodiments of the electronic device disclosed herein. Figure 7 As shown, the electronic device 70 of this embodiment includes: a memory 710 and a processor 720 coupled to the memory 710, and the processor 720 is configured to execute the cross-blockchain transaction method in any of the embodiments of the present disclosure based on the instructions stored in the memory 710.

[0098] The memory 710 may include, for example, a system memory, a fixed non-volatile storage medium, etc. The system memory may store, for example, an operating system, an application program, a boot loader, a database, and other programs.

[0099] Figure 8 FIG. 1 is a structural diagram of some other embodiments of the electronic device disclosed herein. Figure 8As shown, the electronic device 80 of this embodiment includes: a memory 810 and a processor 820, which are similar to the memory 710 and the processor 720, respectively. It may also include an input / output interface 830, a network interface 840, a storage interface 850, etc. These interfaces 830, 840, 850 and the memory 810 and the processor 820 can be connected, for example, via a bus 860. Among them, the input / output interface 830 provides a connection interface for input / output devices such as a display, mouse, keyboard, and touch screen. The network interface 840 provides a connection interface for various networked devices, such as a database server or a cloud storage server. The storage interface 850 provides a connection interface for external storage devices such as SD cards and USB flash drives.

[0100] Those skilled in the art will appreciate that embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transient storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0101] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0102] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0103] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0104] The above are only preferred embodiments of the present disclosure and are not intended to limit the present disclosure. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A cross-blockchain transaction method, comprising: The main blockchain system receives a cross-blockchain transaction request sent by a first sub-blockchain system, including: when the main blockchain system and the first sub-blockchain system are connected through a primary or multi-level blockchain system, the main blockchain system receives the cross-blockchain transaction request sent by the first sub-blockchain system forwarded by the primary or multi-level blockchain system, wherein the cross-blockchain transaction request is encapsulated using a multi-level cross-chain communication protocol, including cross-blockchain transaction information between the first sub-blockchain system and the second sub-blockchain system in a transaction packaging field, an identifier of the first sub-blockchain system in a source identifier field, and an identifier of the second sub-blockchain system in a destination identifier field, and the identifier of the first sub-blockchain system and the second The identifiers of the sub-blockchain systems all carry link-router location information; the main blockchain system has the highest level, and the levels decrease in order from the main blockchain system to the first sub-blockchain system. Each blockchain system in the first or multi-level blockchain system receives the cross-blockchain transaction request sent by the connected lower-level blockchain system, decapsulates the cross-blockchain transaction request according to the preset multi-level cross-chain communication protocol, obtains the identifier of the first sub-blockchain system, the identifier of the second sub-blockchain system, and the cross-blockchain transaction information, generates a block based on the cross-blockchain transaction information, uploads it to the current blockchain for storage, and forwards the cross-blockchain transaction request to the connected higher-level blockchain system based on the identifier of the second sub-blockchain system. The main blockchain system generates a block based on the cross-blockchain transaction information and uploads it to the main blockchain for storage; The main blockchain system forwards the cross-blockchain transaction request to the second sub-blockchain system according to the identifier of the second sub-blockchain system, so that the second sub-blockchain system executes the transaction according to the cross-blockchain transaction information.

2. The method according to claim 1, wherein The main blockchain system forwarding the cross-blockchain transaction request to the second sub-blockchain system according to the identifier of the second sub-blockchain system includes: In the case where the main blockchain system and the second sub-blockchain system are connected via one or more blockchain systems, the main blockchain system queries the identifier of the blockchain system at a lower level than the main blockchain system that the second sub-blockchain system passes through, based on the identifier of the second sub-blockchain system, and uses the identifier as the next-hop identifier. The main blockchain system then forwards the cross-blockchain transaction request to the blockchain system corresponding to the next-hop identifier. Among them, the main blockchain system has the highest level, and the levels decrease in sequence from the main blockchain system to the second sub-blockchain system. Each level blockchain system in the one or more levels of blockchain systems receives the cross-blockchain transaction request sent by the connected higher-level blockchain system, generates a block according to the cross-blockchain transaction information, and uploads it to the current blockchain for storage, and forwards the cross-blockchain transaction request to the connected lower-level blockchain system according to the identifier of the second sub-blockchain system.

3. The method according to claim 1 or 2, wherein: Each of the primary blockchain system, the primary or multi-level blockchain system, and the second sub-blockchain system receives a cross-blockchain transaction request that further includes: an identifier of the first sub-blockchain system, an identifier of a block storing the cross-blockchain transaction information in the previous sub-blockchain system, and a transaction hash; The method further comprises: Each blockchain system queries the transaction hash in the block based on the identifier of the block stored in the previous blockchain system, and matches it with the transaction hash in the cross-blockchain transaction request. If a match is found, the system generates a block based on the cross-blockchain transaction information and uploads it to the current blockchain for storage. Among them, for each blockchain system, the previous blockchain system is the blockchain system located one hop before the blockchain system on the path from the first sub-blockchain system to the second sub-blockchain system.

4. The method according to claim 3, wherein: Each blockchain system in the main blockchain system, the primary or multi-level blockchain system, and the second sub-blockchain system receives a cross-blockchain transaction request that also includes: a certificate of the previous blockchain system; each blockchain system also receives a signature result of the previous blockchain system for the cross-blockchain transaction request; Each blockchain system generates a block based on the cross-blockchain transaction information and uploads it to the current blockchain for storage, including: Each blockchain system verifies the signature result based on the public key of the previous blockchain system, and verifies whether the previous blockchain system has the authority to issue a cross-blockchain transaction request based on the certificate of the previous blockchain system. If the verification is successful and the previous blockchain system has the authority to issue a cross-blockchain transaction request, a block is generated based on the cross-blockchain transaction information and uploaded to the current blockchain for storage.

5. The method according to claim 1 or 2, wherein: Each blockchain system is configured with a corresponding identifier. The identifier of each blockchain system is composed of the identifier of the higher-level blockchain system connected to the blockchain system and the unique identifier assigned to each blockchain system at the same level. The identifier of the higher-level blockchain system and the assigned unique identifier are separated by a separator.

6. The method according to claim 1, further comprising: The main blockchain system receives an archive request sent by the first sub-blockchain system, wherein the archive request includes: information of a latest block generated by the first sub-blockchain system, a hash value of the latest block generated, and an identifier of the main blockchain system; The main blockchain system generates a block based on the hash value of the latest generated block and uploads it to the main blockchain for storage.

7. The method according to claim 6, wherein: The main blockchain system receiving the archiving request sent by the first sub-blockchain system includes: In a case where the main blockchain system and the first sub-blockchain system are connected via one or more blockchain systems, the main blockchain system receives an archive request sent by the first sub-blockchain system and forwarded via the one or more blockchain systems; Among them, the main blockchain system has the highest level, and the levels decrease from the main blockchain system to the first sub-blockchain system. Each level of the blockchain system in the one or more levels of the blockchain system receives the archiving request sent by the connected lower-level blockchain system, generates a block according to the hash value of the latest generated block, and uploads it to the current blockchain for storage, and forwards the archiving request to the connected higher-level blockchain system according to the identifier of the main blockchain system.

8. The method according to claim 7, further comprising: The main blockchain system and each blockchain system in the primary or multi-level blockchain system calculates a hash value of the block based on the information of the latest generated block, matches it with the hash value in the archive request, and if they match, generates a block based on the hash value of the latest generated block and uploads it to the current blockchain for storage.

9. The method according to claim 8, wherein The archiving request received by the primary blockchain system and each of the primary or multi-level blockchain systems further includes: a certificate of the previous blockchain system; each blockchain system also receives a signature result of the previous blockchain system on the archiving request; Each blockchain system generates a block according to the hash value of the latest generated block, including: Each blockchain system verifies the signature result using the public key of the previous blockchain system and verifies whether the previous blockchain system has the authority to issue the archiving request based on the certificate of the previous blockchain system. If the verification is successful and the previous blockchain system has the authority to issue the archiving request, it generates a block based on the hash value of the latest generated block and uploads it to the current blockchain for storage. Among them, for each blockchain system, the previous blockchain system is the blockchain system located one hop before the blockchain system on the path from the first sub-blockchain system to the main blockchain system.

10. The method according to claim 7, wherein: The archiving request is encapsulated using a preset multi-level cross-chain communication protocol; The main blockchain system and each blockchain system in the first or multi-level blockchain systems decapsulates the cross-blockchain transaction request according to the preset multi-level cross-chain communication protocol, obtains the identifier of the first sub-blockchain system in the source identifier field, the identifier of the main blockchain system in the destination identifier field, and the information of the latest block generated by the first sub-blockchain system in the block sending field and the hash value of the latest generated block.

11. The method according to claim 1 , further comprising: The main blockchain system receives a registration request sent by the first sub-blockchain system, wherein the registration request includes: an identity identifier of the first sub-blockchain system and an identifier of the main blockchain system; The main blockchain system verifies the first sub-blockchain system according to the identity identifier of the first sub-blockchain system; If the verification is successful, the main blockchain system sends a registration response to the first sub-blockchain system. The registration response includes: the identifier and certificate assigned by the main blockchain system to the first sub-blockchain system, and the identifier of the first sub-blockchain system.

12. The method according to claim 11, wherein The main blockchain system receiving the registration request sent by the first sub-blockchain system includes: In a case where the main blockchain system and the first sub-blockchain system are connected via a primary or multi-level blockchain system, the main blockchain system receives a registration request sent by the first sub-blockchain system and forwarded via the primary or multi-level blockchain system; Among them, the main blockchain system has the highest level, and the levels decrease from the main blockchain system to the first sub-blockchain system. Each level of the blockchain system in the one or more levels of the blockchain system receives the registration request sent by the connected lower-level blockchain system, generates a block according to the registration request, and uploads it to the current blockchain for storage, and forwards the registration request to the connected higher-level blockchain system according to the identifier of the main blockchain system.

13. The method according to claim 12, wherein: The main blockchain system sending a registration response to the first sub-blockchain system includes: The main blockchain system forwards the registration response to the first sub-blockchain system through the primary or multi-level blockchain system; Among them, each level blockchain system in the one or more level blockchain systems receives the registration response sent by the connected higher-level blockchain system, generates a block according to the registration response, and uploads it to the current blockchain for storage, and forwards the registration response to the connected lower-level blockchain system according to the identifier of the first sub-blockchain system.

14. A system supporting cross-blockchain transactions, comprising: Main blockchain system and multiple sub-blockchain systems; Wherein, the multiple sub-blockchain systems are divided into one or more levels. When the sub-blockchain systems are divided into multiple levels, the highest-level sub-blockchain system is directly connected to the main blockchain system via an interface, and the two sub-blockchain systems directly connected via the interface are respectively one level and two levels apart; the multiple sub-blockchain systems include a first sub-blockchain system and a second sub-blockchain system; The first sub-blockchain system is configured to send a cross-blockchain transaction request, wherein the cross-blockchain transaction request is encapsulated using a multi-level cross-blockchain communication protocol and includes: cross-blockchain transaction information between the first sub-blockchain system and the second sub-blockchain system in a transaction packaging field, an identifier of the first sub-blockchain system in a source identifier field, and an identifier of the second sub-blockchain system in a destination identifier field, wherein the identifier of the first sub-blockchain system and the identifier of the second sub-blockchain system both carry link routing location information; The main blockchain system is configured to receive a cross-blockchain transaction request sent by a first sub-blockchain system, including: when the main blockchain system and the first sub-blockchain system are connected via a primary or multi-level blockchain system, the main blockchain system receives the cross-blockchain transaction request sent by the first sub-blockchain system forwarded by the primary or multi-level blockchain system, wherein the primary blockchain system has the highest level, and the levels decrease in order from the main blockchain system to the first sub-blockchain system, each level of the primary or multi-level blockchain system receives the cross-blockchain transaction request sent by the connected lower-level blockchain system, decapsulates the cross-blockchain transaction request according to a preset multi-level cross-chain communication protocol, obtains an identifier of the first sub-blockchain system, an identifier of the second sub-blockchain system, and the cross-blockchain transaction information, generates a block based on the cross-blockchain transaction information, uploads it to the current blockchain for storage, and forwards the cross-blockchain transaction request to the connected higher-level blockchain system based on the identifier of the second sub-blockchain system; generates a block based on the cross-blockchain transaction information, and uploads it to the main blockchain for storage; and forwards the cross-blockchain transaction request to the second sub-blockchain system based on the identifier of the second sub-blockchain system; The second sub-blockchain system is configured to execute a transaction based on the cross-blockchain transaction information.

15. An electronic device comprising: processor; as well as A memory coupled to the processor, configured to store instructions, wherein when the instructions are executed by the processor, the processor executes the steps of the method for cross-blockchain transactions according to any one of claims 1 to 13.

16. A non-transitory computer-readable storage medium having a computer program stored thereon, wherein: When the program is executed by a processor, the steps of the cross-blockchain transaction method according to any one of claims 1 to 13 are implemented.

Citation Information

Patent Citations

  • A multi-blockchain cross-chain transaction processing system and method

    CN109636395A

  • Cross-block chain data information synchronization method and device, equipment and medium

    CN110597907A