A multi-chain alliance blockchain architecture

Abstract

The present application relates to a multi-chain alliance blockchain architecture. The physical nodes in the alliance blockchain include at least one type of proxy nodes, alliance nodes, archive nodes, and light nodes. The alliance blockchain architecture includes a genesis block and several organizations. Several physical nodes are deployed in the organization, and each organization contains several chain structures. The deployment of the alliance blockchain requires at least one proxy node to provide an external interface, an archive node to store complete alliance blockchain data, and three or more alliance nodes to run the consensus protocol normally, where each organization needs to run at least one alliance node. By dividing the node types and modular design, the system can ensure the fast and low-cost construction of the system while ensuring the different business deployment requirements of each organization. The design of the alliance node ensures that a single organization alliance node only stores the block data of its own organization, thereby ensuring the needs of each organization for protecting privacy data.

Description

Technical Field

[0001] The present application relates to the field of blockchain technology, and in particular to a multi-chain alliance blockchain architecture. Background Art

[0002] As a new technology, blockchain is widely used in many fields, including information processing systems, Internet of Things systems, and medical systems. According to the access control mechanism of nodes, blockchain can be divided into public blockchain, private blockchain, and alliance blockchain. Alliance blockchain has a weakly centralized structure, usually composed of multiple organizations that do not trust each other, and the number of nodes within the organization is smaller, which allows the ecological governance in the alliance chain to be completed with the participation of only a small number of nodes. Fewer nodes participating in governance voting means that the alliance chain has higher efficiency, and the alliance chain has a relatively trusted network environment, so it can avoid the user privacy risks brought by the transparency and openness of the entire network.

[0003] At present, the exploration of alliance blockchain is still in its early stages. Alliance blockchain has serious performance problems. The performance status of alliance blockchain is far from the performance requirements of such application scenarios with large-scale organizations, nodes, and complex business systems. At present, the application of high-performance alliance blockchain faces the following challenges: the current alliance chain architecture cannot meet the needs of large-scale industry applications. With the increase in the number of organizations and nodes joining the alliance blockchain system, the alliance chain architecture currently proposed has the problem of significantly reduced throughput when the number of nodes increases. On the other hand, each organization or unit does not want to share its core data. Secondly, in such scenarios, the business system is usually complex and diverse, including internal systems of organizations and business systems shared by alliances. The existing alliance chain architecture cannot meet all business system requirements. Therefore, designing an alliance blockchain architecture suitable for large-scale industry applications is of great significance for the implementation of alliance chains. Summary of the invention

[0004] In order to solve or partially solve the problems existing in the related technologies, the present application provides a multi-chain alliance blockchain architecture, which can ensure the fast and low-cost construction of the system by dividing the node types and modular design, while ensuring the different business deployment needs of various organizations.

[0005] The first aspect of the present application provides a multi-chain alliance blockchain architecture.

[0006] The physical nodes in the alliance blockchain include at least one type of proxy nodes, alliance nodes, archive nodes, and light nodes. The alliance blockchain architecture includes a genesis block and several organizations. Several physical nodes are deployed in the organizations. Each organization contains several chain structures. The alliance blockchain requires at least one proxy node to provide an external interface, an archive node to store complete alliance blockchain data, and three or more alliance nodes to run the consensus protocol normally. Each organization needs to run at least one alliance node.

[0007] Preferably, the proxy node is used for chaining and data preprocessing, and encapsulating the interface of the alliance blockchain.

[0008] Preferably, the proxy node is also used to dynamically add new organizations and / or physical nodes to the alliance blockchain when there is no need for data confidentiality.

[0009] Preferably, the alliance node is deployed in an organization and is used to store the block data of the organization.

[0010] Preferably, the alliance node is also used for block sorting, block generation, block synchronization, and cross-organization and / or inter-chain interactions.

[0011] Preferably, the archiving node is used for block data synchronization, account book storage, and data backup.

[0012] Preferably, the light node is used to store the plurality of chain structure block header data, synchronize and verify block header information, and verify data.

[0013] Preferably, the organization also includes several units, in which several light nodes are deployed according to needs.

[0014] Preferably, the light node is deployed in a unit, and new units and / or physical nodes are dynamically added to the alliance blockchain.

[0015] The technical solution provided by the present application may include the following beneficial effects: the embodiment of the present application discloses a multi-chain alliance blockchain architecture, the physical nodes in the alliance blockchain include at least one type of proxy nodes, alliance nodes, archive nodes, and light nodes, and each type of node has different functions. The alliance blockchain includes several organizations, and several physical nodes are deployed in the organization. Each organization contains several chain structures. The deployment of the alliance blockchain requires at least one proxy node to provide an external interface, an archive node is used to store complete alliance blockchain data, and three or more alliance nodes are used to run the consensus protocol normally, wherein each organization needs to run at least one alliance node. By dividing the node types and modular design, the system can ensure the fast and low-cost construction of the system while ensuring the different business deployment requirements of each organization. The design of the alliance node ensures that a single organization alliance node only stores the block data of its own organization, thereby guaranteeing the needs of each organization for protecting privacy data.

[0016] The technical solution provided by the present application also includes the following beneficial effects: by supporting the dynamic joining of organizations or nodes through the functions of proxy nodes and light nodes, the scalability of the entire architecture is improved.

[0017] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and other objects, features and advantages of the present application will become more apparent by describing in more detail the exemplary embodiments of the present application in conjunction with the accompanying drawings, wherein the same reference numerals generally represent the same components in the exemplary embodiments of the present application.

[0019] Figure 1 It is a schematic diagram of the structure of the alliance blockchain shown in the embodiment of the present application;

[0020] Figure 2 is a schematic diagram of the alliance node storage structure shown in an embodiment of the present application;

[0021] Figure 3 It is a schematic diagram of the archiving node storage structure shown in an embodiment of the present application;

[0022] Figure 4 It is a schematic diagram of the light node storage structure shown in the embodiment of the present application;

[0023] Figure 5 This is another structural diagram of the alliance blockchain shown in the embodiment of the present application. DETAILED DESCRIPTION

[0024] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments described herein. On the contrary, these embodiments are provided to make the present application more thorough and complete, and to fully convey the scope of the present application to those skilled in the art.

[0025] The terms used in this application are for the purpose of describing specific embodiments only and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0026] It should be understood that although the terms "first", "second", "third", etc. may be used in this application to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "multiple" is two or more, unless otherwise clearly and specifically defined.

[0027] The current alliance chain architecture cannot meet the needs of large-scale industry applications. With the increase in the number of organizations and nodes joining the alliance blockchain system, the alliance chain architecture currently proposed has the problem of significantly reduced throughput when the number of nodes increases. On the other hand, each organization or unit does not want to share its core data. Secondly, in such scenarios, the business system is usually complex and diverse, including the internal system of the organization and the business system shared by the alliance. The existing alliance chain architecture cannot meet all business system requirements. Therefore, designing an alliance blockchain architecture suitable for large-scale industry applications is of great significance for the implementation of the alliance chain.

[0028] In response to the above problems, the embodiments of the present application provide a multi-chain alliance blockchain architecture, which can ensure the rapid and low-cost construction of the system by dividing the node types and modular design, while ensuring the different business deployment needs of various organizations or units. The design of the alliance node ensures that a single organization's alliance node only stores the block data of its own organization, thereby ensuring the needs of various organizations or units for protecting privacy data.

[0029] The technical solution of the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0030] Figure 1It is a schematic diagram of the structure of the alliance blockchain shown in the embodiment of the present application.

[0031] See also Figure 1 The physical nodes in the alliance blockchain 101 include at least one type of proxy nodes 102, alliance nodes 103, archive nodes 104, and light nodes 105. The alliance blockchain 101 includes several organizations, and several physical nodes are deployed in the organizations. Each organization contains several chain structures; deploying the alliance blockchain 101 requires at least one proxy node 102 to provide an external interface, an archive node 104 is used to store complete alliance blockchain 101 data, and three or more alliance nodes 103 are used to run the consensus protocol normally, where each organization needs to run at least one alliance node 103.

[0032] Alliance Blockchain 101 has a weakly centralized structure, usually composed of multiple organizations that do not trust each other, and the number of nodes within the organization is smaller, which means that the ecological governance in Alliance Blockchain 101 can be completed with the participation of only a small number of nodes. Fewer nodes participating in governance voting means that Alliance Blockchain 101 has higher efficiency. At the same time, Alliance Blockchain 101 has a relatively trusted network environment, so it can avoid user privacy risks caused by data transparency and openness across the entire network.

[0033] In the embodiment of the present application, the business end is connected to the alliance blockchain 101 for communication, and the business end can interact with the alliance blockchain 101 for data through SDK (Software Development Kit).

[0034] In the embodiment of the present application, the physical nodes in the alliance blockchain 101 can be logically classified into at least one of the following types: proxy node 102, alliance node 103, archive node 104, and light node 105. Each type of node is a separate code module when actually deployed. You can choose how to deploy different types of nodes on which physical node according to your needs. Each type of node has different functions. In the actual operation process, the same physical entity node can serve as multiple node types. When the alliance blockchain 101 is deployed, at least one proxy node 102, one archive node 104, and three or more alliance nodes 103 are required, wherein the proxy node 102 can provide an external interface; the archive node 104 is used to store complete alliance blockchain data; the alliance node 103 is used to run the consensus protocol normally, wherein each organization needs to run at least one alliance node 103. In actual deployment, the node type can be selected according to the node function and business needs. The functional modules of the alliance blockchain 101 are decoupled by dividing the node types into proxy nodes 102, alliance nodes 103, archive nodes 104, and light nodes 105. After decoupling, functions can be deployed in different physical nodes, and after decoupling, different functions can be deployed on the same physical node.

[0035] The alliance blockchain 101 is usually used to solve the problem of data sharing between organizations. In one example, taking the government department as an example, the Civil Affairs Bureau, the Public Security Bureau, the Court, etc. can be divided into different organizations. In business cooperation, each company can also be divided into different organizations. In the embodiment of the present application, the alliance blockchain 101 includes organization one, organization two, organization three... multiple organizations, and each organization includes several chain structures. The alliance blockchain 101 of the embodiment of the present application is multi-chain. After creating the genesis block, it no longer continues to build and maintain a single chain after the genesis block, but can point to multiple blocks afterwards, and then each subsequent block continues to build and maintain a chain, thereby forming a multi-chain blockchain structure.

[0036] In an optional embodiment of the present application, the proxy node is used for chain uploading and data preprocessing, and encapsulating the interface of the alliance blockchain.

[0037] In the blockchain, all transactions are recorded on the blockchain, where each block includes the hash value of the previous block, thus forming a chain-on-chain structure. Blockchain-on-chain is the act of adding a new transaction record to the blockchain.

[0038] In the embodiment of the present application, the proxy node 102 can be used to upload data and perform data preprocessing. Data preprocessing mainly refers to load balancing of blockchain physical nodes in the case of large-scale data, avoiding excessive data volume that a single physical node needs to process, and improving the data processing capacity of the blockchain. In addition, the interface provided by the alliance blockchain 101 to the outside can also be repackaged and provided to the outside, so as to adapt to different business terminals.

[0039] The proxy node 102 also undertakes functions such as blockchain browser, BaaS (Blockchain as a Service), contract IDE (Integrated Development Environment), etc.

[0040] In an optional embodiment of the present application, the proxy node is also used to dynamically add new organizations and / or physical nodes to the consortium blockchain when there is no need for data confidentiality.

[0041] At present, when most alliance blockchains are running, if a new organization joins and a new physical node needs to be deployed, because the physical node may involve consensus, ledger storage and other functions, it is necessary to stop the system and modify the configuration file, perform related operations such as associating each node network and synchronizing data, and then restart the system. The process of deleting an organization or node is similar. In the embodiment of the present application, a proxy node 102 is set, and the coupling degree between the proxy node 102 and the alliance blockchain 101 is low. When there is no need for data confidentiality, it is only necessary to modify the configuration file and reference it to quickly deploy new organizations and / or physical nodes to dynamically join the alliance blockchain 101. By setting up proxy nodes to support the dynamic joining of organizations and / or physical nodes, the scalability of the entire architecture is improved.

[0042] In an optional embodiment of the present application, the alliance node is deployed in an organization to store the block data of the organization.

[0043] The alliance node 103 can be deployed in an organization. Each alliance node 103 stores the block data of the organization to which it belongs, ensuring the needs of each organization for protecting privacy data.

[0044] like Figure 2 As shown, it is a schematic diagram of the alliance node storage structure provided by the embodiment of the present application. After the creation of the genesis block, it is no longer necessary to continue to build and maintain a single chain after the genesis block, but it can point to blocks in multiple different organizations afterwards, and then each subsequent block continues to build and maintain a chain, thereby forming a multi-chain blockchain structure. The alliance node 103 only stores the block data of the organization to which it belongs.

[0045] In an optional embodiment of the present application, the alliance node is also used for block sorting, block generation, block synchronization, and cross-organization and / or inter-chain interactions.

[0046] The alliance node 103 can also undertake the service of generating new block sequence numbers, including functions such as block sorting, block generation, and block synchronization. When different organizations or chains need to interact with each other, the alliance node 103 is responsible for the cross-organization and / or inter-chain interaction function.

[0047] In an optional embodiment of the present application, the archiving node is used for block data synchronization, ledger storage, and data backup.

[0048] The archiving node 104 is a node that maintains the integrity of the blockchain structure in the alliance blockchain 101, and is responsible for block synchronization, account book storage, data backup, etc. The alliance node 103 can synchronize the data after consensus on the chain to the archiving node 104. When the archiving node 104 crashes or is attacked and causes data loss, it can synchronize data to the crashed node.

[0049] like Figure 3 As shown, it is a schematic diagram of the archival node storage structure provided by the embodiment of the present application. After the creation of the genesis block, it is no longer necessary to continue to build and maintain a single chain after the genesis block, but it can point to block data of multiple different organizations, and then each subsequent block header continues to build and maintain a chain, thus forming a multi-chain blockchain structure.

[0050] In an optional embodiment of the present application, the light node is used to store a number of chain structure block header data, synchronize and verify block header information, and verify data.

[0051] The light node 105 is used to store several chain structure block header data, synchronize and verify block header information, and verify data. In the embodiment of the present application, the chain structure based on the blockchain is multi-chain, and the block header data stored in the light node is also the block header data of multiple chains.

[0052] like Figure 4 As shown, it is a schematic diagram of the light node storage structure provided by the embodiment of the present application. After the creation of the genesis block, it is no longer necessary to continue to build and maintain a single chain after the genesis block, but it can point to the block header data of multiple different organizations, and then each subsequent block header continues to build and maintain a chain, thus forming a multi-chain blockchain structure.

[0053] In an optional embodiment of the present application, the organization also includes a number of units, and a number of light nodes are deployed in the units according to needs.

[0054] In the embodiment of the present application, the organization in the alliance blockchain 101 can also be divided into different units. A unit can be deployed with a number of light nodes 105 according to actual needs, and the physical node on which the light node 105 is deployed can be selected according to needs.

[0055] In an optional embodiment of the present application, light nodes are deployed in units, and new units and / or physical nodes are dynamically added to the alliance blockchain.

[0056] At present, when most alliance blockchains 101 are running, if a new unit joins and a new physical node needs to be deployed, because the physical node may involve consensus, ledger storage and other functions, it is necessary to stop the system and modify the configuration file, perform related operations such as associating each node network and synchronizing data, and then restart the system. The process of deleting a unit or node is similar. In the embodiment of the present application, a light node 105 is set. The coupling degree between the light node 105 and the alliance blockchain 101 is low. Only the configuration file needs to be modified and referenced to quickly deploy new units and / or physical nodes to dynamically join the alliance blockchain 101. By setting the light node 105 to support the dynamic joining of units and / or physical nodes, the scalability of the entire architecture is improved.

[0057] In an optional embodiment of the present application, the alliance blockchain architecture is designed based on the ledger structure of the alliance blockchain.

[0058] In the embodiment of the present application, the chain structure of each organization and unit is different from the storage structure of the archive node 104. The chain structure in the alliance blockchain architecture is designed based on the ledger structure of the alliance blockchain. After piecing together the chain structures under each organization, a complete ledger structure stored in the archive node 104 can be obtained.

[0059] Figure 5 is another structural diagram of the alliance blockchain shown in the embodiment of the present application. Figure 5 The physical nodes in the alliance blockchain 500 include at least one type of proxy nodes 501, alliance nodes 502, archive nodes 503, and light nodes 504. The alliance blockchain includes several organizations, different types of nodes are deployed in the organizations, and each organization contains several chain structures.

[0060] In the embodiment of the present application, the alliance blockchain includes organization 1, organization 2, ..., multiple organizations, each of which includes several chain structures. In the embodiment of the present application, the organizations in the alliance blockchain 500 can also be divided into different units. In one example, organization 1 can be divided into unit 1, unit 2, .... Several physical nodes are deployed in the unit, and it can be selected on which physical node to deploy different types of nodes according to needs. Light nodes are deployed in the unit, and new units and / or physical nodes are dynamically added to the alliance blockchain.

[0061] The embodiment of the present application discloses a multi-chain alliance blockchain architecture, in which the physical nodes in the alliance blockchain include at least one type of proxy nodes, alliance nodes, archive nodes, and light nodes. The alliance blockchain architecture includes several organizations, in which several physical nodes are deployed, and each organization contains several chain structures; the deployment of the alliance blockchain requires at least one proxy node to provide an external interface, an archive node to store complete alliance blockchain data, and three or more alliance nodes to run the consensus protocol normally, wherein each organization needs to run at least one alliance node. By dividing the node types and modular design, the system can ensure the fast and low-cost construction of the system while ensuring the different business deployment requirements of each organization. The design of the alliance node ensures that the alliance node of a single organization only stores the block data of its own organization, thereby ensuring the needs of each organization for protecting privacy data.

[0062] The embodiments of the present application have been described above, and the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The selection of terms used herein is intended to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A multi-chain alliance blockchain architecture, characterized by: The physical nodes in the alliance blockchain include at least one type of proxy nodes, alliance nodes, archive nodes, and light nodes; the alliance blockchain architecture is a multi-chain structure, which is designed based on the ledger structure of the alliance blockchain. The alliance blockchain architecture includes a genesis block and several organizations. The organization includes several units. Several physical nodes are deployed in the organization. Each organization contains several chain structures; the several chain structures share a genesis block; the deployment of the alliance blockchain requires at least one proxy node to provide an external interface, an archive node is used to store complete alliance blockchain data, and three or more alliance nodes are used to run the consensus protocol normally, wherein each organization needs to run at least one alliance node, which is deployed in the organization and used to store the block data of the organization in a single chain form; the chain structures under each of the organizations are pieced together to obtain the alliance blockchain data stored in the archive node; Wherein, the proxy node is used to dynamically add new organizations and / or physical nodes to the alliance blockchain by modifying the configuration file and referencing it when there is no need for data confidentiality; The light node is deployed in the unit and is used to dynamically add new units and / or physical nodes to the alliance blockchain by modifying the configuration file and referencing it.

2. The alliance blockchain architecture according to claim 1, characterized in that: The proxy node is used for chaining and data preprocessing, and encapsulates the interface of the alliance blockchain.

3. The alliance blockchain architecture according to claim 1, characterized in that: The alliance nodes are also used for block sorting, block generation, block synchronization, and cross-organization and / or inter-chain interactions.

4. The alliance blockchain architecture according to claim 1, characterized in that: The archiving node is used for block data synchronization, account book storage, and data backup.

5. The alliance blockchain architecture according to claim 1, characterized in that: The light node is used to store the plurality of chain structure block header data, synchronize and verify block header information, and verify data.

6. The alliance blockchain architecture according to claim 1, characterized in that: Several light nodes are deployed in the unit according to needs.

Images