CN113259117A - Method for synchronizing node information lists - Google Patents

Method for synchronizing node information lists Download PDF

Info

Publication number
CN113259117A
CN113259117A CN202110611531.4A CN202110611531A CN113259117A CN 113259117 A CN113259117 A CN 113259117A CN 202110611531 A CN202110611531 A CN 202110611531A CN 113259117 A CN113259117 A CN 113259117A
Authority
CN
China
Prior art keywords
node
list
blockchain
network
node information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110611531.4A
Other languages
Chinese (zh)
Other versions
CN113259117B (en
Inventor
陶友贤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202110611531.4A priority Critical patent/CN113259117B/en
Publication of CN113259117A publication Critical patent/CN113259117A/en
Application granted granted Critical
Publication of CN113259117B publication Critical patent/CN113259117B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees

Abstract

One or more embodiments of the present specification provide a method of synchronizing a list of node information. Each node of the first blockchain network constructs a list designation message for designating a node information list acquired by the node, and broadcasts the list designation message to the first blockchain network. Each node of the first blockchain network can acquire the list designation message broadcast by each other node, each node can summarize the condition that each node of the first blockchain network acquires the node information list, if it is determined that more than N nodes acquire the consistent node information list, the consistent node information list can be determined to be accurate, and then the list synchronous transaction containing the consistent node information list can be broadcast to the first blockchain network. And each node completes the synchronization of the node information list in a mode of executing the list synchronization transaction.

Description

Method for synchronizing node information lists
Technical Field
One or more embodiments of the present disclosure relate to the field of terminal technologies, and in particular, to a method for synchronizing node information lists.
Background
The blockchain technique is built on top of a transport network, such as a point-to-point network. Nodes in the blockchain network utilize a chained data structure to validate and store data and employ a distributed node consensus algorithm to generate and update data. In some blockchain networks, there is sometimes a need for some nodes to implement small-scale transactions to avoid other nodes from obtaining these transactions and their associated data.
In the related art, assuming that the existing blockchain network is a blockchain master network, subnet nodes other than the master network node may be deployed on node devices participating in part of members of the blockchain master network to form a multi-level blockchain system, so that the above-mentioned small-scale transaction can be implemented on the blockchain subnet.
In the multi-level blockchain system, sometimes two blockchain networks need to interact with each other, which means that each node of one blockchain network needs to acquire a node information list of the other blockchain network so as to interact with a node of the other blockchain network based on the acquired node information list. However, how to make each node in the blockchain network acquire a consistent node information list of another blockchain network as much as possible is an urgent technical problem to be solved.
Disclosure of Invention
In view of the above, one or more embodiments of the present specification provide a method of synchronizing a node information list.
To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:
according to a first aspect of one or more embodiments of the present specification, a method for synchronizing a node information list is provided, which is used for implementing synchronization between nodes of a first blockchain network in a multi-level blockchain system: a list of node information of a second blockchain network employed when interacting with the second blockchain network in the system; the method is applied to each node in the first blockchain network, and comprises the following steps:
acquiring a node information list of the second block chain network; constructing and broadcasting a list designation message for designating the acquired node information list;
judging whether more than N nodes obtain a consistent node information list or not according to the obtained node information list and the received list designated information, wherein N is the minimum value of the number of credible nodes determined by applying a consensus protocol in the first block chain network; if yes, constructing a list synchronous transaction containing the consistent node information list and broadcasting;
synchronizing the consistent list of node information by way of performing a list synchronization transaction.
According to a second aspect of one or more embodiments herein, there is provided a multi-level blockchain system in which synchronization between nodes of a first blockchain network: a list of node information of a second blockchain network employed when interacting with the second blockchain network in the system;
each node in the first block chain network acquires a node information list of the second block chain network; constructing and broadcasting a list designation message for designating the acquired node information list; judging whether more than N nodes obtain a consistent node information list or not according to the obtained node information list and the received list designated information, wherein N is the minimum value of the number of credible nodes determined by applying a consensus protocol in the first block chain network; if yes, constructing a list synchronous transaction containing the consistent node information list and broadcasting; synchronizing the consistent list of node information by way of performing a list synchronization transaction.
In the above technical solution, a data interaction relationship exists between a first blockchain network and a second blockchain network in a multi-level blockchain system, and when a node of the first blockchain network interacts with the second blockchain network, a node information list of the second blockchain network needs to be used. In order to synchronize the nodes of the first blockchain network with the node information list of the second blockchain network, each node of the first blockchain network constructs a list specifying message for specifying the node information list acquired by the node, and broadcasts the list specifying message to the first blockchain network. Each node of the first blockchain network may acquire the list designation message broadcast by each other node, and each node may summarize a situation that each node of the first blockchain network acquires the node information list, and if it is determined that more than N (the minimum value of the number of trusted nodes supported by the consensus protocol for the first blockchain network) nodes acquire a consistent node information list, it may be determined that the consistent node information list is accurate, and a list synchronization transaction including the consistent node information list may be broadcast to the first blockchain network. And each node completes the synchronization of the node information list in a mode of executing the list synchronization transaction.
By the technical scheme, each node of any block chain network in the system can realize synchronization of node information lists of other block networks in the system, and the node information lists adopted by each node of any block chain network are consistent, so that safety risks caused by inconsistent node information lists adopted by each node are avoided.
Drawings
FIG. 1 is a schematic diagram of creating an intelligent contract, provided by an exemplary embodiment.
FIG. 2 is a schematic diagram of a calling smart contract provided by an exemplary embodiment.
FIG. 3 is a schematic diagram of creating and invoking an intelligent contract according to an exemplary embodiment.
Fig. 4 is a flowchart of a method for building a blockchain subnet according to an exemplary embodiment.
Fig. 5 is a schematic diagram of building a blockchain subnet based on a blockchain master network according to an exemplary embodiment.
Fig. 6 is a flowchart of another method for building a blockchain subnet provided by an example embodiment.
Fig. 7 is a flowchart illustrating a method for synchronizing node information lists provided in the present specification.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.
It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Blockchains are generally divided into three types: public chain (Public Blockchain), Private chain (Private Blockchain) and alliance chain (Consortium Blockchain). In addition, there are various types of combinations, such as private chain + federation chain, federation chain + public chain, and other different combinations. The most decentralized of these is the public chain. The public chain is represented by bitcoin and ether house, and the participators joining the public chain can read the data record on the chain, participate in transaction, compete for accounting right of new blocks, and the like. Furthermore, each participant (i.e., node) is free to join and leave the network and perform related operations. Private chains are the opposite, with the network's write rights controlled by an organization or organization and the data read rights specified by the organization. Briefly, a private chain can be a weakly centralized system with strictly limited and few participating nodes. This type of blockchain is more suitable for use within a particular establishment. A federation chain is a block chain between a public chain and a private chain, and "partial decentralization" can be achieved. Each node in a federation chain typically has a physical organization or organization corresponding to it; participants jointly maintain blockchain operation by authorizing to join the network and forming a benefit-related alliance.
Whether public, private, or alliance, may provide the functionality of an intelligent contract. An intelligent contract on a blockchain is a contract that can be executed on a blockchain system triggered by a transaction. An intelligent contract may be defined in the form of code.
Taking the ethernet as an example, the support user creates and invokes some complex logic in the ethernet network, which is the biggest challenge of ethernet to distinguish from bitcoin blockchain technology. The core of the ethernet plant as a programmable blockchain is the ethernet plant virtual machine (EVM), each ethernet plant node can run the EVM. The EVM is a well-behaved virtual machine, which means that a variety of complex logic can be implemented through it. The user issuing and invoking smart contracts in the etherhouse is running on the EVM. In fact, what the virtual machine directly runs is virtual machine code (virtual machine bytecode, hereinafter referred to as "bytecode"). The intelligent contracts deployed on the blockchain may be in the form of bytecodes.
For example, as shown in fig. 1, after Bob sends a transaction containing information to create an intelligent contract to the ethernet network, the EVM of node 1 may execute the transaction and generate a corresponding contract instance. The "0 x6f8ae93 …" in fig. 1 represents the address of the contract, the data field of the transaction holds the byte code, and the to field of the transaction is empty. After agreement is reached between the nodes through the consensus mechanism, this contract is successfully created and can be invoked in subsequent procedures. After the contract is created, a contract account corresponding to the intelligent contract appears on the blockchain and has a specific address, and the contract code is stored in the contract account. The behavior of the intelligent contract is controlled by the contract code. In other words, an intelligent contract causes a virtual account to be generated on a blockchain that contains a contract code and an account store (Storage).
As shown in fig. 2, still taking an ethernet house as an example, after Bob sends a transaction for invoking an intelligent contract to the ethernet house network, the EVM of a certain node may execute the transaction and generate a corresponding contract instance. The from field of the transaction in FIG. 2 is the address of the account of the initiator of the transaction (i.e., Bob), the "0 x6f8ae93 …" in the to field represents the address of the smart contract being invoked, the value field is the value in EtherFang that is the value in Tai currency, and the data field of the transaction holds the methods and parameters for invoking the smart contract. After invoking the smart contract, the value of balance may change. Subsequently, a client can view the current value of balance through a blockchain node (e.g., node 6 in fig. 2). The intelligent contract is independently executed at each node in the blockchain network in a specified mode, and all execution records and data are stored on the blockchain, so that after the transaction is completed, transaction certificates which cannot be tampered and cannot be lost are stored on the blockchain.
A schematic diagram of creating an intelligent contract and invoking the intelligent contract is shown in fig. 3. To create an intelligent contract in an ethernet workshop, the intelligent contract needs to be compiled, compiled into byte codes, deployed to a block chain and the like. The intelligent contract is called in the Ethernet workshop, a transaction pointing to the intelligent contract address is initiated, and the intelligent contract codes are distributed and run in the virtual machine of each node in the Ethernet workshop network.
It should be noted that, in addition to the creation of the smart contracts by the users, the smart contracts may also be set by the system in the creation block. Such contracts are generally referred to as foundational contracts. In general, the data structure, parameters, attributes and methods of some blockchain networks may be set in the startup contract. Further, an account with system administrator privileges may create a contract at the system level, or modify a contract at the system level (simply referred to as a system contract). In addition to EVM in the ethernet, different blockchain networks may employ various virtual machines, which is not limited herein.
After executing a transaction that invokes a smart contract, a node in the blockchain network generates a corresponding receipt (receipt) for recording information related to executing the smart contract. In this way, information about the contract execution results may be obtained by querying the receipt of the transaction. The contract execution result may be represented as an event (event) in the receipt. The message mechanism can realize message passing through an event in a receipt so as to trigger the blockchain node or a node device deploying the blockchain node to execute corresponding processing. The structure of the event may be, for example:
Event：
[topic][data]
[topic][data]
......
in the above example, the number of events may be one or more; wherein, each event respectively comprises fields of a subject (topic) and data (data). The blockchain node or the node device deploying the blockchain node may perform the preset processing by monitoring the topic of the event, in case that the predefined topic is monitored, or read the related content from the data field of the corresponding event, and may perform the preset processing based on the read content.
In the event mechanism, it is equivalent to that there is a client with a monitoring function at a monitoring party (e.g. a user with a monitoring requirement), for example, an SDK or the like for implementing the monitoring function is run on the client, and the client monitors events generated by the blockchain node, and the blockchain node only needs to generate a receipt normally. The passage of transaction information may be accomplished in other ways than through the event mechanism described above. For example, the monitoring code can be embedded in a blockchain platform code running at blockchain nodes, so that the monitoring code can monitor one or more data of transaction content of blockchain transactions, contract states of intelligent contracts, receipts generated by contracts and the like, and send the monitored data to a predefined monitoring party. Since the snoop code is deployed in the blockchain platform code, rather than at the snooper's client, this implementation based on snoop code is relatively more proactive than the event mechanism. The above monitoring code may be added by a developer of the blockchain platform in the development process, or may be embedded by the monitoring party based on the own requirement, which is not limited in this specification.
The blockchain technology is different from the traditional technology in one of decentralization characteristics, namely accounting is performed on each node, or distributed accounting is performed, and the traditional centralized accounting is not performed. To be a difficult-to-defeat, open, non-falsifiable data record decentralized honest and trusted system, the blockchain system needs to be secure, unambiguous, and irreversible in the shortest possible time for distributed data records. In different types of blockchain networks, in order to keep the ledger consistent among the nodes recording the ledger, a consensus algorithm is generally adopted to ensure that the consensus mechanism is the aforementioned mechanism. For example, a common mechanism of block granularity can be implemented between block nodes, such as after a node (e.g., a unique node) generates a block, if the generated block is recognized by other nodes, other nodes record the same block. For another example, a common mechanism of transaction granularity may be implemented between the blockchain nodes, such as after a node (e.g., a unique node) acquires a blockchain transaction, if the blockchain transaction is approved by other nodes, each node that approves the blockchain transaction may add the blockchain transaction to the latest block maintained by itself, and finally, each node may be ensured to generate the same latest block. The consensus mechanism is a mechanism for the blockchain node to achieve a global consensus on the block information (or called blockdata), which can ensure that the latest block is accurately added to the blockchain. The current mainstream consensus mechanisms include: proof of Work (POW), Proof of stock (POS), Proof of commission rights (DPOS), Practical Byzantine Fault Tolerance (PBFT) algorithm, HoneyBadgerBFT algorithm, etc.
A hardware-level blockchain network is generally composed of a plurality of member node devices. The node equipment of each member is provided with nodes, and the nodes arranged on the node equipment of each member form a software-level block chain network.
It is to be understood that different members are different individuals or entities and actually correspond to different interested parties. There may be multiple node devices (i.e., device clusters) for a member, and the member may flexibly (e.g., considering the performance of a single device) deploy in the device cluster several nodes belonging to different blockchain networks through which transactions in the different blockchain networks are engaged.
A node is a concept of a software layer, and one node can be understood as one instance (one process or one thread) of code for realizing the functions of the node, so that a plurality of instances for realizing the functions of the node can be deployed on a node device corresponding to the same member. In the case of a federated link network, the controller of a node is a federation member (enterprise) and the controller of a client is a user to which the enterprise interfaces, so that the multiple nodes can communicate with the client through different ports (or the same default port) of the node device to receive transactions submitted by the client.
In the case of a public link network, the node is included in the client, and the controller of the node is the controller of the client, i.e., the user.
Herein, for convenience of description, the "node receives a transaction submitted by a client" may refer to both the case of a federation chain network and the case of a public chain network.
Due to the decentralized characteristic of the blockchain network, all blockchain nodes in the blockchain network can maintain the same blockchain data, and the special requirements of part of nodes cannot be met. Taking an existing alliance chain network as an example, nodes of the alliance chain network are deployed on node devices of all alliance members (i.e., node members in an alliance), a blockchain network can be formed, that is, all alliance members respectively have corresponding blockchain nodes in the blockchain network, and all transactions and related data occurring on the blockchain network can be obtained through the corresponding blockchain nodes. In some cases, however, there may be some federations who wish to perform some transactions with privacy requirements within a small range, and who wish to be able to both verify such transactions on the blockchain or to take advantage of other advantages of blockchain technology, and to avoid other federations viewing such transactions and associated data.
To this end, the embodiments of the present specification provide a blockchain system participated by a plurality of members, the system includes, on a hardware level, a node device of each member, at least one node is deployed on the node device of each member, and different nodes deployed on the node device of the same member belong to different blockchain networks. Meanwhile, the system has a tree structure in a software layer, wherein the tree structure takes the block chain main network as a root node and each block chain sub network as other nodes.
It should be noted that the nodes and nodes described herein are different concepts. A node is a concept in the sense of a blockchain, and refers to a node in a blockchain network; and a node is a concept in a tree structure, and refers herein to a blockchain network in the tree structure.
The blockchain master network can be regarded as the blockchain network at the uppermost level in the system, and generally consists of master network nodes deployed on node devices of all members of the system. It should be noted that in some embodiments, a member may be assigned a score of an initial member (a member participating in initializing the system) and a subsequent member (a member joining after system initialization). All initial members construct a blockchain system, a blockchain main network in the system is composed of main network nodes deployed on node devices of all initial members, and then more subsequent members can join the blockchain system, and main network nodes can be deployed on the node devices of the subsequent members so as to join the main network, or only one or more sub-network nodes can be deployed without deploying the main network nodes.
The blockchain subnet in the system may have multiple levels. The block chain sub-network at the top level is a sub-node of the block chain main network in the tree structure. The blockchain sub-network can also have sub-nodes of the next-level blockchain sub-network. It should be noted that, in general, a master network node of a block chain master network is also deployed on a node device corresponding to a node of a block chain sub-network. In the embodiment where there is a difference between the initial member and the subsequent member in the system, the node device corresponding to the node of one blockchain subnet may be the node device of the subsequent member, and the node device of the subsequent member may not deploy the main network node.
By means of the blockchain system, individual members can self-establish a blockchain sub-network to conduct small-range transactions, and the blockchain networks (whether main networks or sub-networks) in the system are mutually isolated in data.
In some embodiments, the blockchain network may be created by manually deploying on its own node device by each member, and if 3 nodes of different blockchain networks (one main network and two subnets) need to be deployed on the node device of one member, the member needs to perform a process of manually deploying the blockchain network on the node device three times. However, for the member, each time a node of a new blockchain network needs to be additionally deployed on its own node device, the member needs to perform the manual deployment procedure again, which is troublesome. Moreover, the small-scale transaction requirements among some members are often temporary or have certain timeliness, so that the manually deployed new blockchain subnet can lose significance quickly due to the disappearance of the requirements, and the cancellation of the blockchain subnet requires the members to manually operate the node equipment, which further increases the trouble.
To this end, in some embodiments, another method of creating a blockchain network in a system is presented. And taking the block chain main network initially established in the system as a base, and establishing a block chain sub-network on the basis of the block chain main network.
Specifically, a blockchain main network accepts a subnet creation transaction, processes the subnet creation transaction based on a deployed contract, triggers a subnet creation event, and creates an instance as a node of a created subnet according to configuration information carried by the subnet creation transaction if each main network node determines that a member of a node device corresponding to the main network node participates in the subnet after monitoring the subnet creation event. Each blockchain subnet can also further accept subnet creation transactions and process the subnet creation transactions based on deployed contracts, and trigger subnet creation events, after each subnet node in the blockchain subnet monitors the subnet creation events from the subnet node, if it is determined that members of the node device corresponding to the blockchain subnet node participate in the next-level subnet, an instance is created according to configuration information carried by the subnet creation transactions, and the instance is used as a node of the further-created next-level subnet.
In this context, for any blockchain subnet, if the blockchain network responsible for processing the subnet creation transaction used to create the blockchain subnet, i.e., the blockchain network referred to as creating the blockchain subnet, is the parent node of the blockchain subnet in the tree structure. In the tree structure, the blockchain subnet of the child node of the parent node is not necessarily created by the parent node, but may still be managed by the parent node (i.e., the network identifier and address information of the blockchain subnet of the child node are recorded in the blockchain network of the parent node).
In these embodiments, any blockchain subnet is created and managed by the blockchain network corresponding to its parent node. In this way, the member usually only needs to complete one manual deployment of the master network node on its own node device, and the master network node on the node devices of the subsequent members can create a new instance as the next-level sub-network node. The node of a block chain sub-network on the node devices of some members can further create a new instance as a sub-network node of a lower level. Through the hierarchical network deployment mode, the trouble of manual deployment of members can be reduced.
In addition, in these embodiments, node devices of some subsequent members may still be added to the system after the blockchain sub-network is deployed, which means that the blockchain sub-network is not created by any original blockchain network in the system, but is directly added to the blockchain sub-network in the system from the outside, and such blockchain sub-network may still be added to the tree structure to become a node, except that the blockchain sub-network of the node is managed (not created) by the blockchain network corresponding to its parent node.
Through the above subnet creating and managing manner, any blockchain subnet is either created and managed by the blockchain network of the parent node, or is directly added into the tree structure from the outside and managed by the blockchain network of the parent node. In either case, the address information of any blockchain subnet (i.e. the address information of each node contained therein, such as IP address and port number) can be exposed only to the blockchain network of its parent node, and recorded by each node in the blockchain network of its parent node. Therefore, the privacy of the subnet can be ensured to the maximum extent, and the risk of network attack is reduced.
The building scheme of the block chain sub-network in this specification is described below with reference to fig. 4. It should be noted that, the node member in the following description specifically refers to a member; the node equipment refers to equipment controlled by members and is a concept of a hardware level; a node refers to a node instance (a process or a thread running on a node device), is deployed on the node device, and is a concept of a software layer.
Referring to fig. 4, fig. 4 is a flowchart of a method for building a blockchain subnet according to an exemplary embodiment. As shown in fig. 4, the method may include the steps of:
step 402, each block link point in a block link main network respectively acquires a transaction for building a block link sub-network, wherein the transaction includes configuration information of the block link sub-network, and the configuration information includes identity information of node members participating in building the block link sub-network.
The transaction for establishing the blockchain sub-network can be initiated by an administrator of the blockchain main network, that is, the administrator is only allowed to establish the blockchain sub-network on the basis of the blockchain main network, and the establishment permission of the blockchain sub-network is prevented from being opened to a common user, so that the security problem caused by the establishment permission can be prevented. In some cases, a common user of the blockchain main network may also be allowed to initiate a transaction for building the blockchain sub-network, so as to meet networking requirements of the common user, and the common user can still quickly build the blockchain sub-network under the condition that an administrator is not convenient to initiate the transaction.
For example, as shown in fig. 5, the main network of the blockchain is subnet0, and the subnet0 includes blockchain link points nodeA, nodeB, nodeC, nodeD, and nodeE. Suppose that the node members respectively corresponding to nodeA, nodeB, nodeC and nodeD wish to construct a blockchain subnet: if nodeA is an administrator and only allows the administrator to initiate a transaction to build a blockchain subnet, the transaction to build the blockchain subnet can be initiated by nodeA to subnet 0; if the nodeb is an administrator and only the administrator is allowed to initiate a transaction for building the blockchain subnet, nodeb a to nodeb d need to make a request to nodeb, so that nodeb initiates the transaction for building the blockchain subnet to subnet 0; if the node E is an administrator but allows a common user to initiate the transaction of building the blockchain sub-network, the node A-node E can initiate the transaction of building the blockchain sub-network to the subnet 0. Of course, no matter an administrator or an ordinary user, the node members corresponding to the blockchain link points initiating the transaction for building the blockchain subnet do not necessarily participate in the built blockchain subnet, for example, although the blockchain subnet is finally built by the node members respectively corresponding to nodeA, nodeB, nodeC and nodeD, the transaction for building the blockchain subnet may be initiated to subnet0 by nodeE, but the transaction for building the blockchain subnet is not necessarily initiated by nodeA to nodeD.
When the blockchain sub-network is constructed on the basis of the blockchain main network, it is easy to understand that a logical hierarchical relationship exists between the blockchain sub-network and the blockchain main network. For example, when a blockchain subnet1 is constructed on subnet0 shown in fig. 5, subnet0 may be considered to be at the first level and subnet1 may be considered to be at the second level. In one case, the blockchain main network in this specification may be an underlying blockchain network, that is, the blockchain main network is not a blockchain sub-network constructed on the basis of other blockchain networks, for example, the subnet0 in fig. 5 may be regarded as a blockchain main network belonging to the underlying blockchain network type. In another case, the blockchain master network in this specification may be a sub-network of another blockchain network, for example, another blockchain sub-network may be further configured on the basis of the subnet1 in fig. 5, and at this time, the subnet1 may be considered as the blockchain master network corresponding to the blockchain sub-network, and this does not affect that the subnet1 belongs to the blockchain sub-network created on the subnet0 at the same time. It can be seen that the blockchain main network and the blockchain sub-network are actually relative concepts, and the same blockchain network may be the blockchain main network in some cases and the blockchain sub-network in other cases.
In step 404, each block link node in the block chain master network performs the transaction to reveal the configuration information.
Step 406, when the configuration information includes identity information of a node member corresponding to the first block link point, the node device deploying the first block link node starts a second block link node belonging to the block link subnet based on the creation block including the configuration information.
After the transaction for establishing the blockchain sub-network is sent to the blockchain main network, the consensus nodes in the blockchain main network perform consensus, and after the consensus is passed, the transaction is executed by each blockchain link point, so that the establishment of the blockchain sub-network is completed. The consensus process depends on the consensus mechanism employed, such as any of the consensus mechanisms described above, and is not limited by the present specification.
The configuration information is included in the transaction of the block chain sub-network, and the configuration information can be used for configuring the block chain sub-network, so that the block chain sub-network meets networking requirements. For example, by including identity information of the node members participating in the building of the blockchain subnet in the configuration information, it can be specified to which node members the built blockchain subnet corresponds.
The identity information of the node member may include a public key, or other information capable of representing the identity of the node member, such as a node ID, which is not limited in this specification. Taking a public key as an example, each block chain node has one or more corresponding public and private key pairs, and the block chain node holds the private key and the public key is public and uniquely corresponds to the private key, so that the identity of the corresponding block chain node can be represented by the public key, and the identity of a node member corresponding to the block chain node can also be represented by the public key. Therefore, for the node members who wish to participate in building the blockchain sub-network, the public keys of the blockchain nodes corresponding to the node members on the blockchain main network can be added to the transaction of building the blockchain sub-network to serve as the identity information of the node members. The public and private key pair described above may be used in the process of signature verification. For example, in a signed consensus algorithm, such as the sub net1, the above-mentioned nodeA1 signs a message with its own private key, and broadcasts the signed message in the sub net1, while nodeB1, nodeC1 and nodeD1 can verify that the received message is signed with the public key of nodeA1 to confirm that the received message is indeed from nodeA1 and has not been tampered with.
The first block link point may be a block link point on the block chain backbone corresponding to a node member indicated by the configuration information. When building the block chain sub-network, the first block chain link point does not directly participate in building the block chain sub-network, but the node device for deploying the first block chain node needs to generate a second block chain node, and the second block chain link point participates in building the block chain sub-network. The first block chain node and the second block chain node correspond to the same node member, for example, correspond to the same alliance chain member in an alliance chain scene, but the first block chain node belongs to a block chain main network, and the second block chain node belongs to a block chain sub-network, so that the node member can participate in the transactions of the block chain main network and the block chain sub-network respectively; moreover, because the blockchain main network and the blockchain sub-network belong to two mutually independent blockchain networks, the block generated by the first blockchain link point and the block generated by the second blockchain link point are respectively stored in different storages (the adopted storages can be databases, for example) on the node device, so that mutual isolation between the storages used by the first blockchain link point and the second blockchain link point is realized, data generated by the blockchain sub-network can only be synchronized among the blockchain nodes in the blockchain sub-network, so that the node members only participating in the blockchain main network can not obtain the data generated on the blockchain sub-network, data isolation between the blockchain main network and the blockchain sub-network is realized, and the transaction requirements between partial node members (namely, the node members participating in the blockchain sub-network) are met.
The first blockchain node and the second blockchain node are logically divided blockchain link points, and from the perspective of physical devices, the node device which is equivalent to the first blockchain node and the second blockchain node is deployed to participate in both the blockchain main network and the blockchain sub-network. Since the identity systems of the two blockchain networks are independent from each other due to the independence between the blockchain main network and the blockchain sub-network, even though the first blockchain node and the second blockchain node may use the same public key, they should be regarded as different blockchain nodes. For example, in fig. 5, the nodeA in subnet0 corresponds to a first blockchain node, and the node device deploying the nodeA generates nodeA1 belonging to subnet1, and the nodeA1 corresponds to a second blockchain node. It can be seen that, because the identity systems are independent of each other, even if the public key adopted by the second blockchain node is different from the first blockchain node, the implementation of the scheme in this specification is not affected.
Of course, the node members participating in the blockchain sub-network are not necessarily only a part of the node members participating in the blockchain main network. In some cases, the node members participating in the blockchain subnet may be completely consistent with the node members participating in the blockchain main network, and at this time, all the node members may obtain data on the blockchain main network and the blockchain subnet, but data generated by the blockchain main network and the blockchain subnet may still be isolated from each other, for example, one type of service may be implemented on the blockchain main network, and another type of service may be implemented on the blockchain subnet, so that service data generated by the two types of services may be isolated from each other.
In addition to the identity information of the node members described above, the configuration information may include at least one of: the network identifier of the blockchain subnet, the identity information of an administrator of the blockchain subnet, the attribute configuration for the blockchain platform code, and the like, which are not limited in this specification. The network identifier is used to uniquely characterize the blockchain subnet, and thus the network identifier of the blockchain subnet should be distinguished from the blockchain main network and other blockchain subnets established on the blockchain main network. Identity information of an administrator of the blockchain subnet, such as a public key of a node member as the administrator; the administrators of the blockchain main network and the blockchain sub-network may be the same or different.
One of the advantages of building the block chain sub-network by the block chain main network is that since the first block chain node is already deployed on the node device generating the second block chain node, the block chain platform code used by the first block chain node can be multiplexed on the second block chain node, so that repeated deployment of the block chain platform code is avoided, and the building efficiency of the block chain sub-network is greatly improved. Then, if the configuration information does not include the attribute configuration for the blockchain platform code, the second blockchain link point may reuse the attribute configuration adopted on the first blockchain node; if the configuration information includes the attribute configuration for the blockchain platform code, the second blockchain link point may adopt the attribute configuration, so that the attribute configuration adopted by the second blockchain node is not limited to the attribute configuration of the first blockchain node and is independent of the first blockchain link point. The attribute configuration for blockchain platform code may include at least one of: code version number, whether consensus is required, type of consensus algorithm, block size, etc., which is not limited in this specification.
The transactions that make up the blockchain subnet include transactions that invoke contracts. The address of the invoked smart contract, the method invoked and the incoming parameters may be specified in the transaction. For example, the contract invoked may be the aforementioned startup contract or system contract, the method invoked may be a method that builds a blockchain subnet, and the incoming parameters may include the configuration information described above. In one embodiment, the transaction may contain the following information:
from：Administrator
to：Subnet
method：AddSubnet(string)
string：genesis
the from field is information of the initiator of the transaction, such as administeror indicating that the initiator is an Administrator; the to field is the address of the intelligent contract being called, for example, the intelligent contract may be a Subnet contract, and the to field is specifically the address of the Subnet contract; the method field is a called method, for example, the method used in the Subnet contract to build the blockchain Subnet may be AddSubnet (string), and string is a parameter in the AddSubnet () method, and the value of the parameter is represented by the aforementioned example, which is specifically the aforementioned configuration information.
Take the example that nodes nodeA-nodeS on Subnet0 execute a transaction that invokes the AddSubnet () method in the Subnet contract. After the transaction passes the consensus, nodeA-nodeE respectively execute the AddSubnet () method and transmit configuration information to obtain corresponding execution results.
The execution result of the contract may include the configuration information, and the execution result may be in the receipt as described above, and the receipt may contain the event related to the execution of the adsubnet () method, i.e., the networking event. The topoc of a networking event may contain a predefined networking event identification to distinguish it from other events. For example, in an event related to the execution of the AddSubnet () method, the content of topic is a keyword subnet, and the keyword is distinguished from topic in the event generated by other methods. Then, the nodeA-nodeE or the node devices 1-5 deploying the nodeA-nodeE can determine to monitor the event related to the execution of the AddSubnet () method, namely the networking event, by monitoring topic contained in each event in the generated receipt and under the condition of monitoring topic containing the keyword subnet. For example, the events in the receipt are as follows:
Event：
[topic:other][data]
[topic:subnet][data]
......
then, when the 1 st event is monitored, the event is determined to be irrelevant to the AddSubnet () method because the contained content of topic is other; and when the 2 nd event is monitored, determining that the event is related to an AddSubnet () method because the contained topic content is subnet, and further reading a data field corresponding to the event, wherein the data field contains the configuration information. Taking the example that the configuration information includes the public key of the node member of the blockchain subnet, the content of the data field may include, for example:
{subnet1；
the public key of nodeA, the IP of nodeA, port number … of nodeA;
public key of nodeB, IP of nodeB, port number … of nodeB;
public key of nodeC, IP of nodeC, port number … of nodeC;
the public key of nodeD, the IP of nodeD, port number … of nodeD;
}
where subnet1 is the network identification of the blockchain subnet that one wishes to create. Each blockchain link point in the blockchain master network may record network identifiers of all blockchain subnets that have been created on the blockchain master network, or other information related to the blockchain subnets, which may be maintained in the Subnet contract, for example, and may specifically correspond to values of one or more contract states included in the Subnet contract. Then, it may be determined whether the subnet1 already exists according to the recorded network identifications of all blockchain subnets that have been created; if not, subnet1 is the new blockchain subnet that needs to be created currently, and if so, subnet1 is already present.
In addition to the network identifier of the new blockchain subnet that is desired to be created, a predefined new network identifier may be used, which indicates that the corresponding networking event is used to create the new blockchain subnet. For example, the subnet1 may be replaced by newsbnet, where newsbnet is a predefined new network identifier, and when the nodeA to nodeE recognize that the data field includes newsbnet, it may be determined that an event including newsbnet is a networking event and a new blockchain subnet needs to be created.
Besides the network identification subnet1, the data field also contains the identity information of each node member participating in building the blockchain subnet. The node device deploying the first blockchain node may monitor the generated receipt, and acquire, by the node device deploying the first blockchain node, configuration information or a creation block included in the networking event when the networking event is monitored and the content of the networking event includes identity information of a node member corresponding to the first blockchain node. Or the first block link point may monitor the generated receipt, and trigger the node device deploying the first block link node to acquire the configuration information or the created block included in the networking event when the networking event is monitored and the content of the networking event indicates that the first block link point belongs to the node member.
As previously described, the node device may listen for receipts directly. Assuming that nodeA to nodeE are respectively deployed on the node devices 1 to 5, and the node devices 1 to 5 can monitor receipts respectively generated by the nodeA to nodeE, the node devices 1 to 5 further identify the identity information of the node members included in the data field to determine their own processing modes when it is monitored that the subnet1 is a block chain subnet that needs to be newly built. Take nodeA and node device 1 as an example: if node device 1 finds that the data field contains identity information such as a public key, an IP address, and a port number of nodeA, node device 1 generates a created block containing configuration information when obtaining the configuration information from the data field based on the above-mentioned message mechanism, and node device 1 deploys nodeA1 locally, and nodeA1 loads the generated created block, thereby becoming a subnet node of subnet 1; similarly, node device 2 may generate nodeB1, node device 3 may generate nodeB c1, and node device 4 may generate nodeB 1. And if the node device 5 finds that the identity information included in the data field does not match with itself, the node device 5 does not generate a creation block according to the configuration information in the data field, and does not generate a block link point in subnet 1.
As mentioned above, the blockchain link point in the blockchain master network can listen for the receipt and trigger the node device to perform the relevant processing according to the listening result. For example, when determining that subnet1 is a blockchain subnet that needs to be newly built, nodeA to nodeE further identify the identity information of the node members included in the data field to determine their own processing methods. For example, the nodeA to nodeD may find that the data field includes identity information such as their own public key, IP address, and port number, and assume that nodeA to nodeD are respectively deployed on node devices 1 to 4, taking nodeA and node device 1 as an example: the nodeA triggers the node device 1, so that the node device 1 generates a created block containing the configuration information when obtaining the configuration information from the data field based on the above message mechanism, and the node device 1 deploys the nodeA1 locally, and the nodeA1 loads the generated created block, thereby becoming a subnet node of the subnet 1; similarly, nodeB will trigger NodeB1 to be generated by node device 2, nodeC will trigger NodeC1 to be generated by node device 3, and nodeD will trigger NodeD1 to be generated by node device 4. And the nodeE finds that the identity information contained in the data field is not matched with the nodeE, and if the nodeE is deployed on the node device 5, the node device 5 does not generate a creation block according to the configuration information in the data field, and does not generate a block link point in the subnet 1.
As mentioned above, the first block link point and the second block link point do not necessarily use the same identity information. Therefore, in the above embodiment, the data field may include the identity information previously generated for nodeA 1-nodeD 1, and is different from the identity information of nodeA-nodeD. Taking nodeA and node device 1 as an example: if identity information of nodeA1 is found in the data field, node device 1 may generate a founding block, deploy nodeA1, and load the founding block by nodeA 1; alternatively, nodeA, if identity information of nodeA1 is found in the data field, will trigger node device 1 to generate a foundational block, deploy nodeA1, and load the foundational block by nodeA 1. The processing modes of other blockchain nodes or node devices are similar, and are not described in detail herein.
In addition to configuration information, the execution results of the contract may include a foundational block. In other words, in addition to the configuration information contained in the data field, the created block containing the configuration information may be directly generated in the process of executing the contract call, so that the created block is contained in the data field, and for the nodeA to nodeD described above, the corresponding node devices 1 to 4 may directly obtain the created block from the data field through a message mechanism without self-generation, so that the deployment efficiency of nodeA1 to nodeD1 may be improved.
In this specification, the transaction for creating the blockchain subnet may not be a transaction for calling an intelligent contract, so that the blockchain network that does not support the intelligent contract may also implement the technical solution of this specification, thereby quickly creating the blockchain subnet on the basis of the blockchain main network. For example, a group network transaction type identifier may be predefined, and when a transaction includes the group network transaction type identifier, it indicates that the transaction is used for building a new blockchain subnet, that is, the transaction is a transaction for building a blockchain subnet. The blockchain platform code may include related processing logic for building a blockchain subnet, so that when a first blockchain node running the blockchain platform code executes a transaction, if the transaction is found to include the above networking transaction type identifier and the identity information of a node member corresponding to the first blockchain node is included in the configuration information in the transaction, a node device deploying the first blockchain node may be triggered to generate an innovation block including the configuration information and start a second blockchain node based on the processing logic, and the innovation block is loaded by the second blockchain node to form a blockchain node in the blockchain subnet.
The node equipment realizes the deployment of a blockchain node on the node equipment by creating an instance of a running blockchain platform code in a process. For the first blockchain node, it is formed by the node device creating a first instance of the running blockchain platform code in the above-described process. Similarly, for the second blockchain node, it is formed by the node device creating a second instance of the run blockchain platform code in the above-described process. For example, the node device may first create a first instance in a process to form a first blockchain node in a blockchain master network; when the node member corresponding to the node device wishes to participate in building the blockchain subnet, a second instance may be created in the process, where the second instance is different from the first instance, and forms a second blockchain node in the blockchain subnet. When the first instance and the second instance are located in the same process, the deployment difficulty of the second block chain node can be reduced and the deployment efficiency can be improved because cross-process interaction is not involved. Of course, the second instance may also be in a different process on the node device than the first instance, and this specification does not limit this; for example, the node device may create a first instance in a first process to form a first blockchain node in a blockchain master network; when the node member corresponding to the node device wishes to participate in building the blockchain subnet, a second process different from the first process may be started, and a second instance different from the first instance may be created in the second process, so that the second blockchain node in the blockchain subnet is formed by the second instance.
By the method, the block chain sub-network can be created on the block chain main network. Taking fig. 5 as an example, the subnet0 originally includes nodeA to nodeE, and can construct subnet1 on the basis of subnet0, where subnet1 includes nodeA1 to nodeD1, and nodeA1, nodeB and nodeB1, nodeC and nodeC1, and nodeD1 are respectively disposed on the same node device. Similarly, a subnet2 or more block chain subnets can be constructed on subnet0, where subnet2 includes nodeA2, nodeB2, nodeC2 and nodeE2, and nodeA1, nodeA2, nodeB and nodeB1, nodeB2, nodeC and nodeC1, nodeC2, nodeD and nodeD1, and nodeE2 are respectively deployed on the same node device. And, subnet1, subnet2, etc. may be used as new blockchain main networks, and a blockchain subnet is further constructed on the basis, which is similar to the construction of subnet1 or subnet2, and is not described herein again.
In the above embodiment as shown in fig. 4, the process of building a blockchain subnet in the present specification is actually described from the perspective of the whole blockchain system, and in this process, not all node members participate in the blockchain subnet, and next, in conjunction with fig. 6, the technical solution of the present specification will be described from the perspective of the master node participating in the blockchain subnet and the node device located in the master node. It will be readily appreciated that the embodiment shown in fig. 6 is not substantially different from the embodiment shown in fig. 4, and the foregoing description of the embodiment shown in fig. 4 applies to the embodiment shown in fig. 6.
Fig. 6 is a flowchart of another method for building a blockchain subnet provided by an example embodiment. As shown in fig. 6, the method may include the steps of:
step 602, a first blockchain link point in a blockchain master network obtains a transaction for building a blockchain subnet, where the transaction includes configuration information of the blockchain subnet, and the configuration information includes identity information of node members participating in building the blockchain subnet.
In step 604, the first block node performs the transaction to reveal the configuration information.
Step 606, when the configuration information includes identity information of a node member corresponding to the first block link point, the node device that deploys the first block link node starts a second block link node belonging to the block link subnet based on the creation block including the configuration information.
As previously described, the transactions that make up the blockchain subnet include transactions that invoke contracts.
As previously mentioned, the contracts include either a startup contract or a system contract.
As has been described in the foregoing, the present invention,
the execution result of the contract comprises the configuration information, the node equipment deploying the first block chain node obtains the configuration information through a message mechanism, and the created block is generated according to the obtained configuration information; alternatively, the first and second electrodes may be,
and the execution result of the contract comprises the creation block, and the node equipment for deploying the first block chain node obtains the creation block through a message mechanism.
As mentioned above, the receipt generated after the contract is executed contains networking events related to the establishment of a new blockchain subnet; the node device deploying the first block chain node obtains the configuration information or the creation block through a message mechanism, and the method includes:
monitoring a generated receipt by a first block chain link point, and triggering node equipment for deploying a first block chain node to acquire the configuration information or the created block contained in the networking event under the condition that the networking event is monitored and the content of the networking event indicates that the first block chain link point belongs to the node member; alternatively, the first and second electrodes may be,
and the node equipment deploying the first block chain node monitors the generated receipt, and acquires the configuration information or the created block contained in the networking event under the condition that the networking event is monitored and the content of the networking event indicates that the first block chain link point belongs to the node member.
As previously mentioned, the networking events include: the subject name in the receipt contains the event identified by the predefined networking event.
As mentioned above, when the content of the networking event contains the following identification, it indicates that the networking event is related to the establishment of a new blockchain subnet:
the network identification of the block chain sub-network which is expected to be established is different from the existing block chain sub-network; alternatively, the first and second electrodes may be,
and a predefined new network identifier, wherein the new network identifier indicates that the networking event is used for establishing a new block chain subnet.
As mentioned above, the transaction includes a networking transaction type identifier, which indicates that the transaction is used to construct a new blockchain subnet.
As has been described in the foregoing, the present invention,
the transaction of the building blockchain sub-network is initiated by an administrator of the blockchain main network; alternatively, the first and second electrodes may be,
and the transaction for establishing the blockchain sub-network is initiated by a common user of the blockchain main network.
As mentioned above, the configuration information further includes at least one of: the network identification of the blockchain subnet, the identity information of an administrator of the blockchain subnet, and the attribute configuration aiming at the blockchain platform code.
As previously described, the blockchain master network may be the same or different from the administrator of the blockchain sub-network.
As previously mentioned, the attribute configuration for blockchain platform code includes at least one of: code version number, whether consensus is required, consensus algorithm type, block size.
As previously described, the node device initiating a second block link point comprises: the node device creates a second instance of a run blockchain platform code distinct from the first instance of the first blockchain node on which the blockchain platform code is run.
As described above, the block generated by the first block link point and the block generated by the second block link point are stored in different storages on the node device.
As previously described, the storage used by the first block link point and the second block link point, respectively, are isolated from each other.
As previously mentioned, the storage is a database.
As described above, the block chain master network is a bottom layer block chain network; or, the block chain master network is a subnet of other block chain networks.
In addition, cross-network communication can be carried out between two blockchain networks in the system. Cross-network communication between two blockchain networks in a system is described herein. Assume that cross-network communication is required between a first blockchain network and a second blockchain network in the system. The first blockchain network may send a request message to the second blockchain network and receive a response message returned by the second blockchain network. Similarly, the second blockchain network may also send a request message to the first blockchain network and receive a response message returned by the first blockchain network.
Take the example where the first blockchain network sends a request message to the second blockchain network. Each node in the first blockchain network may send a request message to the second blockchain network during execution of the business process contract. Assuming that the number of nodes in the second blockchain network is Q, each node in the first blockchain network needs to construct Q request messages, and each request message is sent to each node in the second blockchain network.
In the multi-level blockchain system, sometimes two blockchain networks need to interact with each other, which means that each node of one blockchain network needs to acquire a node information list of the other blockchain network so as to interact with a node of the other blockchain network based on the acquired node information list.
Hereinafter, for convenience of description, one of the blockchain networks is referred to as a first blockchain network, and the other blockchain network is referred to as a second blockchain network. It is to be understood that any blockchain network in the system may be a first blockchain network, and any blockchain network in the system having an interaction relationship with the first blockchain network may be a second blockchain network.
The node information list of the second blockchain network records information of each node of the second blockchain network, and the node information may generally include a node identifier, and may also include other information related to the node, such as a node communication address, a node public key, and the like.
When each node of the first blockchain network interacts with each node of the second blockchain network, on one hand, the identifier of each node of the second blockchain network can be inquired based on the node information list of the second blockchain network, so that when a message is sent to each node of the second blockchain network, the node identifier of the node is specified in the message, and the message can be routed to the node; on the other hand, whether the sender of the received message is a node of the second blockchain network may be queried based on the node information list of the second blockchain network.
That is, when the node of the first blockchain network interacts with the second blockchain network, the steps performed may include: and inquiring node identifications of one or more nodes of the second blockchain network based on the local node information list, and constructing a message sent to one or more nodes of the second blockchain network based on the inquired node identifications. Further, the steps performed may also include: and verifying whether the nodes outside the first block network interacting with the nodes belong to the second block chain network or not based on a local node information list.
If the node information lists adopted by the nodes of the first blockchain network are inconsistent, operations of the nodes in the first blockchain network interacting with the second blockchain network are easily inconsistent, and thus a security risk is brought. For example, the node information list of the second blockchain network adopted by the node 1 of the first blockchain network includes the node a, and the node information list adopted by other nodes of the first blockchain network does not include the node a, and in fact, the node a has already exited the second blockchain network before, and only because the node 1 does not acquire the latest node information list of the second blockchain network, the node 1 may send data that can only be sent to the second blockchain network to the node a, thereby causing data leakage and endangering data security.
In order to enable each node in a blockchain network to acquire a consistent node information list of another blockchain network as much as possible, the following technical scheme is proposed:
each node of the first blockchain network synchronizes (which may be understood as a consistency consensus) the respective acquired node information lists of the second blockchain network. Specifically, each node of the first blockchain network constructs a list specification message for specifying a node information list acquired by itself, and broadcasts the list specification message to the first blockchain network. Each node of the first blockchain network may acquire the list designation message broadcast by each other node, and each node may summarize a situation that each node of the first blockchain network acquires the node information list, and if it is determined that more than N (the minimum value of the number of trusted nodes supported by the consensus protocol for the first blockchain network) nodes acquire a consistent node information list, it may be determined that the consistent node information list is accurate, and a list synchronization transaction including the consistent node information list may be broadcast to the first blockchain network. And each node completes the synchronization of the node information list in a mode of executing the list synchronization transaction.
By the technical scheme, each node of any block chain network in the system can realize synchronization of node information lists of other block networks in the system, and the node information lists adopted by each node of any block chain network are consistent, so that safety risks caused by inconsistent node information lists adopted by each node are avoided.
Fig. 7 is a flowchart illustrating a method for synchronizing node information lists provided in this specification, including the following steps:
s700: and acquiring a node information list of the second block chain network.
The method shown in fig. 7 is applied to each node in the first blockchain network. The execution timing of the method shown in fig. 7 can be specified according to actual needs. In some embodiments, the method of fig. 7 may be performed when each node of the first blockchain network performs a transaction consensus (i.e., a block is out).
In addition, considering that the node information of each node of the second blockchain network may be changed from time to time (such as node addition and deletion, and node address change), this means that the node information list of the second blockchain network is updated from time to time. Therefore, in order to make the node information list of the second blockchain network adopted by each node in the first blockchain network as up-to-date as possible, each node in the first blockchain network may execute the method shown in fig. 7 multiple times according to a certain time schedule. For example, the method shown in FIG. 7 may be performed periodically.
In step S700, each node of the first blockchain network generally acquires the node information lists of the second blockchain network, respectively, and since the acquisition routes are not consistent, the node information lists acquired by each node of the first blockchain network are likely to be inconsistent. In addition, even if the paths of acquiring the node information lists by the nodes of the first blockchain network are consistent, there is still a possibility that the node information lists acquired by the nodes of the first blockchain network are inconsistent (for example, some of the node information lists acquired by the nodes lose part of data in the transmission process).
There are various ways in which a node of a first blockchain network obtains a node information list of a second blockchain network. For example, one node of a first blockchain network may obtain a list of node information from one node of a second blockchain network, and a different node of the first blockchain network may obtain a list of node information from a different node of the second blockchain network.
In some embodiments, the second blockchain network is managed by a blockchain network that is a higher level of the second blockchain network in the system. The management here includes at least maintaining a list of node information for the second blockchain network. That is, the previous blockchain network of the second blockchain network may store the node information list of the second blockchain network, and also update the node information list according to the update condition of the node in the second blockchain network. In this way, each node of the first blockchain network respectively obtains the node information list of the second blockchain network from the previous-stage blockchain network of the second blockchain network.
For example, the second blockchain network may be a blockchain subnet, and the higher-level blockchain network of the second blockchain network may be a blockchain master network. The first blockchain network may also be a blockchain subnet, and the node information list of the second blockchain network is obtained from the blockchain master network.
Further, in some embodiments, each node of the first blockchain network obtains a node information list of the second blockchain network from a blockchain network of a higher level of the second blockchain network deployed on the corresponding node device. As described above, the system includes node devices of several members on a hardware level, and nodes of different blockchain networks can be deployed on the node device of the same member, so that the same member can participate in different blockchain networks. In these embodiments, the node device corresponding to each node of the first blockchain network is configured with nodes of a blockchain network at a previous stage of the second blockchain network.
For example, the first blockchain network and the second blockchain network may be two blockchain subnets at the same level, and the blockchain network at the previous level of the two blockchain subnets may be a blockchain master network. The block chain master network manages a first block chain network and a second block chain network, and maintains a node list of the first block chain network and a node information list of the second block chain network. Not only can the first blockchain network obtain the node information list of the second blockchain network from the blockchain master network node of the corresponding node device, but also the second blockchain network can obtain the node information list of the first blockchain network from the blockchain master network node of the corresponding node device.
Although the previous blockchain network of the second blockchain network maintains the node information list of the second blockchain network in response to the change of the system node information of the second blockchain network, the previous blockchain network of the second blockchain network generally updates the node information list by performing the change of the node information into a transaction with respect to the second blockchain network. Each node of the previous-stage blockchain network of the second blockchain network does not necessarily perform the transaction of node information change at the same time, that is, the node information lists of the second blockchain network maintained by each node of the previous-stage blockchain network of the second blockchain network in the same time period are not necessarily consistent. This means that each node of the first blockchain network acquires a node information list from a node of a blockchain network at the previous stage of the second blockchain network deployed on the corresponding node device, and the acquired node information lists may be inconsistent.
S702: a list specifying message for specifying the acquired node information list is constructed and broadcast.
In the method shown in fig. 7, the principle of synchronizing the node information list of the second blockchain network among the nodes of the first blockchain network is that each node can inform other nodes of the first blockchain network of the node information list acquired by itself, so that each node of the first blockchain network can summarize the condition of acquiring the node information list by each node of the first blockchain network.
The list designation message constructed by each node is mainly used for designating the node information list acquired by the node, so that each node can conveniently know the condition of mutually acquiring the node information lists, and the statistical judgment is carried out. In some embodiments, each node-constructed list assignment message may contain a list of self-obtained node information and/or a hash of the list of self-obtained node information.
S704: judging whether more than N nodes acquire a consistent node information list or not according to the acquired node information list and the received list designation information, if so, executing a step S706; if not, go to step S708.
S706: constructing a list synchronization transaction containing the consistent node information list and broadcasting.
S708: no list synchronization transaction is constructed.
S710: synchronizing the consistent list of node information by way of performing a list synchronization transaction.
N is the minimum number of trusted nodes determined by applying the consensus protocol in the first blockchain network. For example, if the consensus protocol is PBFT, N may be 2f +1, the number of nodes of the first blockchain network is 3f +1, and f is the maximum value of the number of fault-tolerant nodes (which may be bad or down) corresponding to the PBFT protocol. For another example, if the consensus protocol is RAFT, N may be f +1, the number of nodes of the first blockchain network is 2f +1, and f is the maximum value of the number of fault-tolerant nodes (which may be down) corresponding to the PBFT protocol.
In addition, the list assignment message constructed by each node may also contain the node identification of the node. In this way, each node can acquire a corresponding node public key according to the node identifier included in each received list designation message to verify the signature of the list designation message, and then the node can determine whether more than N nodes acquire a consistent node information list according to the acquired node information list and each list designation message passing the signature verification. That is, a list-specified message that fails signature verification may default to untrusted, not including statistics.
The existence of more than N nodes acquiring the consistent node information list means that the consistent node information number list is authentic, and therefore the consistent node information list can be synchronized among the nodes of the first blockchain network.
If more than N nodes do not obtain a consistent node information list, the situation shows that all the nodes of the first block chain network cannot commonly identify a credible node information list. In this case, the nodes may notify each other of the reacquisition of the node information list of the second blockchain network, thereby triggering the re-execution of the method shown in fig. 7. Furthermore, the node may not trigger the method shown in fig. 7 to be re-executed.
In step S706, the list synchronization transaction of the node construction may be such that the nodes of the first blockchain network synchronize the consistent list of node information in a manner that the list synchronization transaction is performed. The list synchronization transaction may be stored in the blockchain corresponding to the first blockchain network through execution of the first blockchain network. Each node of the first blockchain network may interact with the second blockchain network based on a list of node information of the second blockchain network that is most recently certified in the blockchain.
Further, in some embodiments, each node of the first blockchain network may invoke a deployed intelligent contract to perform a list synchronization transaction, and after performing the list synchronization transaction, a notification carrying the consistent node information list may be triggered by using an event notification mechanism of the intelligent contract, where the notification may map information on the chain to outside the chain, so that each node of the first blockchain network may synchronize the consistent node information list according to the monitored notification, that is, write the consistent node information list into a local storage outside the chain.
It should be noted that, in practical applications, the interaction between each node of the first blockchain network and each node of the second blockchain network is generally an off-chain interaction, and the interaction message is generally not a data structure of blockchain transaction, so that each node of the first blockchain network uses the node information list of the second blockchain network in the off-chain local storage, which is more efficient.
In some embodiments, when a node constructs a list synchronization transaction, the constructed list synchronization transaction may be signed to indicate its own approval of a consistent list of node information to be synchronized. The list synchronization transaction may include not only the consistent list of node information, but also signatures of at least N-1 list designation messages that designate the consistent list of node information.
In this way, each node may perform the list synchronization transaction when it is determined that the signature of the list synchronization transaction is verified and the signature included in the list synchronization transaction is verified. Thus, each node can synchronize the node information list carried in the list synchronization transaction only when the list to be synchronized in the list synchronization transaction is confirmed by at least N nodes.
Furthermore, in the method shown in fig. 7, it may happen that more than one node of the first blockchain network constructs a list synchronization transaction and broadcasts it. In view of the fact that the list synchronization transaction is redundant in this case, in some embodiments, each node may be configured to construct the list synchronization transaction only when determining that the list synchronization transaction broadcasted by another node is not received even though it determines that the trusted node information list exists, and if determining that the list synchronization transaction broadcasted by another node is received, the list synchronization transaction does not need to be constructed again.
In addition, each node of the first blockchain network can be set to synchronize the consistent node information list in a way of executing the acquired first list synchronization transaction. Each node of the first blockchain network may discard the acquired non-first list synchronization transaction, or make the execution result of the acquired non-first list synchronization transaction a failure, thereby avoiding a situation that the list synchronization transaction is repeatedly executed.
In addition, the present specification also provides a multi-level blockchain system, in which synchronization between nodes of a first blockchain network: a list of node information of a second blockchain network employed when interacting with the second blockchain network in the system;
each node in the first block chain network acquires a node information list of the second block chain network; constructing and broadcasting a list designation message for designating the acquired node information list; judging whether more than N nodes obtain a consistent node information list or not according to the obtained node information list and the received list designated information, wherein N is the minimum value of the number of credible nodes determined by applying a consensus protocol in the first block chain network; if yes, constructing a list synchronous transaction containing the consistent node information list and broadcasting; synchronizing the consistent list of node information by way of performing a list synchronization transaction.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims (16)

1. A method for synchronizing node information lists is used for realizing synchronization among nodes of a first block chain network in a multi-stage block chain system: a list of node information of a second blockchain network employed when interacting with the second blockchain network in the system; the method is applied to each node in the first blockchain network, and comprises the following steps:
acquiring a node information list of the second block chain network; constructing and broadcasting a list designation message for designating the acquired node information list;
judging whether more than N nodes obtain a consistent node information list or not according to the obtained node information list and the received list designated information, wherein N is the minimum value of the number of credible nodes determined by applying a consensus protocol in the first block chain network; if yes, constructing a list synchronous transaction containing the consistent node information list and broadcasting;
synchronizing the consistent list of node information by way of performing a list synchronization transaction.
2. The method of claim 1, wherein the nodes of the first blockchain network interact with the second blockchain network, and wherein the steps performed comprise: and inquiring node identifications of one or more nodes of the second blockchain network based on the local node information list, and constructing a message sent to one or more nodes of the second blockchain network based on the inquired node identifications.
3. The method of claim 1, wherein the nodes of the first blockchain network interact with the second blockchain network, and wherein the steps performed comprise: and verifying whether the nodes outside the first block network interacting with the nodes belong to the second block chain network or not based on a local node information list.
4. The method of claim 1, wherein the second blockchain network is managed by a higher level blockchain network of the second blockchain network in the system; the managing at least comprises: maintaining a list of node information for the second blockchain network;
each node of the first blockchain network acquires a node information list of the second blockchain network, and the method comprises the following steps:
and each node of the first block chain network respectively acquires a node information list of the second block chain network from the upper-level block chain network of the second block chain network.
5. The method according to claim 4, wherein each node of the first blockchain network respectively obtains a node information list of the second blockchain network from a blockchain network at a higher level of the second blockchain network, and the obtaining comprises:
each node of the first blockchain network acquires a node information list of the second blockchain network from a higher-level blockchain network of the second blockchain network deployed on corresponding node equipment.
6. The method of claim 4 or 5, performed periodically.
7. The method of claim 1, further comprising:
if the judgment result is negative, the list synchronous transaction is not constructed.
8. The method of claim 1, wherein each node performs a list synchronization transaction comprising:
each node calls an intelligent contract execution list to perform synchronous transaction, and triggers a notice carrying the consistent node information list;
each node synchronizes the consistent list of node information, including:
each node synchronizes the consistent list of node information according to the monitored notification.
9. The method according to claim 1, wherein the list assignment message constructed by each node comprises the acquired list of node information and/or comprises a hash value of the acquired list of node information.
10. The method of claim 1, wherein the list assignment message constructed by each node includes a node identification for the node;
judging whether more than N nodes acquire a consistent node information list or not according to the acquired node information list and the received list designation information, wherein the judging step comprises the following steps:
aiming at each received list designation message, acquiring a corresponding node public key according to a node identifier contained in the list designation message to verify the signature of the list designation message;
and judging whether more than N nodes acquire a consistent node information list or not according to the acquired node information list and each list designated message passing signature verification.
11. The method of claim 10, constructing a list synchronization transaction containing the consistent list of node information, comprising:
constructing a list synchronous transaction, and signing the constructed list synchronous transaction;
wherein the constructed list-synchronized transaction contains the consistent list of node information and signatures of at least N-1 list-specifying messages that specify the consistent list of node information.
12. The method of claim 11, performing a list synchronization transaction, comprising:
in the event that it is determined that the signature of the list synchronization transaction is verified, and the signature included in the list synchronization transaction is verified, the list synchronization transaction is performed.
13. The method of claim 1, if so, constructing a list synchronization transaction comprising:
if yes, under the condition that the list synchronous transaction broadcasted by other nodes is not received, the list synchronous transaction is constructed;
the method further comprises the following steps:
if yes, the list synchronization transaction is not constructed under the condition that the list synchronization transaction broadcasted by other nodes is determined to be received.
14. The method of claim 1, synchronizing the consistent list of node information by performing a list synchronization transaction, comprising:
synchronizing the consistent node information list in a mode of executing the obtained first list synchronous transaction;
the method further comprises the following steps:
discarding the obtained non-first list synchronous transaction; or the acquired execution result of the non-first list synchronous transaction is failed.
15. The method of claim 1, wherein the first blockchain network and the second blockchain network are blockchain subnets managed by the same higher-level blockchain network.
16. A multi-level blockchain system in which synchronization between nodes of a first blockchain network: a list of node information of a second blockchain network employed when interacting with the second blockchain network in the system;
each node in the first block chain network acquires a node information list of the second block chain network; constructing and broadcasting a list designation message for designating the acquired node information list; judging whether more than N nodes obtain a consistent node information list or not according to the obtained node information list and the received list designated information, wherein N is the minimum value of the number of credible nodes determined by applying a consensus protocol in the first block chain network; if yes, constructing a list synchronous transaction containing the consistent node information list and broadcasting; synchronizing the consistent list of node information by way of performing a list synchronization transaction.
CN202110611531.4A 2021-06-02 2021-06-02 Method for synchronizing node information lists Active CN113259117B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110611531.4A CN113259117B (en) 2021-06-02 2021-06-02 Method for synchronizing node information lists

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110611531.4A CN113259117B (en) 2021-06-02 2021-06-02 Method for synchronizing node information lists

Publications (2)

Publication Number Publication Date
CN113259117A true CN113259117A (en) 2021-08-13
CN113259117B CN113259117B (en) 2021-09-24

Family

ID=77185790

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110611531.4A Active CN113259117B (en) 2021-06-02 2021-06-02 Method for synchronizing node information lists

Country Status (1)

Country Link
CN (1) CN113259117B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114338724A (en) * 2021-12-31 2022-04-12 支付宝(杭州)信息技术有限公司 Block synchronization method and device, electronic equipment and storage medium
WO2023207076A1 (en) * 2022-04-29 2023-11-02 蚂蚁区块链科技(上海)有限公司 Method and apparatus for establishing blockchain subnet

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108200210A (en) * 2018-02-12 2018-06-22 众安信息技术服务有限公司 The method, apparatus and computer-readable medium of chain management based on block chain
CN110033371A (en) * 2019-02-19 2019-07-19 阿里巴巴集团控股有限公司 A kind of account checking method and device based on transaction in assets
CN111414210A (en) * 2020-03-25 2020-07-14 北京创世智链信息技术研究院 Method and device for generating side chain based on main chain and computer readable storage medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108200210A (en) * 2018-02-12 2018-06-22 众安信息技术服务有限公司 The method, apparatus and computer-readable medium of chain management based on block chain
CN110033371A (en) * 2019-02-19 2019-07-19 阿里巴巴集团控股有限公司 A kind of account checking method and device based on transaction in assets
CN111414210A (en) * 2020-03-25 2020-07-14 北京创世智链信息技术研究院 Method and device for generating side chain based on main chain and computer readable storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114338724A (en) * 2021-12-31 2022-04-12 支付宝(杭州)信息技术有限公司 Block synchronization method and device, electronic equipment and storage medium
WO2023207076A1 (en) * 2022-04-29 2023-11-02 蚂蚁区块链科技(上海)有限公司 Method and apparatus for establishing blockchain subnet

Also Published As

Publication number Publication date
CN113259117B (en) 2021-09-24

Similar Documents

Publication Publication Date Title
CN113067904B (en) Method for building block chain sub-network and block chain system
CN113067894B (en) Method for node to exit block chain sub-network
CN113067902B (en) Block chain message transmission method and device
CN113067895B (en) Method for building block chain sub-network and block chain system
CN113067901B (en) Method for creating block chain subnet
CN113098982B (en) Block chain message transmission method and device
CN113259117B (en) Method for synchronizing node information lists
CN113259118B (en) Method for synchronizing node information lists
CN113259120B (en) Method for synchronizing node information lists
CN113326290B (en) Cross-network query control method
CN113055190B (en) Access control method for client
CN113067896B (en) Method for adding node in block chain sub-network and block chain system
CN113259457B (en) Information synchronization method and device for block chain sub-network
CN113259461B (en) Cross-chain interaction method and block chain system
CN113886495A (en) Method and device for verifying block chain data, electronic equipment and storage medium
CN113259236B (en) Transaction forwarding method between block chain networks
CN113259237B (en) Transaction forwarding method between block chain networks
CN113067774B (en) Transaction forwarding method between block chain networks
CN113067772B (en) Transaction forwarding method between block chain networks
CN113259459B (en) Block chain subnet operation state control method and block chain system
CN113259466B (en) Block chain subnet operation state control method and block chain system
CN113259463B (en) Cross-chain interaction method and block chain system
CN114363162A (en) Block chain log generation method and device, electronic equipment and storage medium
CN115086338A (en) Block chain subnet building method and device
CN113098984B (en) Method for forming multi-layer block chain system based on registration mechanism and block chain system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant