CN112200680B - Blockchain node management method, device, computer and readable storage medium - Google Patents

Abstract

The embodiment of the application discloses a block link point management method, a block link point management device, a computer and a readable storage medium, wherein the method comprises the following steps: acquiring at least two network nodes in a block chain network, and acquiring a consensus weight of each network node from a full node table; acquiring at least two consensus nodes from at least two network nodes based on the consensus weight of each network node; detecting the connection state of at least two consensus nodes, recording the consensus nodes with the connection state being the disconnection state as consensus nodes to be connected, acquiring the node address information of the consensus nodes to be connected from the whole node table, and establishing network connection among the consensus nodes to be connected based on the node address information to obtain a consensus network; and when a network quitting request of the network node to be processed is obtained, returning the consensus weight of the network node to be processed, and deleting the network node to be processed in the whole node table. By adopting the method and the device, the flexibility of network node management in the block chain network can be improved.

Description

Blockchain node management method, device, computer and readable storage medium

technical field

The present application relates to the field of blockchain technology, and in particular, to a method, device, computer and sustainable storage medium for managing blockchain nodes.

Background technique

With the increasing maturity of blockchain technology, coupled with the decentralization and other characteristics of blockchain, the application of blockchain has become increasingly widespread. Among them, there is more than one network node in the blockchain network, and the network nodes that make up the blockchain network may change, especially the network nodes that make up the consensus network have a high probability of changing. At present, when a network node is added to the blockchain network, the network connection of the network node is deployed to add the network node to the blockchain network. When the network node in the blockchain network changes , it is necessary to delete the existing network connection and re-establish the network connection between the updated network nodes, so that the configuration of the network nodes is relatively fixed, and the update of the deployment of the blockchain network is more difficult, which makes it difficult to update the deployment of the blockchain network. The update process consumes more resources, which reduces the flexibility of network node management in the blockchain network.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a blockchain node management method, device, computer equipment, and storage medium, which can improve the flexibility of network node management in a blockchain network.

On the one hand, the embodiments of the present application provide a blockchain node management method, including:

Obtain at least two network nodes in the blockchain network, and obtain the consensus weight of each network node from the full node table;

Obtain at least two consensus nodes from at least two network nodes based on the consensus weight of each network node;

Detect the connection status of at least two consensus nodes, record the consensus node whose connection status is disconnected as the consensus node to be connected, and obtain the node address information of the consensus node to be connected from the full node table. Establish network connections between consensus nodes to obtain a consensus network;

When the logout request of the network node to be processed is obtained, the consensus weight of the network node to be processed is obtained from the full node table, the consensus weight of the network node to be processed is sent to the network node to be processed, and the pending network node is deleted from the full node table. The network node, if the pending network node that initiates the withdrawal request belongs to the consensus network, the consensus network is updated; the pending network node belongs to at least two network nodes.

Among them, the full node table includes the identity label and consensus weight of each network node;

Obtain at least two network nodes in the blockchain network, and obtain the consensus weight of each network node from the full node table, including:

Obtain at least two network nodes in the blockchain network, obtain the identity label of each network node from the full node table, obtain network nodes whose identity labels are consensus labels from at least two network nodes, and obtain candidate consensus nodes;

Obtain consensus weights of candidate consensus nodes from the full node table;

Based on the consensus weight of each network node, obtain at least two consensus nodes from at least two network nodes, including:

Obtain the number of consensus nodes, and determine N consensus nodes from the candidate consensus nodes based on the consensus weight of the candidate consensus nodes and the number of consensus nodes; the number of consensus nodes is used to represent the number of consensus nodes that form a consensus network, and N is the number of consensus nodes.

Among them, based on the consensus weight of each network node, at least two consensus nodes are obtained from at least two network nodes, including:

Obtain the number of consensus nodes, sort at least two network nodes based on the consensus weight of each network node, and obtain N consensus nodes from at least two network nodes according to the sorting result; the number of consensus nodes is used to represent the consensus nodes that constitute the consensus network , and N is the number of consensus nodes.

Wherein, the full node table includes the identity label of each network node;

Detect the connection status of at least two consensus nodes, and record the consensus node whose connection status is disconnected as the consensus node to be connected, including:

Obtain the identity labels corresponding to N consensus nodes from the full node table, and determine the connection state of the consensus node whose identity label is not the consensus label as the disconnected state;

The consensus node whose connection state is disconnected is recorded as the consensus node to be connected.

Wherein, the method also includes:

Obtain historical consensus nodes whose identity labels are consensus labels from the full node table;

If the historical consensus node does not belong to N consensus nodes, disconnect the network connection of the historical consensus node, update the identity label of the historical consensus node in the full node table to the data label, perform detection of the connection status of at least two consensus nodes, and set the A consensus node whose connection state is disconnected is recorded as the step to be connected to a consensus node.

Wherein, the method also includes:

Obtain the node identifiers of at least two consensus nodes from the full node table, and generate a consensus node table according to the node identifiers of the at least two consensus nodes;

The consensus network block is generated according to the consensus node table. If the consensus on the consensus network block is passed, the consensus network block is added to the node management block chain, and the step of detecting the connection status of at least two consensus nodes is performed.

Wherein, the method also includes:

Obtain the virtual mortgage rights and historical consensus times of network nodes, and determine the consensus weight of network nodes according to the virtual mortgage rights and historical consensus times;

If the consensus on the consensus weight is passed, the consensus weight is added to the node management blockchain, and the association between the consensus weight and the network nodes is added to the full node table.

Wherein, the method also includes:

Obtain the node network access request sent by the target network node; the node network access request includes the target node identifier, the target identity label and the target node address information of the target network node;

Verify the target network node according to the target node identifier and the target node address information, and obtain the target identity label if the target node address information of the target network node is legal;

Consensus is carried out on the target identity label. If the consensus is passed, the node information block is generated according to the target node identification, target identity label and target node address information, and the node information block is added to the node management blockchain;

Add the target node identification, target identity label and target node address information to the full node table.

Among them, the consensus on the target identity label, including:

If the target identity label is a consensus label, obtain the target virtual mortgage rights of the target identity label;

Obtain the consensus equity threshold. If the target virtual mortgage equity is less than the consensus equity threshold, it is determined that the consensus on the target identity label has failed, and a label exception message is sent to the target network node;

If the target virtual mortgage equity is greater than or equal to the consensus equity threshold, the target consensus weight of the target network node is generated according to the target virtual mortgage equity, and it is determined that the consensus on the target identity label is passed.

Wherein, the full node table also includes the node signature of each network node;

The method also includes:

If an abnormal node is detected from at least two network nodes, obtain the public key of the abnormal node;

Use the public key of the abnormal node to verify the signature of the node corresponding to the abnormal node in the full node table. If the verification is passed, a node confirmation message is sent to the abnormal node; the node confirmation message is used to obtain abnormal data from the abnormal node;

If the node signature verification of the abnormal node fails, the network connection with the abnormal node is disconnected, and the data associated with the abnormal node is deleted from the full node table.

On the one hand, the embodiments of the present application provide a block chain node management device, and the above device includes:

The weight obtaining module is used to obtain at least two network nodes in the blockchain network, and obtain the consensus weight of each network node from the full node table;

The node selection module is used to obtain at least two consensus nodes from at least two network nodes based on the consensus weight of each network node;

The connection establishment module is used to detect the connection status of at least two consensus nodes, record the consensus node whose connection status is disconnected as the consensus node to be connected, and obtain the node address information of the consensus node to be connected from the full node table. The node address information establishes a network connection between the consensus nodes to be connected to obtain a consensus network;

The node de-networking module is used to obtain the consensus weight of the to-be-processed network node from the full node table when the de-network request of the to-be-processed network node is obtained, send the consensus weight of the to-be-processed network node to the to-be-processed network node, and delete For the network nodes to be processed in the full node table, if the network node to be processed that initiates the withdrawal request belongs to the consensus network, the consensus network is updated; the network nodes to be processed belong to at least two network nodes.

Among them, the full node table includes the identity label and consensus weight of each network node;

The weight acquisition module includes:

The label obtaining unit is used to obtain at least two network nodes in the blockchain network, obtain the identity label of each network node from the full node table, and obtain the network node whose identity label is the consensus label from the at least two network nodes, Get candidate consensus nodes;

The weight acquisition unit is used to acquire the consensus weight of candidate consensus nodes from the full node table;

This node selects the module, which is specifically used for:

Obtain the number of consensus nodes, and determine N consensus nodes from the candidate consensus nodes based on the consensus weight of the candidate consensus nodes and the number of consensus nodes; the number of consensus nodes is used to represent the number of consensus nodes that form a consensus network, and N is the number of consensus nodes.

Among them, the node selection module is specifically used for:

Obtain the number of consensus nodes, sort at least two network nodes based on the consensus weight of each network node, and obtain N consensus nodes from at least two network nodes according to the sorting result; the number of consensus nodes is used to represent the consensus nodes that constitute the consensus network , and N is the number of consensus nodes.

Wherein, the full node table includes the identity label of each network node;

In terms of detecting the connection status of at least two consensus nodes, and recording the consensus node whose connection status is disconnected as the consensus node to be connected, the connection establishment module includes:

The state determination unit is used to obtain the identity labels corresponding to the N consensus nodes from the full node table, and determine the connection state of the consensus node whose identity label is not the consensus label as the disconnected state;

The consensus determination unit is used to record the consensus node whose connection state is in the disconnected state as the consensus node to be connected.

Wherein, the device also includes:

The history acquisition module is used to obtain the historical consensus nodes whose identity label is the consensus label from the full node table;

The label update module is used to disconnect the network connection of the historical consensus node if the historical consensus node does not belong to N consensus nodes, update the identity label of the historical consensus node in the full node table to the data label, and perform detection of at least two consensuses The connection status of the node, the consensus node whose connection status is disconnected is recorded as the step to be connected to the consensus node.

Wherein, the device also includes:

The table generation module is used to obtain the node identifiers of at least two consensus nodes from the full node table, and generate a consensus node table according to the node identifiers of the at least two consensus nodes;

The data storage module is used to generate a consensus network block according to the consensus node table. If the consensus on the consensus network block is passed, the consensus network block will be added to the node management blockchain, and the connection status of at least two consensus nodes will be detected. A step of.

Wherein, the device also includes:

The weight determination module is used to obtain the virtual mortgage rights and historical consensus times of network nodes, and determine the consensus weights of network nodes according to the virtual mortgage rights and historical consensus times;

The data uploading module is used to add the consensus weight to the node management blockchain if the consensus on the consensus weight is passed, and add the association between the consensus weight and the network nodes to the full node table.

Wherein, the device also includes:

A request obtaining module is used to obtain the node network access request sent by the target network node; the node network access request includes the target node identifier, the target identity label and the target node address information of the target network node;

The node verification module is used to verify the target network node according to the target node identifier and the target node address information, and obtain the target identity label if the target node address information of the target network node is legal;

The label verification module is used to reach a consensus on the target identity label. If the consensus is passed, the node information block will be generated according to the target node identification, target identity label and target node address information, and the node information block will be added to the node management blockchain. ;

The node adding module is used to add target node identification, target identity label and target node address information to the full node table.

Among them, in terms of consensus on the target identity label, the label verification module includes:

The equity acquisition unit is used to acquire the target virtual mortgage equity of the target identity label if the target identity label is a consensus label;

The message sending unit is used to obtain the consensus equity threshold. If the target virtual mortgage equity is less than the consensus equity threshold, it is determined that the consensus on the target identity label has failed, and a label exception message is sent to the target network node;

The verification pass unit is used to generate the target consensus weight of the target network node according to the target virtual mortgage equity if the target virtual mortgage equity is greater than or equal to the consensus equity threshold, and determine that the consensus on the target identity label is passed.

Wherein, the full node table also includes the node signature of each network node;

The device also includes:

a public key acquisition module, configured to acquire the public key of the abnormal node if an abnormal node is detected from at least two network nodes;

The node signature verification module is used to verify the signature of the abnormal node in the full node table by using the public key of the abnormal node. If the signature is passed, it will send a node confirmation message to the abnormal node; The node obtains abnormal data;

The node signature verification module is further configured to disconnect the network connection with the abnormal node if the node signature verification of the abnormal node fails, and delete the data associated with the abnormal node from the full node table.

An aspect of the embodiments of the present application provides a computer device, including a processor, a memory, and an input and output interface;

The processor is connected to the memory and the input-output interface respectively, wherein the input-output interface is used for data interaction of each network node in the blockchain, the memory is used to store the program code, and the processor is used to call the program code, To execute the blockchain node management method implemented in one aspect of the embodiments of the present application.

An aspect of an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program includes program instructions. When the program instructions are executed by a processor, an aspect of the embodiments of the present application is executed. The blockchain node management method implemented in .

In one aspect, embodiments of the present application provide a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in various optional manners in one aspect of the embodiments of the present application.

Implementing the embodiments of the present application will have the following beneficial effects:

In the embodiment of the present application, the consensus weight of each network node is obtained from the full node table by obtaining at least two network nodes in the blockchain network; based on the consensus weight of each network node, at least two network nodes are obtained from the at least two network nodes. Two consensus nodes; detect the connection status of at least two consensus nodes, record the consensus node whose connection status is disconnected as the consensus node to be connected, and obtain the node address information of the consensus node to be connected from the full node table. A network connection is established between the address information and the consensus node to be connected, and a consensus network is obtained; when the logout request of the network node to be processed is obtained, the consensus weight of the network node to be processed is obtained from the full node table, and the consensus weight of the network node to be processed is obtained. The consensus weight is sent to the pending network node, and the pending network node in the full node table is deleted. If the pending network node that initiated the withdrawal request belongs to the consensus network, the consensus network is updated; the pending network node belongs to at least two network nodes . Through the above process, a full node table is introduced into the blockchain network, and the full node table stores the node information (such as consensus weight) of each network node in the blockchain network. When the network nodes change, the data of the changed network nodes can be directly obtained from the full node table, and a consensus network can be established based on the full node table, without the need to re-count the node information of each network node, and without the need to re-implement the blockchain network. The deployment of the blockchain network reduces the time and resources required to update the blockchain network when the blockchain network changes, and improves the flexibility of network node management in the blockchain network.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

1 is an optional schematic diagram of a block structure provided by an embodiment of the present application;

2 is a schematic diagram of a network architecture for block chain node management provided by an embodiment of the present application;

3 is a schematic diagram of a blockchain node management scenario provided by an embodiment of the present application;

4 is a flowchart of a method for managing a blockchain node provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a consensus network determination provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of another consensus network determination provided by an embodiment of the present application;

7 is a schematic diagram of a block chain node management device provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application.

Among them, the embodiments of this application can store and transmit data generated in the network nodes (such as consensus nodes or common network nodes, etc.) mentioned in this application based on cloud technology, and are applicable to the field of data transmission in big data . For example, cloud storage technology is used to store the data generated in this application, and data transmission technology in cloud technology is used to realize data interaction between various network nodes.

Among them, cloud technology refers to a kind of hosting technology that unifies a series of resources such as hardware, software, and network in a wide area network or a local area network to realize the calculation, storage, processing and sharing of data.

Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, and application technology based on cloud computing business models. Cloud computing technology will become an important support. Background services of technical network systems require a lot of computing and storage resources, such as video websites, picture websites and more portal websites. With the high development and application of the Internet industry, in the future, each item may have its own identification mark, which needs to be transmitted to the back-end system for logical processing. Data of different levels will be processed separately, and all kinds of industry data need to be strong. The system backing support can only be achieved through cloud computing.

Among them, in this application, there may be a large number of network nodes in a blockchain network, each network node may generate or store a large amount of data, and there may also be a lot of data interaction between each network node. Therefore, in In this application, big data technology can be used to manage the data generated in this application, such as data transmission, data storage or data update.

