CN115293769B - Dynamic management and check node system based on block chain - Google Patents
Dynamic management and check node system based on block chain Download PDFInfo
- Publication number
- CN115293769B CN115293769B CN202211219028.5A CN202211219028A CN115293769B CN 115293769 B CN115293769 B CN 115293769B CN 202211219028 A CN202211219028 A CN 202211219028A CN 115293769 B CN115293769 B CN 115293769B
- Authority
- CN
- China
- Prior art keywords
- node
- transaction
- height
- record
- block
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3825—Use of electronic signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/405—Establishing or using transaction specific rules
Abstract
The application relates to the technical field of block chains, and provides a dynamic management and check node system based on a block chain, which comprises: the system comprises a block chain cluster, a transaction request node and a packaging node, wherein the block chain cluster is provided with a block chain account book node, the transaction request node and the packaging node; the blockchain ledger node is configured to: recording all information in the block chain cluster; the transaction request node is configured to: sending a transaction request to the blockchain ledger node; the packing node is configured to: packaging transactions in the blockchain cluster into blocks; wherein the node transaction types include: adding a node into a transaction, quitting the transaction, freezing the transaction and unfreezing the transaction; the history tracing of the node operation is conveniently carried out through the node operation history record table, the operation of what height is clearly known is displayed through the sorting mode of the block height, the effective node number is conveniently calculated to carry out the verification operation of the related node information, and the decentralization of the node management is realized.
Description
Technical Field
The present application relates to the field of block chain technologies, and in particular, to a dynamic management and check node system based on a block chain.
Background
The block chain of alliance is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. Essentially a database, is a string of blocks associated using cryptography, each block containing information about a batch of network transactions for verifying the validity of the information and generating the next block. A federation blockchain is a data structure used to store transactions, and the compute nodes of the federation blockchain may be referred to simply as nodes.
In the existing block chain scheme of the alliance, the relationship between nodes is a peer-to-peer relationship, the identity authentication basis of information interaction between the nodes is confirmed through a digital certificate, the addition and the exit of the nodes are generally controlled through operation authority given by an administrator at present, the administrator agrees with the addition of the nodes or the exit of the nodes, and after an addition or exit instruction is initiated to a block chain network, the node executes the operation action of the instruction, which is equivalent to a centralized server management mode.
The centralized management mode, the authentication method, the reliability and the safety of the management mode depend on the individual administrator, and the problems of single point of failure, poor expansibility, complex management and application and the like exist. Therefore, it is necessary to achieve decentralized federation blockchain, improve operation efficiency, and reduce centralized service management of single-use administrator operation authority.
Disclosure of Invention
In order to solve the problems that an authentication method, reliability and safety all depend on an administrator in a centralized management mode, and single-point faults, poor expansibility, complex management and application and the like exist, the invention provides a dynamic management and check node system based on a block chain, which comprises the following steps: the system comprises a block chain cluster, a transaction request node and a packaging node, wherein the block chain cluster is provided with a block chain account book node, the transaction request node and the packaging node;
the block chain ledger node is configured to: recording all information in the block chain cluster;
the transaction requesting node is configured to: sending a transaction request to the blockchain ledger node;
the packing node is configured to: transactions in a blockchain cluster are packaged into blocks.
Wherein the node transaction types include: adding the node into the transaction, quitting the node, freezing the node and unfreezing the node.
The system is configured to perform a method comprising the steps of:
a transaction request node initiates a node transaction meeting a node transaction rule to the blockchain ledger node, wherein the node transaction comprises a signature of the transaction request node;
other nodes in the block chain cluster check the signature of the transaction request node and select whether to receive the node transaction;
when other nodes in the blockchain cluster select to receive the number of the node transactions which meets the requirement of the consensus rule, the node transactions are successfully consensus and executed by all nodes in the blockchain cluster;
when the transaction request node executes the transaction, generating a transaction record in a node operation history record table, wherein the transaction record comprises the block height corresponding to the node transaction; the node operation history table also records the node operation time, the node operation starting height, the node operation ending height and the node transaction type of the nodes in the block chain cluster;
the block chain account book node saves the block height and executes the data synchronization function of the historical block;
when a new transaction request node initiates the node to join the transaction, the step of checking the signature is repeatedly executed;
when the packaging node performs transaction packaging, inquiring effective nodes under the block height according to the current block height in the node operation history table to generate an effective node list and acquire the number of the effective nodes;
calculating the lowest vote number of the current block height according to the number of the effective nodes, and initiating QC verification;
and when the node vote number in the QC verification meets the minimum vote number, completing transaction packaging.
Further, the node join transaction is configured to: adding the target node to the blockchain cluster;
the node logout transaction is configured to: causing the target node to exit the blockchain cluster;
the node freeze transaction is configured to: freezing the target node, wherein the frozen target node cannot acquire the data operation request on the link;
the node unfreezing transaction is configured to: and enabling the target node to be restored to the state capable of acquiring the data operation request on the chain from the frozen state.
Further, the step of determining the valid node under the block height includes:
acquiring all node operation records of any node, and searching the maximum record of which the corresponding node operation height is smaller than the block height in the node adding and quitting operation;
if the maximum node operation ending height of the node in the joining and exiting operation is 0 or greater than the block height, inquiring whether the node operation type is the node freezing and unfreezing operation in all records of which the maximum node operation ending height is less than the block height, wherein the node freezing and unfreezing operation height is less than the record of the block height;
if not, the node is a valid node;
if so, checking whether the corresponding node operation ending height is not 0 in the record of the node, wherein the node operation type is the largest one of the starting heights corresponding to the operations of freezing and unfreezing the node, and the node operation ending height is smaller than the block height, if so, the node is an effective node.
Further, the step of determining the valid node under the block height further includes:
acquiring all node operation records of any node, and searching the maximum record of which the corresponding node operation height is less than the block height in the node adding and quitting operation;
and if the corresponding recorded node operation ending height is not 0 and is smaller than the block height, judging that the node is not a valid node.
Further, the step of determining the valid node under the block height further includes:
if the node operation type is found to be the record of node freezing, and the node operation type is the record of the largest one of the starting heights corresponding to the operations of node freezing and unfreezing, whether the corresponding node operation ending height is 0 or larger than the block height is judged, and if yes, the node is not an effective node.
Further, the node transaction rule includes:
when a node exits a transaction request sent by a node in a block chain cluster is obtained, inquiring whether a record with the maximum node operation height corresponding to the node adding and exiting operations, which is the node operation type, in a historical block of the node is the node adding transaction record or not;
if yes, executing the node to quit the transaction; if not, stopping the node from quitting the transaction and feeding back.
Further, the node transaction rule further includes:
when a node sends a node join transaction request in a block chain cluster, inquiring whether a node operation record exists or not, and if not, executing the node access transaction;
if so, inquiring whether a record with the maximum node operation height corresponding to the node adding and quitting operation in the history block of the node is the transaction record of the node quitting;
if yes, executing the node joining transaction; if not, stopping the node from joining the transaction and feeding back.
Further, the node transaction rule further includes:
when a node freezing transaction request is sent by a certain node in an acquired block chain cluster, inquiring whether a record with the maximum node operation height corresponding to the node adding and quitting operation, which is the node operation type, in a historical block of the node is the node adding transaction record or not;
if not, stopping the node from joining the transaction and feeding back;
if yes, inquiring whether the node operation type is the node freezing and unfreezing operation, and if not, executing the node freezing transaction;
if yes, inquiring whether the record of the largest one of the corresponding node operation heights is the node unfreezing transaction record or not if the node operation type is the node freezing operation and the unfreezing operation exists;
if yes, executing the node freezing transaction; if not, stopping the node to freeze the transaction and feeding back.
Further, the node transaction rule further includes:
when a node unfreezing transaction request is sent by a certain node in an acquired block chain cluster, inquiring whether a record with the maximum node operation height, corresponding to node adding and quitting operations, in the operation type of the node in a historical block of the node is the transaction record of the node adding;
if not, stopping the node from joining the transaction and feeding back;
if yes, inquiring whether the node operation type is the node freezing and unfreezing operation, and if not, stopping the node freezing transaction and feeding back;
if so, inquiring whether the record of the largest one of the corresponding node operation heights is the node freezing transaction record or not if the node operation type is the node freezing operation and the unfreezing operation;
if yes, executing the node unfreezing transaction; if not, stopping the unfreezing transaction of the node and feeding back. The invention provides a dynamic management and check node system based on a block chain. The advantages are that: the decentralized center of block chain management is realized, historical operation tracing of operation is facilitated through historical operation records of node operation, what operation is performed at what height is clearly known through a height sorting mode, and the number of effective nodes is conveniently calculated to perform the checking operation of related node information; each initiation is recorded on the chain through an intelligent contract medium in a system transaction form, so that the decentralized processing is realized, and other attributes of the block chain, such as tamper resistance and the like, are also given; when other node blocks are synchronized with any other node blocks after the synchronization, the effective node number is conveniently and quickly calculated through the operation record table, verification and verification of relevant blocks, transactions and intelligent contracts are carried out, and the legality is guaranteed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention. It is obvious that the drawings in the following description are only some of the embodiments of the invention, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.
FIG. 1 is a block chain based dynamic management and check node system of the present application;
FIG. 2 is a block chain based dynamic management and check node system operational height record for a node of the present application;
FIG. 3 is a schematic flow chart of a method performed by a blockchain based dynamic management and check node system according to the present application;
fig. 4 is a schematic flowchart of a process for determining an effective node by a block chain-based dynamic management and check node system according to the present application.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. In the following description, numerous specific details are provided to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, steps, etc. In other instances, well-known techniques have not been shown or described in detail to avoid obscuring aspects of embodiments of the invention.
As shown in fig. 1, the present application provides a block chain-based dynamic management and check node system, including: the block chain cluster in this application is a chain formed by blocks, and each block stores certain information, and the certain information is connected into the chain according to the time sequence generated by each block. This chain is maintained in all servers, and as long as one server can work in the entire system, the entire blockchain cluster is secure. These servers, referred to as nodes in the blockchain cluster, provide storage and computational support for the entire blockchain cluster. Specifically, the node in the present application includes: the system comprises a block chain account book node, a transaction request node and a packaging node. Different nodes on a blockchain cluster are configured with different functionality.
Wherein the block chain ledger node is configured to: recording all information in the block chain cluster; the transaction request node is configured to: sending a transaction request to the blockchain ledger node; the packing node is configured to: transactions in a blockchain cluster are packaged into blocks.
The transaction request node can be any node on the blockchain cluster, and can be used as the transaction request node as long as the node has the operation of transaction request; and the packing nodes are block chains, and select a leader node to trade a packing block under the condition that all the nodes meet the consensus requirement through a consensus algorithm. The transaction types in the blockchain cluster are multiple, and specifically, the node transaction types include: adding the node into the transaction, quitting the node, freezing the node and unfreezing the node.
Further, the node join transaction is configured to: adding the target node to the blockchain cluster; the node logout transaction is configured to: causing the target node to exit the blockchain cluster; the node freeze transaction is configured to: freezing the target node, wherein the frozen target node cannot acquire a data operation request on the link; the node unfreezing transaction is configured to: and enabling the target node to be restored to the state capable of acquiring the data operation request on the chain from the frozen state.
The system of the application is a transaction according to the joining (quitting, freezing, unfreezing and the like) of the nodes, and needs to form consensus among the nodes of the alliance chain according to the fact that a certain block is effectively in a block chain cluster intelligent contract transaction mode and record the consensus on the block to complete the joining (quitting, freezing, unfreezing and the like) of the nodes, so that decentralization is realized, the operation efficiency is improved, and the centralized service management mode of the operation authority of a single use administrator is also reduced. For example, the node joins the blockchain network at a blockchain height of 5, after which the node is a valid node and participates in transaction signature verification generated by the blockchain, and before the height of 5, the node does not participate in signature verification of the transaction. As shown in fig. 2, fig. 2 is a record of the operation height of a certain node in the present application. It can be seen that the node enters at 1, exits at 10, then enters again at 15, is frozen at 20, thawed at 40, and exits at 60.
Specifically, in order to improve the security and flexibility of the dynamic management node of the blockchain cluster, the system is configured to execute the following method, as shown in fig. 3, where the method includes the steps of:
s100, a transaction request node initiates a node transaction meeting a node transaction rule to the block chain account node, wherein the node transaction comprises a signature of the transaction request node;
further, in order to realize effective management of the nodes, the node transaction rules need to be specified to avoid invalid transactions, wherein the transaction rules mainly include four points:
firstly, the method comprises the following steps: before the node quits the transaction, the latest joining and quitting operation record must be the joining record.
Specifically, the method comprises the following steps:
when a node quitting transaction request is sent by a certain node in a block chain cluster, inquiring whether a record with the maximum node operation height corresponding to the node adding and quitting operation in the node operation type in a historical block of the node is the node adding transaction record or not;
if yes, executing the node to quit the transaction; if not, stopping the node from quitting the transaction and feeding back.
Secondly, the method comprises the following steps: before a node joins a transaction, the record of the last joining and exiting operation must be the exit record or no joining and exiting record.
Specifically, the method comprises the following steps:
when a node sends a node join transaction request in the block chain cluster, inquiring whether a node operation record exists or not, and if not, executing the node access transaction;
if so, inquiring whether a record with the maximum node operation height corresponding to the node adding and quitting operation in the history block of the node is the transaction record of the node quitting;
if yes, executing the node joining transaction; if not, stopping the node from joining the transaction and feeding back.
Thirdly, before the node freezes the transaction, the latest one-time record of the adding and quitting operation must be the record of adding, and if the record of the freezing and unfreezing operation exists, the latest one-time record of the freezing and unfreezing operation must be the record of unfreezing.
Fourthly, specifically:
when a node freezing transaction request is sent by a certain node in a block chain cluster, inquiring whether a record with the maximum node operation height corresponding to the node adding and quitting operation in the node operation type in a historical block of the node is the node adding transaction record or not;
if not, stopping the node from joining the transaction and feeding back;
if yes, inquiring whether the node operation type is the node freezing and unfreezing operation, and if not, executing the node freezing transaction;
if so, inquiring whether the record of the largest one of the corresponding node operation heights is the node unfreezing transaction record or not if the node operation type is the node freezing operation and the unfreezing operation;
if yes, executing the node freezing transaction; if not, stopping the node to freeze the transaction and feeding back.
Fourthly: before the node unfreezes the transaction, the latest adding and quitting operation record must be the adding record, and the latest freezing and unfreezing operation record must be the freezing record.
Specifically, the method comprises the following steps:
when a node unfreezing transaction request is sent by a certain node in a block chain cluster, inquiring whether a record with the maximum node operation height corresponding to node adding and quitting operation in the operation type of the node in a historical block of the node is a transaction record added by the node or not;
if not, stopping the node from joining the transaction and feeding back;
if yes, inquiring whether the node operation type is node freezing and unfreezing operation, and if not, stopping the node freezing transaction and feeding back;
if so, inquiring whether the record of the largest one of the corresponding node operation heights is the node freezing transaction record or not if the node operation type is the node freezing operation and the unfreezing operation;
if yes, executing the node unfreezing transaction; and if not, stopping the thawing transaction of the node and feeding back.
In the embodiment of the present application, the above rules are used to avoid situations affecting the finally recorded state, such as freezing nodes that do not exist, unfreezing nodes that are not frozen, and freezing nodes that have been deleted.
S200, checking the signature of the transaction request node by other nodes in the block chain cluster, and selecting whether to receive the node transaction;
s300, when other nodes in the block chain cluster select to receive the number of the node transactions, wherein the number meets the number required by the consensus rule, the node transactions are successfully known and executed by all the nodes in the block chain cluster.
The consensus rule is a process of achieving a uniform agreement on the state of the network in a decentralized manner. Validation and validation information is added to the categorized ledger to ensure that only real transactions are recorded on the blockchain. If the PBFT algorithm, namely the Byzantine fault-tolerant algorithm, is adopted, the number of the consensus rules is two thirds of the number of all the nodes, the consensus rules are not limited, and different consensus rules can be selected according to actual conditions.
S400, when the transaction request node executes the transaction, generating a transaction record in a node operation history record table, wherein the transaction record comprises the block height corresponding to the node transaction; and the node operation time, the node operation starting height, the node operation ending height and the node transaction type of the nodes in the block chain cluster are also recorded in the node operation history table.
According to the method and the device, historical operation of node operation is recorded, the historical retrospection of operation is facilitated, the operation of what height is clearly known is displayed in a high sequencing mode, and the number of effective nodes is conveniently calculated to perform verification operation of related node information.
And S500, the block chain account book node stores the block height and executes the data synchronization function of the historical blocks.
The historical block is a block interval smaller than the height of the current block, specifically, for example, the height of a block for adding a node into a transaction is 10, the blocks are historical blocks from 0 to 9, another transaction request node initiates a transaction later, the current node participates in the verification of the number of effective nodes, and when the blocks of other nodes fall behind, a function of synchronizing the blocks of other arbitrary nodes is executed, at the moment, the number of effective nodes is conveniently and rapidly calculated through the operation record table, the verification and verification of related blocks, transactions and intelligent contracts are carried out, and the legality is guaranteed.
S600, when a new transaction request node initiates the node to join the transaction, the step of checking the signature is repeatedly executed.
In the block chain cluster, an unlimited number of transaction request nodes can be used for transaction, and the method steps have universality. And the interval height is adopted to control effective nodes, and each initiation is recorded on a chain in an intelligent contract medium in a system transaction mode, so that the decentralized function is realized, and functions of traceability, tamper resistance and the like are given to a block chain cluster.
S700, when the packing node carries out transaction packing, in the node operation history table, inquiring effective nodes under the block height according to the current block height, generating an effective node list, and acquiring the number of the effective nodes;
s800, calculating the lowest vote number of the current block height according to the number of the effective nodes, and initiating QC verification; the voting uses a Quorum Certificate (QC) in cryptography, and the Quorum Certificate is essentially a Certificate signed by each node through its own private key, and is used as evidence of voting for other nodes in the present application.
And S900, when the node vote number in the QC verification meets the minimum vote number, completing transaction packaging. When the transaction is packaged into the block, the effective node can be obtained according to the current block height, and the voting of the effective node is used for verification, so that the decision-making performance of the block chain cluster is more efficient and accurate.
Further, as shown in fig. 4, the step of determining the valid node under the block height in the present application includes:
s710, acquiring all node operation records of any node, and searching the maximum record of which the corresponding node operation height is less than the block height in the node adding and quitting operation; the searched node is the node for adding the node into the transaction before the current block height, and the selection range of the node is effectively controlled.
Further, in step S711, the corresponding recorded node operation ending height is not 0 and is smaller than the block height, which indicates that the node has performed a node exit transaction before the current block height, and then it is determined that the node is not a valid node.
S720, if the maximum node operation ending height of the node in the quitting operation is 0 or more than the block height, inquiring whether the node operation type is the node freezing and unfreezing operation in all the records of which the maximum node operation ending height is less than the block height, and the node freezing and unfreezing operation height is less than the record of the block height;
the maximum node operation ending height is 0, which means that the node does not perform node exit transaction after performing node join transaction, and the node operation ending height is larger than the block height, which means that the operation height of the node is within the historical block range.
S730, if the node is not found, the node is an effective node; if the record of the operation type of node freezing and unfreezing is not found, the node does not perform node freezing transaction in the historical block corresponding to the block height, and the node has a normal function of acquiring transaction data on a chain, namely is an effective node.
And S740, if yes, checking whether the corresponding node operation ending height is not 0 in the record of the node, wherein the node operation type is the largest one of the starting heights corresponding to the operations of freezing and unfreezing the node, and the node operation ending height is smaller than the block height, if yes, the node is an effective node.
And when the operation type is the record of the node freezing and unfreezing operation, the node is indicated to perform the node freezing transaction, whether the node is unfrozen or not is continuously searched, when the node operation ending height is not 0 and is smaller than the block height, the node is indicated to perform the node unfreezing transaction, and after the node is unfrozen, the node recovers the function of acquiring transaction data on the chain, namely the node is an effective node.
Further, S741, if the node operation type is found to be the record of node freezing, checking whether the node operation ending height of the largest one of the node operation starting heights in the record of the node is 0 or greater than the block height, and if so, determining that the node is not an effective node.
When the node operation ending height is found to be 0 and is smaller than the block height, it is indicated that the node does not perform node unfreezing transaction, and the node is still in a frozen state, so that the node is not an effective node without a function of acquiring transaction data on a chain.
The embodiments described above show that the present application relates to the field of blockchain technology, and provides a system and a method for dynamically managing and checking nodes based on blockchains, wherein a blockchain cluster is provided with a blockchain account book node, a transaction request node, and a packaging node; the blockchain ledger node is configured to: recording all information in the block chain cluster; the transaction request node is configured to: sending a transaction request to the blockchain ledger node; the packing node is configured to: packaging transactions in the blockchain cluster into blocks; wherein the node transaction types include: adding a node into a transaction, quitting the transaction, freezing the transaction and unfreezing the transaction; the historical operation of the node operation is recorded, the historical tracing of the operation is facilitated, the operation at any height is clearly known through the height sorting mode, and the effective node number is conveniently calculated to carry out the verification operation of the related node information; each transaction initiation is recorded on a chain through an intelligent contract medium in a system transaction form, so that the decentralized and block chain tamper-proof functions are realized; and when other node blocks are synchronized with any other node blocks after, the effective node number is conveniently and rapidly calculated through the node operation record table, verification and verification of related blocks, transactions and intelligent contracts are carried out, the legality is ensured, and decentralization of node management is realized.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. The embodiments of the present application are intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (8)
1. A blockchain-based dynamic management and check node system, comprising: the system comprises a block chain cluster, a transaction request node and a packaging node, wherein the block chain cluster is provided with a block chain account book node, a transaction request node and a packaging node;
the blockchain ledger node is configured to: recording all information in the block chain cluster;
the transaction request node is configured to: sending a transaction request to the blockchain ledger node;
the packing node is configured to: packaging transactions in the blockchain cluster into blocks;
the system is configured to perform a method comprising the steps of:
a transaction request node initiates a node transaction meeting a node transaction rule to the block chain account node, wherein the node transaction comprises a signature of the transaction request node;
other nodes in the block chain cluster check the signature of the transaction request node and select whether to receive the node transaction;
when other nodes in the blockchain cluster select to receive the number of the node transactions meeting the number required by the consensus rule, the node transactions are successfully known and executed by all the nodes in the blockchain cluster;
when the transaction request node executes the transaction, generating a transaction record in a node operation history record table, wherein the transaction record comprises the block height corresponding to the node transaction; the node operation history table also records the node operation time, the node operation starting height, the node operation ending height and the node transaction type of the nodes in the block chain cluster; the node transaction types include: node joining transaction, node quitting transaction, node freezing transaction and node unfreezing transaction;
the block chain account book node saves the block height and executes the data synchronization function of the historical block;
when a new transaction request node initiates the node to join the transaction, the step of checking the signature is repeatedly executed;
when the packaging node carries out transaction packaging, all node operation records of any node are obtained in the node operation history record table, and the maximum record of which the corresponding node operation height is smaller than the block height in the node adding and quitting operation is searched;
if the maximum node operation ending height of the node in the joining and exiting operation is 0 or greater than the block height, inquiring whether the node operation type is the node freezing and unfreezing operation in all records of which the maximum node operation ending height is less than the block height, wherein the node freezing and unfreezing operation height is less than the record of the block height;
if not, the node is a valid node;
if so, checking whether the corresponding node operation ending height is not 0 in the record of the node, wherein the node operation type is the largest one of the starting heights corresponding to the operations of freezing and unfreezing the node, and the node operation ending height is smaller than the block height, if so, the node is an effective node;
generating an effective node list and acquiring the number of effective nodes;
calculating the lowest vote number of the current block height according to the number of the effective nodes, and starting arbitration certificate verification;
and when the node vote number in the arbitration certificate verification meets the minimum vote number, completing transaction packaging.
2. The blockchain-based dynamic management and check node system of claim 1,
the node join transaction is configured to: adding the target node to the blockchain cluster;
the node logout transaction is configured to: causing the target node to exit the blockchain cluster;
the node freeze transaction is configured to: freezing the target node, wherein the frozen target node cannot acquire the data operation request on the link;
the node unfreezing transaction is configured to: and enabling the target node to be restored to a state capable of acquiring the data operation request on the chain from the frozen state.
3. The blockchain-based dynamic management and check node system of claim 1, wherein the method further comprises:
acquiring all node operation records of any node, and searching the maximum record of which the corresponding node operation height is smaller than the block height in the node adding and quitting operation;
and if the corresponding recorded node operation ending height is not 0 and is smaller than the block height, judging that the node is not a valid node.
4. The blockchain-based dynamic management and check node system of claim 1, wherein the method further comprises:
if the node operation type is found to be the record of node freezing, and the node operation type is the record of the largest one of the starting heights corresponding to the operations of node freezing and unfreezing, whether the corresponding node operation ending height is 0 or larger than the block height is judged, and if yes, the node is not an effective node.
5. The blockchain-based dynamic management and verification node system of claim 1, wherein the node transaction rules include:
when a node quitting transaction request is sent by a certain node in a block chain cluster, inquiring whether a record with the maximum node operation height corresponding to the node adding and quitting operation in the node operation type in a historical block of the node is the node adding transaction record or not;
if yes, executing the node to quit the transaction; if not, stopping the node from quitting the transaction and feeding back.
6. The blockchain-based dynamic management and verification node system of claim 1, wherein the node transaction rules further comprise:
when a node sends a node join transaction request in a block chain cluster, inquiring whether a node operation record exists or not, and if not, executing the node access transaction;
if so, inquiring whether a record with the maximum node operation height corresponding to the node adding and quitting operation in the history block of the node is the transaction record of the node quitting;
if yes, executing the node joining transaction; if not, stopping the node from joining the transaction and feeding back.
7. The blockchain-based dynamic management and verification node system of claim 1, wherein the node transaction rules further include:
when a node freezing transaction request is sent by a certain node in a block chain cluster, inquiring whether a record with the maximum node operation height corresponding to the node adding and quitting operation in the node operation type in a historical block of the node is the node adding transaction record or not;
if not, stopping the node from joining the transaction and feeding back;
if yes, inquiring whether the node operation type is the node freezing and unfreezing operation, and if not, executing the node freezing transaction;
if so, inquiring whether the record of the largest one of the corresponding node operation heights is the node unfreezing transaction record or not if the node operation type is the node freezing operation and the unfreezing operation;
if yes, executing the node freezing transaction; if not, stopping the node to freeze the transaction and feeding back.
8. The blockchain-based dynamic management and verification node system of claim 1, wherein the node transaction rules further comprise:
when a node unfreezing transaction request is sent by a certain node in a block chain cluster, inquiring whether a record with the maximum node operation height corresponding to node adding and quitting operation in the operation type of the node in a historical block of the node is a transaction record added by the node or not;
if not, stopping the node from joining the transaction and feeding back;
if yes, inquiring whether the node operation type is the node freezing and unfreezing operation, and if not, stopping the node freezing transaction and feeding back;
if so, inquiring whether the record of the largest one of the corresponding node operation heights is the node freezing transaction record or not if the node operation type is the node freezing operation and the unfreezing operation;
if yes, executing the node unfreezing transaction; if not, stopping the unfreezing transaction of the node and feeding back.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211219028.5A CN115293769B (en) | 2022-10-08 | 2022-10-08 | Dynamic management and check node system based on block chain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211219028.5A CN115293769B (en) | 2022-10-08 | 2022-10-08 | Dynamic management and check node system based on block chain |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115293769A CN115293769A (en) | 2022-11-04 |
| CN115293769B true CN115293769B (en) | 2022-12-27 |
Family
ID=83833388
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211219028.5A Active CN115293769B (en) | 2022-10-08 | 2022-10-08 | Dynamic management and check node system based on block chain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115293769B (en) |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106445711A (en) * | 2016-08-28 | 2017-02-22 | 杭州云象网络技术有限公司 | Byzantine-fault-tolerant consensus method applied to block chain |
| CN107040594A (en) * | 2017-04-12 | 2017-08-11 | 山大地纬软件股份有限公司 | The method and device of license block chain node access based on PBFT |
| CN108027867A (en) * | 2015-07-14 | 2018-05-11 | Fmr有限责任公司 | Calculate efficient transfer accounts processing, audit and searcher, method and system |
| CN108681900A (en) * | 2018-07-18 | 2018-10-19 | 众安信息技术服务有限公司 | The method of light node verification transaction |
| CN108769173A (en) * | 2018-05-21 | 2018-11-06 | 阿里体育有限公司 | The block chain implementation method and equipment of the intelligent contract of operation |
| WO2019019056A1 (en) * | 2017-07-26 | 2019-01-31 | 杭州复杂美科技有限公司 | Method for frontal machine to participate in block chain consensus |
| CN109493222A (en) * | 2018-10-18 | 2019-03-19 | 尚维斯 | A kind of method of any number of block chain account book real-time synchronizations |
| CN109859047A (en) * | 2019-01-31 | 2019-06-07 | 北京瑞卓喜投科技发展有限公司 | A kind of block chain update method and block chain more new system |
| CN110580605A (en) * | 2019-09-11 | 2019-12-17 | 中原工学院 | Block chain-based electronic warehouse receipt information storage system |
| CN111106942A (en) * | 2019-12-13 | 2020-05-05 | 南京邮电大学 | Block chain credit mechanism based on AP-PBFT algorithm |
| CN111444512A (en) * | 2019-01-17 | 2020-07-24 | 杨税令 | Mobile terminal blocking method and system for block chain |
| CN111445333A (en) * | 2020-03-26 | 2020-07-24 | 腾讯科技（深圳）有限公司 | Block generation method and device, computer equipment and storage medium |
| CN111507709A (en) * | 2020-03-25 | 2020-08-07 | 农业农村部农药检定所(国际食品法典农药残留委员会秘书处) | Data traceability system |
| CN111630507A (en) * | 2020-04-20 | 2020-09-04 | 支付宝(杭州)信息技术有限公司 | Distributed blockchain data storage under account model |
| CN111988137A (en) * | 2020-07-11 | 2020-11-24 | 浙江工商大学 | DPoS (dual port service) consensus method and system based on threshold signature and fair reward |
| CN112235429A (en) * | 2020-12-17 | 2021-01-15 | 暗链科技(深圳)有限公司 | Central accounting type decentralized distributed data processing method and system |
| CN112269791A (en) * | 2020-11-30 | 2021-01-26 | 上海特高信息技术有限公司 | Construction method of account book index skip list and block chain account book processing method using same |
| CN112541758A (en) * | 2020-12-01 | 2021-03-23 | 鲁静 | Multi-round voting type fault-tolerant sequencing consensus mechanism and method based on block chain |
| CN114826780A (en) * | 2022-06-24 | 2022-07-29 | 中铱数字科技有限公司 | Block chain based multi-level authority management system and method |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11212081B2 (en) * | 2017-02-24 | 2021-12-28 | Nec Corporation | Method for signing a new block in a decentralized blockchain consensus network |
| JP2019109635A (en) * | 2017-12-16 | 2019-07-04 | 株式会社ｂｉｔＦｌｙｅｒ | Method for enabling past transaction to be accessed in block chain network and node to configure block chain network |
| CN108810077A (en) * | 2018-04-19 | 2018-11-13 | 深圳市网心科技有限公司 | Block chain common recognition processing method, electronic device and computer readable storage medium |
| EP3565218B1 (en) * | 2018-04-30 | 2023-09-27 | Hewlett Packard Enterprise Development LP | System and method of decentralized management of multi-owner nodes using blockchain |
| CN108805569A (en) * | 2018-05-29 | 2018-11-13 | 阿里巴巴集团控股有限公司 | Transaction processing method and device, electronic equipment based on block chain |
| WO2019170169A2 (en) * | 2019-06-05 | 2019-09-12 | Alibaba Group Holding Limited | Consensus system and method |
| CN110796549B (en) * | 2019-11-06 | 2023-04-14 | 杭州复杂美科技有限公司 | Transaction method, apparatus and storage medium |
| CN113691597B (en) * | 2019-11-27 | 2022-06-14 | 腾讯科技（深圳）有限公司 | Block chain contract deployment method, device, equipment and storage medium |
| CN111355810B (en) * | 2020-03-17 | 2022-05-10 | 重庆邮电大学 | Improved PBFT consensus method based on credit and voting mechanism |
| US20220083656A1 (en) * | 2020-09-14 | 2022-03-17 | POSTECH Research and Business Development Foundation | Apparatus and method for tolerating byzantine faults in blockchain platforms |
| CN112163954B (en) * | 2020-10-28 | 2022-04-08 | 腾讯科技（深圳）有限公司 | Transaction method and device based on block chain |
-
2022
- 2022-10-08 CN CN202211219028.5A patent/CN115293769B/en active Active
Patent Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108027867A (en) * | 2015-07-14 | 2018-05-11 | Fmr有限责任公司 | Calculate efficient transfer accounts processing, audit and searcher, method and system |
| CN106445711A (en) * | 2016-08-28 | 2017-02-22 | 杭州云象网络技术有限公司 | Byzantine-fault-tolerant consensus method applied to block chain |
| CN107040594A (en) * | 2017-04-12 | 2017-08-11 | 山大地纬软件股份有限公司 | The method and device of license block chain node access based on PBFT |
| WO2019019056A1 (en) * | 2017-07-26 | 2019-01-31 | 杭州复杂美科技有限公司 | Method for frontal machine to participate in block chain consensus |
| CN108769173A (en) * | 2018-05-21 | 2018-11-06 | 阿里体育有限公司 | The block chain implementation method and equipment of the intelligent contract of operation |
| CN108681900A (en) * | 2018-07-18 | 2018-10-19 | 众安信息技术服务有限公司 | The method of light node verification transaction |
| CN109493222A (en) * | 2018-10-18 | 2019-03-19 | 尚维斯 | A kind of method of any number of block chain account book real-time synchronizations |
| CN111444512A (en) * | 2019-01-17 | 2020-07-24 | 杨税令 | Mobile terminal blocking method and system for block chain |
| CN109859047A (en) * | 2019-01-31 | 2019-06-07 | 北京瑞卓喜投科技发展有限公司 | A kind of block chain update method and block chain more new system |
| CN110580605A (en) * | 2019-09-11 | 2019-12-17 | 中原工学院 | Block chain-based electronic warehouse receipt information storage system |
| CN111106942A (en) * | 2019-12-13 | 2020-05-05 | 南京邮电大学 | Block chain credit mechanism based on AP-PBFT algorithm |
| CN111507709A (en) * | 2020-03-25 | 2020-08-07 | 农业农村部农药检定所(国际食品法典农药残留委员会秘书处) | Data traceability system |
| CN111445333A (en) * | 2020-03-26 | 2020-07-24 | 腾讯科技（深圳）有限公司 | Block generation method and device, computer equipment and storage medium |
| CN111630507A (en) * | 2020-04-20 | 2020-09-04 | 支付宝(杭州)信息技术有限公司 | Distributed blockchain data storage under account model |
| CN111988137A (en) * | 2020-07-11 | 2020-11-24 | 浙江工商大学 | DPoS (dual port service) consensus method and system based on threshold signature and fair reward |
| CN112269791A (en) * | 2020-11-30 | 2021-01-26 | 上海特高信息技术有限公司 | Construction method of account book index skip list and block chain account book processing method using same |
| CN112541758A (en) * | 2020-12-01 | 2021-03-23 | 鲁静 | Multi-round voting type fault-tolerant sequencing consensus mechanism and method based on block chain |
| CN112235429A (en) * | 2020-12-17 | 2021-01-15 | 暗链科技(深圳)有限公司 | Central accounting type decentralized distributed data processing method and system |
| CN114826780A (en) * | 2022-06-24 | 2022-07-29 | 中铱数字科技有限公司 | Block chain based multi-level authority management system and method |
Non-Patent Citations (2)
| Title |
|---|
| "Survey of security supervision on blockchain from the perspective of technology";Yu Wang et al;《Journal of Information Security and Applications》;20210831;第1-31页 * |
| "基于联盟链的多链式区块链共识性能研究";孙一蓬;《中国优秀硕士学位论文全文数据库 信息科技辑》;20200115;I138-219 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115293769A (en) | 2022-11-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109639632B (en) | User information management method based on block chain, electronic equipment and storage medium | |
| CN107193490B (en) | Distributed data storage system and method based on block chain | |
| WO2020258831A1 (en) | Method and device for master node handover processing in blockchain system | |
| KR102002509B1 (en) | Privite blockchain system including notarizing center and notarial method thereof | |
| CN108429759B (en) | Decentralized storage safety implementation method | |
| CN113141414B (en) | Grouped multi-chain asynchronous consensus method for block chain nodes in CNFS protocol | |
| CN110602217A (en) | Block chain-based alliance management method, device, equipment and storage medium | |
| CN111914021A (en) | Cross-block-chain interaction method and system, computer equipment and storage medium | |
| CN112612856B (en) | Block chain-based data processing method and device | |
| CN113806699B (en) | Cross-blockchain identity verification method and system in inter-cloud computing environment | |
| CN112307458A (en) | Light node uplink method and device, Internet of things central control terminal and block chain network | |
| CN112822239A (en) | Block chain consensus method, block chain consensus device, electronic equipment and storage medium | |
| US11343313B1 (en) | Fault tolerant periodic leader rotation for blockchain | |
| CN112073382B (en) | Graph type account book node maintenance method and device based on random consensus | |
| CN113259311A (en) | Decentralized identity authentication system based on block chain | |
| CN114372296A (en) | Block chain-based user behavior data auditing method and system | |
| CN112671908A (en) | Network management method and device, electronic equipment and readable storage medium | |
| CN110278246B (en) | Certificate storage service transfer method, device and equipment for alliance chain | |
| CN116611840A (en) | Distributed data asset circulation traceability system and method based on blockchain | |
| CN109598108B (en) | Program product selling method, block link point, storage medium, and block link system | |
| CN114363089A (en) | Block chain-based network edge terminal data sharing method and model | |
| CN111917748B (en) | Intelligent laser remote control system and method based on IPFS + alliance chain | |
| CN112565368B (en) | Block chain based offshore equipment ad hoc network system, method and medium | |
| CN115293769B (en) | Dynamic management and check node system based on block chain | |
| CN114912856B (en) | Flight simulator maintenance method based on block chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |