TWI629883B - Node list maintenance system based on blockchain and method thereof - Google Patents

Abstract

A blockchain-based node list maintenance system and method thereof, storing a node list in a blockchain through a smart contract, and using a preset static node list and a blockchain network before the node joins the blockchain network Linking, after the node joins the blockchain network, continuously reads the list of nodes in the blockchain according to the contract address, and stores the contents of the node list to the list array to link all the nodes according to the node identifier of the list array, and Maintain the connection between each node to improve the technical convenience of the node's expansion convenience in the Permissioned blockchain environment.

Description

Node list maintenance system based on blockchain and method thereof

The invention relates to a maintenance system and a method thereof, in particular, in a blockchain environment of a privileged system, a blockchain storage node list is used, so that a node connects all nodes according to a node list to maintain a connection between each node. A block-based node list maintenance system and method thereof for a line.

In recent years, with the popularization and vigorous development of blockchain technology, various blockchain-based applications have sprung up. Among them, the blockchain with recognition system is the most popular in the financial industry.

In general, the occupant blockchain will first obtain the network address of the node of the entire blockchain network. Assuming ten nodes, ten network addresses are obtained in advance. Next, a set of key pairs is generated for each node and a corresponding node identifier is generated by using the public key. Taking "Ethereum" as an example, the node identifier is communicated through the public key, the network address, and the service. Generated, for example, the node identification code is: "enode://f3bb48a3adf47226eeea89d08915e6d84b62797b5b67e48abb41b3c05c064dcfbe1922775103d7672fa8e122fe50c82baf136666816a360c579f0ad18f61a686@52.78.19.221:30303". Therefore, in the case of ten nodes, ten node identification codes are generated first. Then, each node executes the blockchain program using the corresponding private key on the specified network address, for example, "Geth" of "Ethereum". Each node will turn off the node discovery function (Node Discovery) and use the node data as a static node list. However, in the case of adding a new node, it is necessary to update the static node list of each node in the blockchain network one by one. When the number of nodes is large, it takes a lot of time to complete the newly added node, and therefore, has a node. The problem of inconvenient expansion.

In summary, it can be seen that there has been a problem of inconvenient node expansion in the prior art, and it is therefore necessary to propose an improved technical means to solve this problem.

The invention discloses a blockchain-based node list maintenance system and a method thereof.

First, the present invention discloses a blockchain-based node list maintenance system, which includes: a node and a management node. In the node part, a plurality of nodes form a blockchain network, and each node has a blockchain of the same content and includes: a generating module, a reading module, and a connecting module. The generating module is configured to continuously generate a block according to the transaction, and after the block is verified by the node, the block is connected to the end of the block chain, and the node is initially preset according to the preset The creation block definition file generates the creation block as the head end of the blockchain, and at the same time generates a smart contract in the creation block to record the node list. The smart contract contains the preset contract address; Reading the list of nodes in the blockchain continuously according to the contract address, and storing the contents of the list of nodes to the list array, the list array containing the node identification code of each node; and the connection module for the joining area Before the blockchain network, the preset static node list is connected with the blockchain network. After joining the blockchain network and updating the blockchain, all nodes are connected according to the node identifier of the list array, and each node is maintained. The connection between the nodes. In a part of the management node, the management node is configured to connect to the blockchain network and pre-store each network address and a set of key pairs of each node, and generate corresponding correspondence according to the network address and the pair of key pairs. The node identification code of each node, and the node identification code of each node is stored to the blockchain using the privileged account to update the node list.

In addition, the present invention discloses a blockchain-based node list maintenance method, the steps comprising: providing a node to form a blockchain network, each node having a blockchain of the same content, and providing a management node for connecting the zone a blockchain network and pre-storing a network address of each node and a set of key pairs; the node initially generates a creation block as a head end of the block chain according to a preset creation block definition file And simultaneously generate a smart contract in the creation block to record the list of nodes, the smart contract contains a pre-set contract address, and the block is generated continuously according to the transaction, and after the block is verified by the node, the area is The block is connected at the end of the blockchain; the management node generates a node identifier corresponding to each node according to the preset communication port, the network address and the pair of key pairs, and identifies the node of each node by using the license account. The code is stored in the blockchain to update the node list; the node is connected to the blockchain network through a preset static node list before joining the blockchain network, when joining the blockchain network After updating the blockchain, the node continuously reads the list of nodes in the blockchain according to the contract address, and stores the contents of the node list to the inventory array; the node links all nodes according to the node identifier of the list array, and maintains The connection between each node.

The system and method disclosed by the present invention are as above, and the difference from the prior art is that the present invention stores a node list in a blockchain through a smart contract, and uses a preset static node list before the node joins the blockchain network. The blockchain network is connected. After the node joins the blockchain network, the node list in the blockchain is continuously read according to the contract address, and the contents of the node list are stored in the list array so as to be based on the node identifier of the list array. Link all nodes and maintain the connection between each node.

Through the above technical means, the present invention can achieve the technical effect of improving the convenience of the node expansion in the blockchain environment of the approved system.

The embodiments of the present invention will be described in detail below with reference to the drawings and embodiments, so that the application of the technical means to solve the technical problems and achieve the technical effects can be fully understood and implemented.

Before describing the blockchain-based node list maintenance system and the method thereof disclosed in the present invention, the nouns defined by the present invention are first described. The management node according to the present invention refers to a computer device of the authority unit, which is responsible for management. All nodes of the blockchain network include a network location, a key pair (ie, a pair of corresponding public and private keys), and a node identifier, and a list of nodes that the privileged account can update the blockchain. In addition, the list array refers to a memory space for storing a list of nodes read from the blockchain. In other words, the contents of the list array are changeable and can be regarded as a variable.

The following is a description of the blockchain-based node list maintenance system and the method thereof according to the following drawings. Please refer to "FIG. 1" first, and "FIG. 1" is the system of the blockchain-based node list maintenance system of the present invention. Block diagram, this system includes: node 110 and management node 120. In the portion of the node 110, the plurality of nodes 110 form a blockchain network 100. Each node 110 has a blockchain of the same content and includes a generation module 111, a reading module 112, and a connection module 113. The generating module 111 is configured to continuously generate a block according to the transaction, and after the block is verified by the node 110, the block is connected to the end of the blockchain, and the node 110 is Initially, a Genesis block is generated as a head end of the blockchain according to a preset creation block definition file, and at the same time, a smart contract is generated in the creation block to record a node list, and the smart contract includes a preset Contract address. In actual implementation, a new node list is generated, and a block containing a node list can be generated by a transaction method, and after the block is verified, the block is linked to the end of the block chain, and then When the node 110 reads the node list through the contract address, it will read from the last generated block containing the node list. In addition, in actual implementation, the authority to update the smart contract can be set by using the creation block definition file, for example, by setting the account of the list of updateable nodes in the creation block definition file "genesis.json", for example: "0x1a9afb711302c5f83b5902843d1c007a1a137632" (ie: franchise account). In particular, the smart contract can record at least one owner (recorded in the above account mode), and when the node 110 owns the license account, it becomes the owner of the smart contract, allowing the transaction to be sent to change the contents of the node list. In actual implementation, at least one privileged account number needs to be preset in "genesis.json" to avoid the possibility of changing the contents of the node list afterwards.

The reading module 112 is configured to continuously read the list of nodes in the blockchain according to the contract address and store the contents of the list of nodes to the inventory array, the list array containing the node identification code of each node 110. In practical implementation, after reading the node list, the node 110 cancels storing the content of the node list to the list array when the content of the node list is the same as the content of the list array of the node 110. In this way, the conversion and processing time spent storing the contents of the node list to the list array can be saved, thereby increasing the execution efficiency.

The connection module 113 is used to connect to the blockchain network 100 through a preset static node list before joining the blockchain network 100. After joining the blockchain network 100 and updating the blockchain, according to the list The node identification code of the array links all nodes 110 and maintains the connection between each node 110. The maintaining the connection between each node 110 includes disconnecting the connection with the node 110 that has been deleted, and establishing a connection with the newly added node 110. In actual implementation, when the node 110 is the first node, the preset static node list may be a null value (Null), and the node 110 after the first node may have a preset static node list as a block. At least one of the nodes 110 in the chain network 100 may even be directly set as the node identification code of the management node 120.

In the portion of the management node 120, the management node 120 is configured to connect to the blockchain network 100 and pre-store the network address and a set of key pairs of each node 110, and according to the network address and the group of gold The key pair generates a node identification code corresponding to each node 110, assuming that the generated node identification code is: "enode://f3bb48a3adf47226eeea89d08915e6d84b62797b5b67e48abb41b3c05c064dcfbe1922775103d7672fa8e122fe50c82baf136666816a360c579f0ad18f61a686@52.78.19.221:30303". In the node identification code of this example, the key used is "f3bb48a3adf47226eeea89d08915e6d84b62797b5b67e48abb41b3c05c064dcfbe1922775103d7672fa8e122fe50c82baf136666816a360c579f0ad18f61a686", the network address is "52.78.19.221", and the communication port is "30303". In addition, the management node 120 stores the node identification code of each node 110 to the blockchain using the privileged account to update the node list. In this way, regardless of the newly added new node or the existing old node, after the blockchain update is completed, the node identification code is obtained from the latest node list, and the node identification code is added (established) or Deleting (interrupting) node connections eliminates the need to manually update the static node list at each node, and automatically maintains the connection between each node 110 in the latest state.

In particular, the node 110 and the management node 120 are computer devices having network connection capabilities and interconnected through a network. For example, it can be a server, a computer host, or the like. In addition, the management node 120 can be regarded as a node in the blockchain network 100, which differs from the node 110 only in that the management node 120 pre-stores the network address and a set of key pairs of each node 110. And the node identification code of each node 110 can be generated and stored in the blockchain to update the node list.

Next, please refer to "FIG. 2", which is a flowchart of a method for maintaining a node list based on a blockchain according to the present invention. The steps include: providing a node 110 for forming a blockchain network 100, each A node 110 has a blockchain of the same content, and provides a management node 120 for connecting to the blockchain network 100 and pre-storing the network address of each node 110 and a set of key pairs (step 210); At initial stage, node 110 generates a creation block as a head end of the blockchain according to a preset creation block definition file, and simultaneously generates a smart contract in the creation zone to record a node list, the smart contract including a preset The contract address, and the block is continuously generated according to the transaction, and after the block is verified by the node 110, the block is linked at the end of the blockchain (step 220); the management node 120 is based on the network address. And the set of key pairs generates a node identification code corresponding to each node 110, and stores the node identification code of each node 110 to the blockchain using a privileged account to update the node list (step 230); the node 110 is joining Before the blockchain network 100, it is connected to the blockchain network 100 through a preset static node list. After joining the blockchain network 100 and updating the blockchain, the node 110 continues to read the block according to the contract address. a list of nodes in the chain, and storing the contents of the list of nodes to the inventory array (step 240); the nodes concatenate all nodes according to the node identification code of the inventory array and maintain a connection between each node 110 (step 250) . Through the above steps, the node list can be stored in the blockchain through the smart contract, and before the node 110 joins the blockchain network 100, the node is connected to the blockchain network 100 using a preset static node list. After joining the blockchain network 100, the list of nodes in the blockchain is continuously read according to the contract address, and the contents of the node list are stored to the list array to link all the nodes 110 according to the node identifier of the list array, and each is maintained. A connection between a node 110.

The following description will be made by way of example with reference to "Fig. 3" and "Fig. 4". Please refer to "3rd figure" and "3rd figure" as a schematic diagram of the change of the node list of the newly added node of the present invention. Assuming node 110 reads a list of nodes on the blockchain based on the contract address, node 110 stores the contents of the list of read nodes in a list array, the contents of which are illustrated by array 311. Before the new node joins the blockchain network 100, the management node 120 generates a corresponding node identifier 320 according to the network address, key pair and communication port of the new node stored in advance, and then the management node 120 passes the license. The list of nodes for the account update blockchain. As for the new node, the new node joins the blockchain network 100 through the preset static node list to join the blockchain network 100 before joining the blockchain network 100, and joins the blockchain. After the network 100, the new node updates its own blockchain. When all the nodes 110 in the blockchain network 100 complete the update of the blockchain, the node 110 reads the list of nodes from the blockchain. The content is also stored in the inventory array, at which point the contents of its inventory array are as illustrated by array 312. In this way, all nodes 110 can read the latest node list for storage to their own inventory array to automatically maintain the connections between the various nodes 110.

As shown in "Fig. 4", "Fig. 4" is a schematic diagram showing changes in the list of nodes for deleting nodes by applying the present invention. It is assumed that the management node 120 wants to delete a node (with the node identification code 420), which can update the node list of the blockchain through a privileged account number, such as: "0x1a9afb711302c5f83b5902843d1c007a1a137632". When each node 110 in the blockchain updates the blockchain and reads the latest node list, it finds the list of nodes read in the blockchain and the contents of its own list array (the contents of which are represented by array 411). At the same time, node 110 will re-storage the contents of the node list to the inventory array, the contents of which are illustrated by array 412. At this point, the content update of the list array is completed. Then, the node 110 maintains the connection between each node 110 according to the content of the new list array. In this example, since a node identifier 420 is deleted, the new The contents of the manifest array do not have a node identification code 420, so all nodes 110 will be disconnected from the node having the node identification code 420.

In summary, it can be seen that the difference between the present invention and the prior art is that the node list is stored in the blockchain through the smart contract, and the preset static node list and the blockchain are used before the node joins the blockchain network. The network link, after the node joins the blockchain network, continuously reads the list of nodes in the blockchain according to the contract address, and stores the contents of the node list to the list array, so as to link all the nodes according to the node identifier of the list array. And maintaining the connection between each node, by this technical means can solve the problems existing in the prior art, and in the privileged blockchain environment, the technical effect of improving the convenience of the node expansion is achieved.

While the present invention has been described above in the foregoing embodiments, it is not intended to limit the invention, and the invention may be modified and modified without departing from the spirit and scope of the invention. The scope of patent protection shall be subject to the definition of the scope of the patent application attached to this specification.

100 blockchain network 110 node 111 generation module 112 read module 113 connection module 120 management node 311, 312 array 320 node identification code 411, 412 array 420 node identification code step 210 provides multiple nodes to form a blockchain network, each node having a blockchain of the same content, and a management node for connecting the blockchain network and pre-storing a network address and a set of keys for each node And in the initial step, the node generates a creation block according to the preset creation block definition file as the head end of the block chain, and simultaneously generates a smart contract in the creation zone to record a node. In the list, the smart contract includes a predetermined contract address, and a block is continuously generated according to the transaction, and after the block is verified by the node, the block is linked at the end of the block chain. The management node generates a node corresponding to each node according to a preset communication port, the network address, and the pair of key pairs. An identification code, and storing the node identification code of each node to the blockchain to update the node list using a privileged account. Step 240: The node passes a preset static node before joining the blockchain network. The list is linked to the blockchain network. After joining the blockchain network and updating the blockchain, the node continuously reads the list of nodes in the blockchain according to the contract address, and the node is The contents of the manifest are stored in a list array step 250. The node links all nodes according to the node identifier of the list array, and maintains the connection between each node.

FIG. 1 is a system block diagram of a node list maintenance system based on a blockchain according to the present invention. FIG. 2 is a flow chart of a method for maintaining a node list based on a blockchain according to the present invention. Figure 3 is a schematic diagram showing changes in the list of nodes to which the new node of the present invention is applied. Figure 4 is a schematic diagram showing the change of the node list of the deleted node by applying the present invention.

Claims (10)

A blockchain-based node list maintenance system, the system comprising: a plurality of nodes for forming a blockchain network, each node having a blockchain of the same content and comprising: a generating module for Continuing to generate a block according to the transaction, and after the block is verified by the node, the block is linked at the end of the block chain, and the node is initially defined according to a preset creation block. The file generates a creation block as the head end of the blockchain, and simultaneously generates a smart contract in the creation block to record a list of nodes, the smart contract includes a predetermined contract address; a group for continuously reading the list of nodes in the blockchain according to the contract address, and storing the contents of the list of nodes to a list array, the list array including a node identifier of each node; and a connection a line module, configured to connect to the blockchain network through a preset static node list before joining the blockchain network, after joining the blockchain network and updating the blockchain, according to Clear The node identifier of a single array links all nodes and maintains a connection between each node; and a management node for connecting the blockchain network and pre-storing a network address of each node and a Grouping a key pair, and generating a node identification code corresponding to each node according to a preset communication port, the network address and the pair of key pairs, and using the privileged account to set the node identification code of each node Save to the blockchain to update the list of nodes. The blockchain-based node list maintenance system according to claim 1, wherein after the node reads the node list, when the content of the node list is the same as the content of the list array of the node, canceling The contents of the list of nodes are stored to the list array. A blockchain-based node list maintenance system according to claim 1, wherein maintaining a connection between each node includes disconnecting the connection with the node that has been deleted, and establishing and adding the new The connection of the node. A blockchain-based node list maintenance system according to claim 1, wherein the smart contract records at least one owner, and when the node is the owner, allows the node to send a transaction to update the block A list of the nodes in the chain. According to the blockchain-based node list maintenance system of claim 1, wherein the node is the first node, the preset static node list is a null value, and the node after the first node is The preset list of static nodes is at least one of the nodes of the blockchain network. A method for maintaining a node list based on a blockchain, the method comprising: providing a plurality of nodes to form a blockchain network, each node having a blockchain of the same content, and providing a management node for connecting the node Block network and pre-storing a network address and a set of key pairs of each node; the node initially generates a creation block according to a preset creation block definition file as the block At the head end of the chain, and simultaneously generate a smart contract in the creation block to record a list of nodes, the smart contract contains a predetermined contract address, and continuously generate a block according to the transaction, and pass through the block. After the node is verified, the block is connected to the end of the blockchain; the management node generates a node corresponding to each node according to a preset communication port, the network address, and the pair of key pairs. An identification code, and storing the node identification code of each node to the blockchain to update the node list by using a privileged account; the node clears through a preset static node before joining the blockchain network Linking to the blockchain network, after joining the blockchain network and updating the blockchain, the node continuously reads the list of nodes in the blockchain according to the contract address, and the node is The contents of the manifest are stored to an inventory array; and the node links all nodes according to the node identification code of the list array and maintains a connection between each node. The blockchain-based node list maintenance method according to claim 6, wherein after the node reads the node list, when the content of the node list is the same as the content of the list array of the node, the cancellation is The contents of the list of nodes are stored to the list array. The blockchain-based node list maintenance method according to claim 6 of the patent application scope, wherein the step of maintaining a connection between each node includes disconnecting a connection with the node that has been deleted, and establishing and adding The connection of the node. A blockchain-based node list maintenance method according to claim 6, wherein the smart contract records at least one owner, and when the node is the owner, allows the node to send a transaction to update the block A list of the nodes in the chain. The blockchain-based node list maintenance method according to claim 6 of the patent application scope, wherein when the node is the first node, the preset static node list is a null value, and the node after the first node is The preset list of static nodes is at least one of the nodes of the blockchain network.