Among them, big data refers to the collection of data that cannot be captured, managed and processed by conventional software tools within a certain time frame. It requires new processing modes to have stronger decision-making, insight and process optimization capabilities. of massive, high-growth and diversified information assets. With the advent of the cloud era, big data is also attracting more and more attention, and big data requires special technologies to efficiently process a large amount of data that tolerates elapsed time. Technologies applicable to big data, including massively parallel processing databases, data mining, distributed file systems, distributed databases, cloud computing platforms, the Internet, and scalable storage systems. When there are multiple blockchains in the blockchain network, or there are many blocks in the blockchain, the implementation of the solution of this application will generate a large amount of data. Big data technology can be used to improve the cost Efficiency of the implementation of the scheme applied for.

Among them, blockchain is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain (Blockchain) is essentially a decentralized database, which is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information to verify its Validity of information (anti-counterfeiting) and generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer. The blockchain includes a series of blocks (Blocks) that follow each other in chronological order. Once a new block is added to the blockchain, it will not be removed. The block records the nodes in the blockchain system. Submitted record data.

1 is an optional schematic diagram of a block structure (Block Structure) provided by an embodiment of the present application, and each block includes the hash value of the transaction record stored in this block (this The hash value of the block), and the hash value of the previous block, each block is connected by the hash value to form a blockchain. In addition, the block may also include information such as the timestamp when the block was generated or the block height of the block. The block may include a block header and a block body. As shown in Figure 1, a block 1 includes a block header and a block body. The block body of the block 1 can store transaction data 1. The block 1 The block header can include the hash of the previous block and the hash of the current block, where the hash of the previous block is the hash of the previous block of block 1. For example, in Figure 1, the block 1 is the first block in the blockchain, then the hash of the previous block in block 1 can be empty. The block body of block 2 includes transaction data 2, and the block header of block 2 includes the hash of the previous block and the hash of this block, wherein the hash of the previous block is the previous block of block 2. The hash of the block (i.e. block 1). The block body of block 3 includes transaction data 3, and the block header of block 3 includes the hash of the previous block and the hash of this block, wherein the hash of the previous block is the previous block of block 3. The hash of the block (i.e. block 2).

Wherein, in the embodiment of the present application, the blockchain network includes at least two network nodes, there may be network connections between each network node, and each network node may perform data interaction based on the network connection. Wherein, each of the at least two network nodes may carry different identity labels, such as consensus labels, data labels, or lightweight labels. For details, please refer to FIG. 2 , which is a schematic diagram of a network architecture of a blockchain node management provided by an embodiment of the present application. As shown in FIG. 2 , when the network node 201 is added to the blockchain network, the data of the network node 201 is added to the full node table, wherein the data of the network node 201 can be recorded as the data of the network node 201 Node information. The node information may include the node identifier of the network node 201 , and optionally, the node information may also include the identity label of the network node 201 . Wherein, when the network node 201 is added to the full node table, the identity label sent by the network node 201 can be added to the full node table, and if the identity label sent by the network node 201 is empty, the identity label sent by the network node 201 can be added. The identity tag of the network node 201 is a data tag or a lightweight tag by default. Among them, the data label is used to indicate that the corresponding network node has the authority to obtain the transaction block in the blockchain network, but does not have the consensus authority to the transaction block; the lightweight label is used to indicate that the corresponding network node has the authority to obtain the block. The authority of some transaction blocks in the chain network, and does not have consensus authority.

Among them, when a new consensus cycle starts, the node information of each network node in the full node table in the blockchain network can be obtained, and each network node is selected based on the node information, and the new consensus cycle is determined. The consensus nodes constituting the consensus network 202 include a consensus node 2021, a consensus node 2022, and a consensus node 2023, among which, each consensus node belongs to the corresponding network node in the full node table, and the consensus network is a part of the blockchain network. Specifically, the full node table includes the consensus weight of each network node. Based on the consensus weight, the probability of each network node being a consensus node can be obtained, so that at least two consensus nodes can be obtained from at least two network nodes. At least two consensus nodes form a consensus network. Further, the full node table may also include node address information of each network node, and a network connection between each consensus node may be established based on the node address information to obtain a consensus network. Among them, in the full node table, the consensus weight and node address information of the network node can be recorded as the node information of the network node, that is, the full node table stores the node information of each network node in the blockchain network , based on the node information of each network node, a consensus network can be selected, a network connection can be established, or data interaction can be performed, etc., so that when the network nodes in the blockchain network change, the blockchain network can be updated directly based on the full node table. It reduces the time and resources spent in the update process of the blockchain network, and improves the flexibility of the network node management of the blockchain network.

The above-mentioned network node may be a server or a terminal device, or a system composed of a server and a terminal device, wherein the terminal device mentioned above may be an electronic device, including but not limited to a mobile phone, a tablet computer, a desktop computer , laptops, PDAs, wearable devices (such as smart watches, smart bracelets, etc.), Augmented Reality/Virtual Reality (AR/VR) devices, head-mounted displays, smart speakers, digital cameras, cameras and Other mobile internet devices (mobile internet devices, MIDs) with network access capability, etc. The server mentioned above may be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud service, cloud database, cloud computing, cloud function, cloud storage, Network services, cloud communications, middleware services, domain name services, security services, Content Delivery Network (CDN), and cloud servers for basic cloud computing services such as big data and artificial intelligence platforms.

Specifically, reference may be made to FIG. 3 , which is a schematic diagram of a blockchain node management scenario provided by an embodiment of the present application. As shown in FIG. 3 , when the network node 301 is added to the blockchain network, the node information of the network node 301 is obtained, including the node identifier and the identity label of the network node 301 , and the node identifier can be the network node 301 Internet Protocol (Internet Protocol, ip) address, device identification or other unique identification, etc. The computer device adds the node information of the network node 301 to the full node table 303, and adds the network node 301 to the blockchain network 302, wherein, if the identity label of the network node 301 is empty, the The identity tag of the network node 301 is a data tag or a lightweight tag by default. The full node table can be found in Table 1 below:

Table 1

node name Node ID identity tag consensus weight network node A 192.154.26.31 Consensus label 25 network node B 152.54.35.25 data labels twenty four network node 301 153.241.54.152 data labels 30 ... ... ... ...

When a new consensus cycle starts or the consensus network changes, the computer equipment can determine the number of consensus nodes, obtain the consensus weight of each network node from the full node table, and select at least two consensus nodes according to the consensus weight of each network node, at least two The number of consensus nodes included in each consensus node is the number of consensus nodes. The node information of the at least two consensus nodes is added to the consensus node table 304 , or the node names and node identifiers of the at least two consensus nodes are added to the consensus node table 304 . That is, the consensus node table 304 may include the node name and node identifier of each consensus node, or may also include the identity label and consensus weight of each consensus node. Wherein, when the node information of the consensus nodes included in the consensus node table 304 includes node names and node identifiers, the consensus node table 304 may be shown in Table 2 below:

Table 2

node name Node ID network node A 192.154.26.31 network node 301 153.241.54.152 ... ...

After selecting at least two consensus nodes, obtain the node information of at least two consensus nodes from the full node table, update the identity label in the node information of each consensus node in the full node table to the consensus label, and update the identity before the update. A consensus node whose label is not a consensus label is used as a consensus node to be connected, and a network connection between the consensus node to be connected and other consensus nodes is established to form a consensus network 305 . At this time, each consensus node (eg, consensus node 3051, consensus node 3052, consensus node 3053, consensus node 3054, etc.) in the consensus network 305 can perform data exchange, and conduct consensus on the acquired transaction blocks.

Further, please refer to FIG. 4 , which is a flowchart of a method for managing a blockchain node provided by an embodiment of the present application. As shown in Figure 4, the execution body of the method can be any network node in the blockchain network, and the execution body is denoted as computer equipment, and the process of the blockchain node management method includes the following steps:

In step S401, at least two network nodes in the blockchain network are obtained, and the consensus weight of each network node is obtained from the full node table.

In the embodiment of the present application, in response to the update request for the consensus network, the computer device can obtain at least two network nodes in the blockchain network, and obtain the consensus weight of each network node from the full node table. Among them, the consensus network has a consensus cycle, which is used to represent the update time period of the consensus network. When a consensus cycle ends, a new consensus cycle is started, and an update request for the consensus network is generated. Optionally, it can be based on The smart contract detects the consensus cycle. When a new consensus cycle starts, the smart contract is triggered, and the update request for the consensus network is obtained based on the smart contract; When the information changes, etc.), an update request for the consensus network is generated. In other words, when the consensus network changes, an update request to the consensus network is generated. For example, taking the consensus cycle as an example, assuming that the consensus cycle is represented by the block height range, when a block corresponding to the starting block height in the block height range is generated, the smart contract is triggered, and the full block is obtained based on the smart contract. Node table, obtain the consensus weight of each network node from the full node table. For example, the block height ranges from block height 10 to block height 40, that is, the starting block height is block height 10, and the end block height The height is block height 40, and the smart contract is called to monitor the block generation in the blockchain network. When a block with a block height of 9 is added to the node management blockchain, the starting block height is obtained based on the smart contract. is the consensus period corresponding to the block height range of block height 10. During this consensus period, at least two network nodes are obtained, and the consensus weight of each network node is obtained from the full node table. Among them, after a consensus cycle ends, the new consensus network can be deployed directly without waiting for the deployment process of the consensus network to be triggered at the beginning of the new consensus cycle, which can reduce the transition time of the consensus cycle and improve the smoothness of consensus network switching. It can improve the switching efficiency of the consensus network.

The full node table may include node information of each network node, the node information may include the consensus weight of the corresponding network node, and optionally, the node information may also include the node name, node identifier, and identity label of the corresponding network node or node address information, etc. When determining the consensus nodes constituting the consensus network, in one case, the computer device can obtain at least two consensus nodes from at least two network nodes, and the computer device can obtain the consensus weight of each network node from the full node table; In one case, the computer device can determine at least two consensus nodes based on the identity labels of each network node. Specifically, the computer device can obtain at least two network nodes in the blockchain network, and obtain each network node from the full node table. The identity label of the node, the network node whose identity label is the consensus label is obtained from at least two network nodes, the candidate consensus node is obtained, and the consensus weight of the candidate consensus node is obtained from the full node table.

Step S402, based on the consensus weight of each network node, obtain at least two consensus nodes from at least two network nodes.

In this embodiment of the present application, in step S401, when obtaining at least two consensus nodes from at least two network nodes, the computer device may obtain the number of consensus nodes, and perform a calculation on the at least two network nodes based on the consensus weight of each network node. Sort, obtain N consensus nodes from at least two network nodes according to the sorting result; the number of consensus nodes is used to represent the number of consensus nodes that constitute the consensus network, and N is the number of consensus nodes.

Wherein, in step S401, when the computer device determines at least two consensus nodes based on the identity labels of each network node, the computer device can obtain the number of consensus nodes, and determine from the candidate consensus nodes based on the consensus weight of the candidate consensus nodes and the number of consensus nodes. N consensus nodes; the number of consensus nodes is used to represent the number of consensus nodes forming the consensus network, and N is the number of consensus nodes. Optionally, if the number of candidate consensus nodes is less than the number of consensus nodes, network nodes whose identity labels are not consensus labels can be obtained from the full node table, which are recorded as backup nodes, and the consensus weight corresponding to the backup nodes can be obtained from the full node table. , based on the consensus weight of the standby node, M consensus nodes are obtained from the standby node, M is a positive integer, and the sum of M and the number of candidate consensus nodes is the number of consensus nodes.

The number of consensus nodes may be a default number of nodes, or may be generated according to the number of nodes of at least two network nodes, or may be generated according to the number of blocks included in the blockchain network, or may be generated according to the blockchain network The number of blocks included in the , and the number of at least two network nodes generated, etc., are not limited here. For example, the number of nodes and the node selection ratio of at least two network nodes are obtained, and the number of consensus nodes is determined based on the node selection ratio and the node number of at least two network nodes. Assuming that the node number of at least two network nodes is 80, the node selection If the ratio is 0.1, the number of consensus nodes is determined to be 8.

For example, when the number of consensus nodes is a default number of nodes, the number of consensus nodes can be submitted by an administrator. For example, see FIG. 5 , which is a schematic diagram of determining a consensus network provided by an embodiment of the present application. As shown in FIG. 5 , in response to the submission operation for the number of consensus nodes, the computer device obtains the number of consensus nodes and the node management period entered in the number acquisition page 501 , where the node management period is used to indicate that the corresponding number of consensus nodes is associated with consensus cycle. For example, if the node management period is from consensus period 5 to consensus period 10, and the number of consensus nodes is 7, then when consensus period 5 starts, the number of consensus nodes obtained is 7; optionally, the node management period can be determined by the block height For example, if the node management period is from block height 10 to block height 40, and the number of consensus nodes is 7, it means that 7 consensus nodes are required for the block corresponding to block height 10 to block height 40. Consensus on blocks. Further, a smart contract 502 can be generated according to the number of consensus nodes and the node management period, a contract block 503 can be generated according to the smart contract 502, and a consensus can be made on the contract block 503. If the consensus is passed, the contract block 503 is added. into the node management blockchain 504. Among them, when the target node management cycle is started, a smart contract is triggered, and the smart contract is used to obtain the target contract block 505 associated with the target node management cycle from the node management blockchain 504, and the consensus node is determined based on the target contract block 505. quantity. Based on the consensus weight of each network node and the number of consensus nodes, at least two consensus nodes 507 are obtained from at least two network nodes 506, including consensus node 5071, consensus node 5072, consensus node 5073, consensus node 5074, and the like.

For example, for steps S401 to S402, reference may be made to FIG. 6 , which is a schematic diagram of another consensus network determination provided by an embodiment of the present application. As shown in FIG. 6, in the first case, the computer device obtains at least two network nodes 601, obtains the consensus weight of each network node from the full node table, and obtains at least two network nodes 601 from the at least two network nodes 601 based on the consensus weight. consensus nodes 602 . In the second case, the computer device can obtain the network node whose identity label is the consensus label from the full node table, as the candidate consensus node 603, obtain the consensus weight of the candidate consensus node 603 from the full node table, and obtain the consensus weight of the candidate consensus node 603 from the full node table based on the consensus weight. At least two consensus nodes 602 are obtained from the node 603 . It is assumed that the at least two consensus nodes 602 include a consensus node 6021, a consensus node 6022, a consensus node 6023, a consensus node 6024, and the like.

Step S403: Detect the connection status of at least two consensus nodes, record the consensus node whose connection status is disconnected as the consensus node to be connected, and obtain the node address information of the consensus node to be connected from the full node table, based on the node address information Establish network connections between consensus nodes to be connected to obtain a consensus network.

In the embodiment of the present application, the computer device obtains the identity labels corresponding to N consensus nodes from the full node table, and determines the connection state of the consensus node whose identity label is not the consensus label as the disconnected state; the connection state is the connected state. The consensus node in the disconnected state is recorded as the consensus node to be connected. Optionally, the computer device can obtain the historical consensus network, determine the connection status of the consensus nodes that do not belong to the historical consensus network among the N consensus nodes as the disconnected state, and record the consensus nodes whose connection status is the disconnected state as pending. Connect to consensus nodes.

Further, when the computer device acquires at least two consensus nodes from at least two network nodes, the computer device can acquire historical consensus nodes whose identity tags are consensus tags from the full node table. If the historical consensus node does not belong to N consensus nodes, it means that the historical consensus node does not participate in this consensus process, disconnect the network connection of the historical consensus node, and update the identity label of the historical consensus node in the full node table to data Label, and then detect the connection status of at least two consensus nodes, and record the consensus node whose connection status is disconnected as the consensus node to be connected. Specifically, when disconnecting the network connection of the historical consensus node, the computer device can obtain the node address information of the historical consensus node from the full node table, and send a network disconnection request to the historical consensus node based on the node address information to disconnect the Open network connections with historical consensus nodes. Optionally, if the computer device belongs to a historical consensus node, the computer device obtains the node address information corresponding to each of the N consensus nodes from the full node table, and sends a network disconnection request to the corresponding consensus node based on the node address information to disconnect. Network connection with N consensus nodes.

Further, the node address information of the consensus nodes to be connected is obtained from the full node table, and a network connection is established between the consensus nodes to be connected based on the node address information to obtain a consensus network. As shown in FIG. 6 , it is assumed that at least two consensus nodes include a consensus node 6021 , a consensus node 6022 , a consensus node 6023 , and a consensus node 6024 . Address information, based on the node address information to establish network connections with other consensus nodes, assuming that the computer device is the consensus node 6022, the computer device obtains the node address information of the consensus node 6021 from the full node table 604, based on the node address of the consensus node 6021 information, send a network connection request to the consensus node 6021, the consensus node 6021 receives the network connection request, sends a network connection confirmation message to the computer device, and establishes a network connection between the computer device and the consensus node 6021 based on the network connection confirmation message. , a network connection with a consensus node to be connected (such as a consensus node 6023 or a consensus node 6024 ) can be established to obtain a consensus network 605 .

Further, the computer device can obtain the node identifiers of at least two consensus nodes from the full node table, and generate the consensus node table according to the node identifiers of the at least two consensus nodes. Optionally, the consensus weight of each consensus node can also be calculated. Added to the consensus node table. The computer equipment generates a consensus network block according to the consensus node table. If the consensus on the consensus network block is passed, the consensus network block is added to the node management block chain, and it is determined that at least two consensus nodes can form a consensus network. The connection status of at least two consensus nodes, and the network connection between each consensus node is established based on the connection status to generate a consensus network.

Further, the generation process of the full node table can be as follows:

Taking a network node as an example, the computer device can obtain the node network access request sent by the target network node; the node network access request includes the target node identifier, target identity label and target node address information of the target network node. The computer device can verify the target network node according to the target node identifier and the target node address information, for example, send a node confirmation request to the target network node based on the target node address information, and determine if the node confirmation message sent by the target network node is obtained. The target node address information of the target network node is legal; if the computer device has not obtained the node confirmation message sent by the target network node after the message feedback time has elapsed after the node confirmation request is sent, it is determined that the target node address information of the target network node is illegal. .

Wherein, if the target node address information of the target network node is illegal, the node network access request of the target network node is rejected, and a node address information exception message is sent to the target network node. If the target node address information of the target network node is legal, the target identity label is obtained; the computer equipment reaches a consensus on the target identity label, and if the consensus is passed, the node information block is generated according to the target node identity, target identity label and target node address information, Add the node information block to the node management blockchain; add the target node identification, target identity label and target node address information to the full node table. Optionally, the node's network access request may also include the target node signature of the target network node, and the computer device may obtain the public key of the target network node, and use the public key of the target network node to verify the signature of the target node. , and the consensus on the target identity label is passed, the node information block is generated according to the target node identification, target identity label, target node address information and target node signature, and the node information block is added to the node management blockchain; if the target network If the target node address information of the node is illegal, or the consensus on the target identity label fails, or the signature verification of the target node fails, the node access request of the target network node is rejected, and an abnormal message is sent to the target network node. For example, when the target When the target node address information of the network node is illegal, the abnormal message is the node address information abnormal message; when the consensus on the target identity label fails, the abnormal message is the label abnormal message; when the signature verification of the target node fails, the abnormal message The exception message is a signed exception message or the like.

Among them, when a consensus is performed on the target identity tag, the computer device can obtain the target identity tag, and if the target identity tag is a consensus tag, the target virtual mortgage rights and interests of the target identity tag are obtained; the threshold value of the consensus rights and interests is obtained, if the target virtual mortgage rights and interests are less than If the target virtual mortgage equity is greater than or equal to the consensus equity threshold, the target consensus weight of the target network node is generated according to the target virtual mortgage equity, and the target consensus weight is determined. The consensus on the target identity tag is passed. Optionally, the computer device may obtain the node cluster to which the target network node belongs, and perform consensus on the target identity label based on the node cluster, wherein, if the node cluster is the first node cluster, the target identity label may be a consensus label, data label or lightweight label; if the node cluster is the second node cluster, the target identity label can be a data label or a lightweight label; if the node cluster is a third node cluster, the target identity label can be a lightweight label . When the target identity label is consensus, the node cluster to which the target network node belongs can be obtained. If the node cluster to which the target network node belongs matches the target identity label, it is determined that the consensus on the target identity label has passed; if the target network node If the node cluster to which it belongs does not match the target identity label, it is determined that the consensus on the target identity label fails, and a label exception message is sent to the target network node. The management authority of the network nodes in the first node cluster is greater than the management authority of the network nodes in the second node cluster, and the management authority of the network nodes in the second node cluster is greater than the management authority of the network nodes in the third node cluster.

The target network node can obtain target node information, and the target node information can include any one or at least two of the target node identifier, target node address information, target identity label or target consensus weight, etc. The target network node can use the The private key of the target network node signs the target node information to generate the target node signature. Wherein, if the node's network access request does not include the target identity label or the target identity label is empty, then the target identity label is determined as a data label or a lightweight label. Specifically, the target consensus weight of the target network node can be obtained, If the target consensus weight belongs to the light weight range, the target identity label of the target network node is determined as the light weight label; if the target consensus weight belongs to the data weight range, the target identity label of the target network node is determined as the data Label.

The consensus weight in this application can be generated based on the data of the corresponding network node. Specifically, taking a network node as an example, a computer device can obtain the virtual mortgage rights and historical consensus times of the network node. According to the virtual mortgage rights and the historical consensus times to determine the consensus weight of the network node. For example, the virtual mortgage rights and historical consensus times can be processed based on the weight algorithm to obtain the consensus weight of the network node. Optionally, the computer device may also obtain the virtual mortgage rights, historical consensus times and random numbers of the network nodes to determine the consensus weights of the network nodes, wherein the virtual mortgage rights can be virtual assets provided by the network nodes, and the historical consensus The number of times may be the number of times the network node participates in the consensus, or the number of cycles of the consensus cycle in which the network node participates, and so on. The random number may be generated according to the system network time, the maximum block height in the node management blockchain, or the hash value of a certain block in the node management blockchain.

Optionally, there is a mortgage account in the blockchain network, virtual assets can be obtained from the account of the network node, the virtual asset is added to the mortgage account, and the virtual asset is used as the virtual mortgage rights and interests of the corresponding network node; or , the virtual asset can be cached. After the verification of the network node is passed, the virtual asset is added to the mortgage account. If the verification of the network node fails, the virtual asset is returned to the account of the corresponding network node.

Step S404, when the logout request of the to-be-processed network node is obtained, the consensus weight of the to-be-processed network node is obtained from the full node table, the consensus weight of the to-be-processed network node is sent to the to-be-processed network node, and the full node is deleted The pending network nodes in the table.

In this embodiment of the present application, if the to-be-processed network node that initiates the withdrawal request belongs to the consensus network, the consensus network is updated, wherein deleting the to-be-processed network node in the full node table refers to deleting the to-be-processed network node in the entire node table. All data in the node table (that is, the node information of the network node to be processed). Specifically, the computer device can obtain the identity label of the network node to be processed from the full node table based on the network withdrawal request, and if the identity label of the network node to be processed is a consensus label, trigger an update request for the consensus network, execute The above steps S401 to S403 are to update the consensus network; or, look up the to-be-processed network node from the consensus node table, and if the to-be-processed network node is found in the consensus node table, trigger an update request for the consensus network, and execute the steps The process from S401 to step S403 is to update the consensus network. When an update request for the consensus network is triggered, or the identity label of the network node to be processed is not a consensus label, or the network node to be processed does not exist in the consensus node table, the computer device can obtain the network node from the full node table. The consensus weight of the network node to be processed, the consensus weight of the network node to be processed includes the virtual mortgage rights and interests of the network nodes to be processed, and the virtual mortgage rights and interests are sent to the network nodes to be processed. Wherein, if the virtual mortgage interest is a virtual asset, the virtual asset is sent to the account of the network node to be processed. Further, the data related to the network node to be processed (ie, the node information of the network node to be processed) in the full node table is deleted. Wherein, the network node to be processed belongs to at least two network nodes. Optionally, the data related to the network node to be processed in the full node table can also be deleted first, and then it is detected whether the network node to be processed belongs to the consensus network. If the network node to be processed belongs to the consensus network, an update for the consensus network is triggered. Request to update the consensus network.

Wherein, when acquiring the logout request of the network node to be processed, the computer device can perform identity verification on the network node that sent the logout request. The network node requested by the network request is the network node requested by the network withdrawal request, obtains the consensus weight of the network node to be processed from the full node table, sends the consensus weight of the network node to be processed to the network node to be processed, and deletes the full node The pending network nodes in the table. For example, when network node A sends a logout request, the logout request is used to indicate that network node B wants to log out of the blockchain network. When the computer device obtains the logout request sent by network node A, it authenticates network node A. If it is found that the network node A requests to withdraw other network nodes from the network, it can be determined that the identity verification of the network node A fails, and optionally, a node exception message can be sent to the network node A.

Wherein, the full node table includes the node signature of each network node. Further, if an abnormal node is detected from at least two network nodes, the public key of the abnormal node is obtained. Use the public key of the abnormal node to verify the signature of the node corresponding to the abnormal node in the full node table. If the verification is passed, it means that the abnormal node has not been replaced, and a node confirmation message is sent to the abnormal node. The node confirmation message is used for Obtain abnormal data from the abnormal node; if the node signature verification of the abnormal node fails, it means that the abnormal node is not the original network node in the full node table, or the abnormal node is unknown and disconnected from the abnormal node. Network connection, delete the data associated with the abnormal node (that is, the node information of the abnormal node) from the full node table.

In the embodiment of the present application, the consensus weight of each network node is obtained from the full node table by obtaining at least two network nodes in the blockchain network; based on the consensus weight of each network node, at least two network nodes are obtained from the at least two network nodes. Two consensus nodes; detect the connection status of at least two consensus nodes, record the consensus node whose connection status is disconnected as the consensus node to be connected, and obtain the node address information of the consensus node to be connected from the full node table. The address information establishes a network connection between the consensus nodes to be connected to obtain a consensus network. Through the above process, a full node table is introduced into the blockchain network, and the full node table stores the node information (such as consensus weight) of each network node in the blockchain network. When the network nodes change, the data of the changed network nodes can be directly obtained from the full node table, and a consensus network can be established based on the full node table, without the need to re-count the node information of each network node, and without the need to re-implement the blockchain network. The deployment of the blockchain network reduces the time and resources required to update the blockchain network when the blockchain network changes, and improves the flexibility of network node management in the blockchain network.

Further, referring to FIG. 7 , FIG. 7 is a schematic diagram of a block chain node management apparatus provided by an embodiment of the present application. The above-mentioned blockchain node management device may be a computer program (including program code) running in a computer device, for example, the blockchain node management device is an application software; the device may be used to execute the method provided by the embodiments of the present application corresponding steps in . As shown in FIG. 7 , the block chain node management apparatus 700 can be used for the computer equipment in the embodiment corresponding to FIG. 4 . Specifically, the block chain node management apparatus 700 may include: a weight acquisition module 11 , a node selection Module 12 , connection establishment module 13 and node withdrawal module 14 .

The weight obtaining module 11 is used to obtain at least two network nodes in the blockchain network, and obtain the consensus weight of each network node from the full node table;

The node selection module 12 is configured to obtain at least two consensus nodes from at least two network nodes based on the consensus weight of each network node;

The connection establishment module 13 is used to detect the connection status of at least two consensus nodes, record the consensus node whose connection status is disconnected as the consensus node to be connected, and obtain the node address information of the consensus node to be connected from the full node table, Establish network connections between consensus nodes to be connected based on node address information to obtain a consensus network;

The node de-networking module 14 is configured to obtain the consensus weight of the to-be-processed network node from the full node table when the de-network request of the to-be-processed network node is obtained, and send the consensus weight of the to-be-processed network node to the to-be-processed network node, Delete the to-be-processed network node in the full node table, if the to-be-processed network node that initiates the withdrawal request belongs to the consensus network, update the consensus network; the to-be-processed network node belongs to at least two network nodes.

Among them, the full node table includes the identity label and consensus weight of each network node;

The weight acquisition module 11 includes:

The label obtaining unit 111 is configured to obtain at least two network nodes in the blockchain network, obtain the identity label of each network node from the full node table, and obtain the network node whose identity label is the consensus label from the at least two network nodes , get candidate consensus nodes;

a weight obtaining unit 112, configured to obtain consensus weights of candidate consensus nodes from the full node table;

The node selection module 12 is specifically used for:

Obtain the number of consensus nodes, and determine N consensus nodes from the candidate consensus nodes based on the consensus weight of the candidate consensus nodes and the number of consensus nodes; the number of consensus nodes is used to represent the number of consensus nodes that form a consensus network, and N is the number of consensus nodes.

Among them, the node selection module 12 is specifically used for:

Obtain the number of consensus nodes, sort at least two network nodes based on the consensus weight of each network node, and obtain N consensus nodes from at least two network nodes according to the sorting result; the number of consensus nodes is used to represent the consensus nodes that constitute the consensus network , and N is the number of consensus nodes.

Wherein, the full node table includes the identity label of each network node;

In terms of detecting the connection status of at least two consensus nodes, and recording the consensus node whose connection status is disconnected as the consensus node to be connected, the connection establishment module 13 includes:

The state determination unit 131 is configured to obtain the identity labels corresponding to the N consensus nodes from the full node table, and determine the connection state of the consensus node whose identity label is not the consensus label as the disconnected state;

The consensus determination unit 132 is configured to record the consensus nodes whose connection state is in the disconnected state as the consensus nodes to be connected.

Wherein, the device 700 further includes:

The history acquisition module 15 is used to acquire historical consensus nodes whose identity labels are consensus labels from the full node table;

The label update module 16 is used to disconnect the network connection of the historical consensus node if the historical consensus node does not belong to N consensus nodes, update the identity label of the historical consensus node in the full node table to the data label, and perform detection of at least two The connection status of the consensus node, the consensus node whose connection status is disconnected is recorded as the step to be connected to the consensus node.

Wherein, the device 700 further includes:

The table generation module 17 is configured to obtain the node identifiers of at least two consensus nodes from the full node table, and generate a consensus node table according to the node identifiers of the at least two consensus nodes;

The data storage module 18 is used for generating a consensus network block according to the consensus node table. If the consensus on the consensus network block is passed, the consensus network block is added to the node management blockchain, and the connection of at least two consensus nodes is detected. Status steps.

Wherein, the device 700 further includes:

The weight determination module 19 is used to obtain the virtual mortgage rights and historical consensus times of network nodes, and determine the consensus weights of network nodes according to the virtual mortgage rights and historical consensus times;

The data uploading module 20 is used to add the consensus weight to the node management block chain if the consensus on the consensus weight is passed, and add the association relationship between the consensus weight and the network nodes to the full node table.

Wherein, the device 700 further includes:

The request obtaining module 21 is used to obtain the node network access request sent by the target network node; the node network access request includes the target node identifier, the target identity label and the target node address information of the target network node;

The node verification module 22 is used to verify the target network node according to the target node identifier and the target node address information, and obtain the target identity label if the target node address information of the target network node is legal;

The label verification module 23 is used for consensus on the target identity label. If the consensus is passed, a node information block is generated according to the target node identification, target identity label and target node address information, and the node information block is added to the node management blockchain. middle;

The node adding module 24 is used for adding target node identification, target identity label and target node address information to the full node table.

Among them, in terms of consensus on the target identity tag, the tag verification module 23 includes:

an equity acquisition unit 231, configured to acquire the target virtual mortgage equity of the target identity label if the target identity label is a consensus label;

The message sending unit 232 is configured to obtain a consensus equity threshold. If the target virtual mortgage equity is less than the consensus equity threshold, it is determined that the consensus on the target identity label has failed, and a label exception message is sent to the target network node;

The verification passing unit 233 is configured to generate the target consensus weight of the target network node according to the target virtual mortgage equity if the target virtual mortgage equity is greater than or equal to the consensus equity threshold, and determine that the consensus on the target identity label is passed.

Wherein, the full node table also includes the node signature of each network node;

The apparatus 700 also includes:

a public key acquisition module 25, configured to acquire the public key of the abnormal node if an abnormal node is detected from at least two network nodes;

The node signature verification module 26 is used to verify the signature of the node corresponding to the abnormal node in the full node table by using the public key of the abnormal node, and if the signature is passed, send a node confirmation message to the abnormal node; The abnormal node obtains abnormal data;

The node signature verification module 26 is further configured to disconnect the network connection with the abnormal node if the node signature verification of the abnormal node fails, and delete the data associated with the abnormal node from the full node table.

The embodiments of the present application describe a blockchain node management device. The above device uses any one of at least two network nodes to manage network nodes in a blockchain network, including the generation of consensus networks and node information. The full node table is introduced into the blockchain network, and the full node table stores the node information (such as consensus weight) of each network node in the blockchain network. When the network nodes change, the data of the changed network nodes can be directly obtained from the full node table, and a consensus network can be established based on the full node table, without the need to re-count the node information of each network node, and without the need to re-implement the blockchain network. The deployment of the blockchain network reduces the time and resources required to update the blockchain network when the blockchain network changes, and improves the flexibility of network node management in the blockchain network.

Referring to FIG. 8, FIG. 8 is a schematic structural diagram of a computer device provided by an embodiment of the present application. As shown in FIG. 8 , the computer device 800 in this embodiment of the present application may include: one or more processors 801 , a memory 802 , and an input-output interface 803 . The above-mentioned processor 801 , memory 802 and input/output interface 803 are connected through a bus 804 . The memory 802 is used to store a computer program, and the computer program includes program instructions, and the input and output interface 803 is used for data interaction between each network node in the blockchain; the processor 801 is used to execute the program instructions stored in the memory 802. The execution is as follows operate:

Obtain at least two network nodes in the blockchain network, and obtain the consensus weight of each network node from the full node table;

Obtain at least two consensus nodes from at least two network nodes based on the consensus weight of each network node;

Detect the connection status of at least two consensus nodes, record the consensus node whose connection status is disconnected as the consensus node to be connected, and obtain the node address information of the consensus node to be connected from the full node table. Establish network connections between consensus nodes to obtain a consensus network;

When the logout request of the network node to be processed is obtained, the consensus weight of the network node to be processed is obtained from the full node table, the consensus weight of the network node to be processed is sent to the network node to be processed, and the pending network node is deleted from the full node table. The network node, if the pending network node that initiates the withdrawal request belongs to the consensus network, the consensus network is updated; the pending network node belongs to at least two network nodes.

