Search

KR-102963744-B1 - APPARATUS AND METHOD FOR CONTROLLING PEER NODES IN A BLOCKCHAIN NETWORK

KR102963744B1KR 102963744 B1KR102963744 B1KR 102963744B1KR-102963744-B1

Abstract

A control device and a control method are provided. The control device comprises: a monitoring unit that verifies the validity of a transaction using a consensus algorithm for a transaction generated by multiple participants, verifies the block of the transaction for a peer node of the blockchain network, and monitors each of the peer nodes of the blockchain network regarding the success or failure of the transaction to record the number of transaction failures; and a blockchain management unit that determines data tampering based on the result value of the transaction.

Inventors

  • 장후규
  • 허광호
  • 박기호
  • 안치훈

Assignees

  • 디엑스웍스 주식회사

Dates

Publication Date
20260512
Application Date
20240529

Claims (15)

  1. A monitoring unit that, when a transaction block is verified for a peer node of a blockchain network, monitors the success or failure of the transaction for each of the peer nodes and records the number of transaction failures; and A blockchain management unit that determines data tampering based on the number of transaction failures mentioned above; is included, In the case where, for a single transaction, the blockchain log of at least one peer node among the plurality of peer nodes included in the blockchain network is recorded as a failure, The aforementioned blockchain management department, Checking whether there is a match between the blockchain log record of at least one peer node and the blockchain log record of the remaining peer nodes among the plurality of peer nodes, excluding at least one peer node, and The blockchain management unit above determines whether data has been tampered with based on whether there is a match between the blockchain log records. Control device.
  2. In paragraph 1, In the case where a peer node of the above blockchain network includes a state database that stores a record of the above transaction related to the success or failure of the above transaction, The blockchain management unit above updates and stores the record of the transaction so that the most recent state is reflected. Control device.
  3. delete
  4. A monitoring unit that, when a transaction block is verified for a peer node of a blockchain network, monitors the success or failure of the transaction for each of the peer nodes and records the number of transaction failures; and A blockchain management unit that determines data tampering based on the number of transaction failures mentioned above; is included, In the case where, for a single transaction, at least one peer node among the plurality of peer nodes included in the blockchain network records the blockchain log as successful and the remaining peer nodes record the blockchain log as unsuccessful, The blockchain management unit above monitors log records for transactions of each peer node based on the remaining peer nodes, and Evaluating whether data matches between the peer nodes based on the above log records to identify data tampering, and calculating the number of transaction failures according to the result of identifying the data tampering, Control device.
  5. A monitoring unit that, when a transaction block is verified for a peer node of a blockchain network, monitors the success or failure of the transaction for each of the peer nodes and records the number of transaction failures; and A blockchain management unit that determines data tampering based on the number of transaction failures mentioned above; is included, The aforementioned blockchain management department, Monitoring is performed based on multiple blockchain log records possessed by multiple peer nodes included in the above blockchain network, Among the plurality of peer nodes mentioned above, the peer node where the transaction processing result is recorded as a failure is compared with the peer node where the transaction processing result is recorded as a success to evaluate whether the plurality of blockchain log records match, and The blockchain management unit above calculates the number of transaction failures based on the plurality of blockchain log records above, Control device.
  6. In paragraph 5, When the same block containing the above transaction is transmitted to the plurality of peer nodes by the orderer node, For each of the aforementioned plurality of peer nodes, the success or failure of the transaction is recorded in the blockchain log, and The blockchain management unit determines the number of transaction failures by evaluating whether there is a match between the plurality of peer nodes based on the plurality of blockchain log records. Control device.
  7. In paragraph 5, The aforementioned blockchain management department, Generate a warning notification for peer nodes whose number of transaction failures exceeds a preset threshold, and The blockchain management unit above sends the warning notification to multiple participants related to the above-mentioned exceeded peer node, Control device.
  8. In paragraph 5, The aforementioned blockchain management department, A peer node whose number of transaction failures exceeds the participation limit threshold is considered a bad node and automatically excluded from the blockchain network. Control device.
  9. In paragraph 8, The aforementioned blockchain management department, For the aforementioned bad node, storing the state database of the said bad node and the log records of the said bad node in the blockchain log, Control device.
  10. delete
  11. delete
  12. delete
  13. delete
  14. delete
  15. delete

Description

Apparatus and Method for Controlling Peer Nodes in a Blockchain Network The present invention relates to a network constructed with blockchain, and more specifically, to a control device and method for controlling a plurality of peer nodes existing in a blockchain network system. A blockchain is an immutable transaction ledger managed by a distributed network of peer nodes. Multiple nodes group blocks by linking them with hashes. It manages copies of the ledger through grouped blocks by applying verified transactions via a consensus protocol. Bitcoin and Ethereum are representative cryptocurrencies well-known for blockchain applications. Both Bitcoin and Ethereum are based on public permissionless blockchain technology and are open public networks where participants communicate anonymously. As the popularity of cryptocurrencies increased, various derivative technologies began to grow alongside them to apply blockchain, distributed ledger, and distributed application platform-based technologies more innovatively, and enterprise use cases also increased. Accordingly, Hyperledger Fabric was developed as an open-source, enterprise-grade permissioned Distributed Ledger Technology (DLT) designed for enterprise use from the outset. Hyperledger Fabric is a permissioned blockchain system in which only authorized users can participate. Participants in Hyperledger Fabric operate their own peer nodes, and block creation is carried out through orderer nodes. In this process, orderer nodes determine the order of transactions and play the role of creating blocks. Orderer nodes arrange these transactions in a specific order to create a block and distribute the generated block to other components of the network. Peer nodes play the role of storing and maintaining the ledger, which is the core data of the blockchain. Each peer node verifies the validity of transactions and records valid transactions in its ledger. Additionally, it executes chaincode, which is a smart contract, to perform the business logic necessary to process transactions, and peer nodes are responsible for maintaining the state database by storing the latest state of the blockchain. This state database reflects the results of transaction processing, but there is a possibility that data may be tampered with during this process. If the state database of each participant's peer node is tampered with, serious problems may arise regarding the integrity and reliability of the entire blockchain network. FIG. 1 is a block diagram illustrating a control system according to an embodiment of the present invention. FIG. 2 is a block diagram illustrating a control system including a blockchain peer node control device according to an embodiment of the present invention. FIG. 3 is a block diagram illustrating a control device according to an embodiment of the present invention. FIG. 4 is a diagram illustrating the process of a control device operating when an initial transaction occurs according to an embodiment of the present invention. FIG. 5 is a diagram illustrating the process of a control device operating when a transaction failure occurs according to an embodiment of the present invention. FIG. 6 is a diagram illustrating the process of a control device operating when transaction failures accumulate according to an embodiment of the present invention. FIG. 7 is a diagram illustrating a peer node removal method performed by a control device according to an embodiment of the present invention. FIG. 8 is a control device according to an embodiment of the present invention and a peer node diagram of a blockchain network performed by the control device. FIG. 9 is a flowchart for explaining a control method performed by a control device according to an embodiment of the present invention. FIG. 10 is a drawing showing a computing device according to an embodiment of the present invention. Embodiments of the present invention are described below with reference to the attached drawings so that those skilled in the art can easily implement them. However, the present invention may be embodied in various different forms and is not limited to the embodiments described herein. Furthermore, in order to clearly explain the present invention in the drawings, parts unrelated to the explanation have been omitted, and similar parts throughout the specification are denoted by similar reference numerals. In this specification and drawings (hereinafter referred to as the 'this specification'), redundant descriptions of identical components are omitted. Furthermore, when it is stated in this specification that a component is 'connected' or 'connected' to another component, it should be understood that it may be directly connected to or connected to the other component, or that there may be other components in between. On the other hand, when it is stated in this specification that a component is 'directly connected' or 'directly connected' to another component, it should be understood t