In some feasible implementation manners, the above-mentioned processor 801 may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits ( application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 802 may include read-only memory and random access memory, and provides instructions and data to the processor 801 and the input-output interface 803 . A portion of memory 802 may also include non-volatile random access memory. For example, memory 802 may also store device type information.

In specific implementation, the above-mentioned computer can execute the implementation manner provided by each step in FIG. 4 through its built-in functional modules. For details, please refer to the implementation manner provided by each step in FIG. 4 , which will not be repeated here.

The embodiments of the present application provide a computer device including: a processor, an input and output interface, and a memory, and the processor obtains computer instructions in the memory, executes each step of the method shown in FIG. 4 above, and manages blockchain nodes operate. Through the computer instructions in the memory, the processor performs the following steps: obtaining at least two network nodes in the blockchain network, obtaining the consensus weight of each network node from the full node table; based on the consensus weight of each network node, from Obtain at least two consensus nodes from at least two network nodes; detect the connection status of at least two consensus nodes, record the consensus node whose connection status is disconnected as the consensus node to be connected, and obtain the consensus to be connected from the full node table The node address information of the node, based on the node address information, establishes a network connection between the consensus nodes to be connected to obtain a consensus network. Through the above process, a full node table is introduced into the blockchain network, and the full node table stores the node information (such as consensus weight) of each network node in the blockchain network. When the network nodes change, the data of the changed network nodes can be directly obtained from the full node table, and a consensus network can be established based on the full node table, without the need to re-count the node information of each network node, and without the need to re-implement the blockchain network. The deployment of the blockchain network reduces the time and resources required to update the blockchain network when the blockchain network changes, and improves the flexibility of network node management in the blockchain network.

Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by the above-mentioned processor, each step in FIG. 4 can be implemented. For the provided blockchain node management method, specific reference may be made to the implementation manner provided by each step in FIG. 4 above, which will not be repeated here. In addition, the description of the beneficial effects of using the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiments involved in the present application, please refer to the description of the method embodiments of the present application. By way of example, program instructions may be deployed to execute on one computer device, or on multiple computer devices located at one site, or alternatively, on multiple computer devices distributed across multiple sites and interconnected by a communications network Implemented, multiple computing devices distributed in multiple locations and interconnected by a communication network can form a blockchain network.

The above-mentioned computer-readable storage medium may be the blockchain node management apparatus provided in any of the foregoing embodiments or an internal storage unit of the above-mentioned computer, such as a hard disk or a memory of the computer. The computer-readable storage medium may also be an external storage device of the computer, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash memory card ( flash card), etc. Further, the computer-readable storage medium may also include both an internal storage unit of the computer and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer. The computer-readable storage medium can also be used to temporarily store data that has been or will be output.

Embodiments of the present application also provide a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in the various optional manners in FIG. The management of network nodes in the network, including the generation of consensus networks and the management of node information for network nodes, etc., among which, a full node table is introduced into the blockchain network, and the full node table stores each network in the blockchain network. The node information of the node (such as consensus weight), etc. When each network node in the blockchain network changes, the data of the changed network node can be directly obtained from the full node table, and a consensus network can be established based on the full node table. , without the need to re-statistic the node information of each network node, without the need to re-implement the deployment of the blockchain network, reducing the time and resources spent on updating the blockchain network when the blockchain network changes, improving the Flexibility in the management of network nodes in a blockchain network.

The terms "first", "second" and the like in the description and claims of the embodiments of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order. Furthermore, the term "comprising" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product or device comprising a series of steps or units is not limited to the listed steps or modules, but optionally also includes unlisted steps or modules, or optionally also includes For other step units inherent to these processes, methods, apparatus, products or equipment.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. Interchangeability, the above description has generally described the components and steps of each example in terms of function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

The methods and related apparatuses provided by the embodiments of the present application are described with reference to the method flowcharts and/or schematic structural diagrams provided in the embodiments of the present application. Specifically, each process and/or the schematic structural diagrams of the method flowcharts and/or structural schematic diagrams can be implemented by computer program instructions. or blocks, and combinations of processes and/or blocks in flowcharts and/or block diagrams. 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 device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce a function An apparatus for implementing the functions specified in one or more of the flowcharts and/or one or more blocks of the structural diagrams. These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in one or more of the flowcharts and/or one or more blocks of the structural diagram. These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the block or blocks of the flowchart and/or structural representation.

The above disclosures are only the preferred embodiments of the present application, and of course, the scope of the rights of the present application cannot be limited by this. Therefore, equivalent changes made according to the claims of the present application are still within the scope of the present application.

Claims (15)

1. A block link point management method, the method comprising:

acquiring at least two network nodes in a block chain network, and acquiring a consensus weight of each network node from a full node table; the consensus weights comprise virtual mortgage interests;

acquiring at least two consensus nodes from the at least two network nodes based on the consensus weight of each network node;

detecting the connection state of the at least two consensus nodes, recording the consensus node with the connection state being a disconnection state as a consensus node to be connected, acquiring node address information of the consensus node to be connected from the whole node table, and establishing network connection between the consensus nodes to be connected based on the node address information to obtain a consensus network;

when a network quitting request of a network node to be processed is obtained, acquiring a consensus weight of the network node to be processed from the whole node table, sending a virtual mortgage interest in the consensus weight of the network node to be processed to the network node to be processed, deleting the network node to be processed in the whole node table, and updating the consensus network if the network node to be processed initiating the network quitting request belongs to the consensus network; the network node to be processed belongs to the at least two network nodes.

2. The method of claim 1, wherein the full node table includes an identity label and a consensus weight for each of the network nodes;

the acquiring at least two network nodes in the blockchain network, acquiring the consensus weight of each network node from the full node table, includes:

acquiring at least two network nodes in a block chain network, acquiring an identity label of each network node from the full node table, and acquiring the network nodes of which the identity labels are consensus labels from the at least two network nodes to obtain candidate consensus nodes;

acquiring consensus weights of the candidate consensus nodes from the full node table;

the obtaining at least two consensus nodes from the at least two network nodes based on the consensus weight of each network node comprises:

acquiring the number of consensus nodes, and determining N consensus nodes from the candidate consensus nodes based on the consensus weights of the candidate consensus nodes and the number of the consensus nodes; the number of the consensus nodes is used for representing the number of the consensus nodes forming the consensus network, and N is the number of the consensus nodes.

3. The method of claim 1, wherein the obtaining at least two consensus nodes from the at least two network nodes based on the consensus weight for each network node comprises:

acquiring the number of consensus nodes, sequencing the at least two network nodes based on the consensus weight of each network node, and acquiring N consensus nodes from the at least two network nodes according to a sequencing result; the number of the consensus nodes is used for representing the number of the consensus nodes forming the consensus network, and N is the number of the consensus nodes.

4. The method of claim 3, wherein the full node table includes an identity tag for each of the network nodes;

the detecting the connection state of the at least two consensus nodes, and recording the consensus node with the connection state being the disconnection state as the consensus node to be connected, includes:

acquiring identity labels corresponding to the N consensus nodes from the full node table, and determining the connection state of the consensus nodes of which the identity labels are not the consensus labels as a connection disconnection state;

and recording the common identification node with the connection state being the disconnection state as a common identification node to be connected.

5. The method of claim 4, wherein the method further comprises:

acquiring a history consensus node with the identity label as a consensus label from the whole node table;

if the historical consensus nodes do not belong to the N consensus nodes, disconnecting the network connection of the historical consensus nodes, updating the identity labels of the historical consensus nodes in the whole node table to be data labels, executing the step of detecting the connection states of the at least two consensus nodes, and recording the consensus nodes with the connection states being the connection disconnection states as the consensus nodes to be connected.

6. The method of claim 1, wherein the method further comprises:

acquiring node identifications of the at least two consensus nodes from the full node table, and generating a consensus node table according to the node identifications of the at least two consensus nodes;

and generating a consensus network block according to the consensus node table, if the consensus passes through the consensus network block, adding the consensus network block into a node management block chain, and executing the step of detecting the connection state of the at least two consensus nodes.

7. The method of claim 1, wherein the method further comprises:

acquiring the virtual mortgage interest and the historical consensus number of the network node, and determining the consensus weight of the network node according to the virtual mortgage interest and the historical consensus number;

and if the consensus weight passes the consensus, adding the consensus weight into a node management block chain, and adding the association relation between the consensus weight and the network node into the full node table.

8. The method of claim 1, wherein the method further comprises:

acquiring a node network access request sent by a target network node; the node network access request comprises a target node identification, a target identity label and target node address information of the target network node;

verifying the target network node according to the target node identification and the target node address information, and if the target node address information of the target network node is legal, acquiring the target identity tag;

performing consensus on the target identity tag, if the consensus passes, generating a node information block according to the target node identifier, the target identity tag and the target node address information, and adding the node information block to a node management block chain;

and adding the target node identification, the target identity label and the target node address information into the full node table.

9. The method of claim 8, wherein the consensus on the target identity tag comprises:

if the target identity label is a consensus label, acquiring a target virtual mortgage right of the target identity label;

acquiring a consensus right interest threshold, if the target virtual mortgage right interest is smaller than the consensus right interest threshold, determining that the target identity label consensus fails, and sending a label abnormal message to the target network node;

and if the target virtual mortgage interest is larger than or equal to the consensus interest threshold, generating a target consensus weight of the target network node according to the target virtual mortgage interest, and determining that the target identity label is agreed.

10. The method of claim 1, wherein the full node table further includes a node signature for the each network node;

the method further comprises the following steps:

if an abnormal node is detected from the at least two network nodes, acquiring a public key of the abnormal node;

adopting the public key of the abnormal node to check the signature of the node corresponding to the abnormal node in the whole node table, and if the signature passes, sending a node confirmation message to the abnormal node; the node confirmation message is used for acquiring abnormal data from the abnormal node;

and if the node signature of the abnormal node fails to pass the verification, disconnecting the network connection with the abnormal node, and deleting the data associated with the abnormal node from the full node table.

11. A block link point management apparatus, the apparatus comprising:

the weight acquisition module is used for acquiring at least two network nodes in the block chain network and acquiring the consensus weight of each network node from the whole node table; the consensus weights comprise virtual mortgage interests;

the node selection module is used for acquiring at least two consensus nodes from the at least two network nodes based on the consensus weight of each network node;

the connection establishing module is used for detecting the connection state of the at least two consensus nodes, recording the consensus node with the connection state being in a disconnection state as a consensus node to be connected, acquiring the node address information of the consensus node to be connected from the whole node table, and establishing network connection between the consensus nodes to be connected based on the node address information to obtain a consensus network;

the node network quitting module is used for acquiring the consensus weights of the network nodes to be processed from the whole node table when network quitting requests of the network nodes to be processed are acquired, sending the virtual mortgage benefits in the consensus weights of the network nodes to be processed to the network nodes to be processed, deleting the network nodes to be processed in the whole node table, and updating the consensus network if the network nodes to be processed initiating the network quitting requests belong to the consensus network; the network node to be processed belongs to the at least two network nodes.

12. The apparatus of claim 11, wherein the full node table comprises an identity label and a consensus weight for each of the network nodes;

the weight obtaining module comprises:

a tag obtaining unit, configured to obtain at least two network nodes in a block chain network, obtain an identity tag of each network node from the full node table, and obtain a network node whose identity tag is a consensus tag from the at least two network nodes, so as to obtain a candidate consensus node;

a weight obtaining unit, configured to obtain a consensus weight of the candidate consensus node from the full node table;

the node selection module is specifically configured to:

acquiring the number of consensus nodes, and determining N consensus nodes from the candidate consensus nodes based on the consensus weights of the candidate consensus nodes and the number of the consensus nodes; the number of the consensus nodes is used for representing the number of the consensus nodes forming the consensus network, and N is the number of the consensus nodes.

13. The apparatus of claim 11, wherein the node selection module is specifically configured to:

acquiring the number of consensus nodes, sequencing the at least two network nodes based on the consensus weight of each network node, and acquiring N consensus nodes from the at least two network nodes according to a sequencing result; the number of the consensus nodes is used for representing the number of the consensus nodes forming the consensus network, and N is the number of the consensus nodes.

14. A computer device comprising a processor, a memory, an input output interface;

the processor is connected to the memory and the input/output interface respectively, wherein the input/output interface is used for data interaction between network nodes in a block chain, the memory is used for storing program codes, and the processor is used for calling the program codes to execute the method of any one of claims 1 to 10.

15. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions which, when executed by a processor, perform the method of any of claims 1-10.

Images