KR102060435B1 - Method and apparatus of blockchain smart contract using proof-of-repuation-of-network as consensus algorithm - Google Patents

Abstract

Disclosed are a method of a blockchain-based smart contract using Proof-of-Reputation-of-Network as a consensus algorithm, and an apparatus thereof. According to one embodiment of the present invention, the method comprises the steps of: acquiring details of a smart contract from a smart contract node which has received the details of a smart contract from a client which is a subject of the smart contract; choosing, when a sequence number granted from an index server comes round, a consensus node for generating a block including the details of a smart contract among consensus nodes connected to a P2P-sub network; transmitting the details of a smart contract to the chosen consensus node; obtaining, from the chosen consensus node, the block including the details of a smart contract; transmitting the block to at least one of the smart contract node, network nodes which have received the sequence number from the index server, and the consensus nodes connected to the P2P-sub network; and including the block in a blockchain.

Description

METHOD AND APPARATUS OF BLOCKCHAIN SMART CONTRACT USING PROOF-OF-REPUATION-OF-NETWORK AS CONSENSUS ALGORITHM}

The following embodiments are related to smart contract technology based on blockchain.

Smart Contract is a network that automates the process of contract execution and verification through the network, so that the rights and the rights between the contracting parties are not negotiated by the intermediary to check the terms of the contract and without additional fees such as brokerage fees. The effect of the obligation is a form of new contract processing that occurs directly, electronically and immediately.

Smart contracts can be stored on the blockchain so that they can't be manipulated or modified once signed. This allows complex business contracts to be safely executed as smart contracts with low cost and consensus trust. A blockchain that records smart contracts can be called a blockchain smart contract system.

Meanwhile, the consensus algorithm applied to the blockchain smart contract system needs to be different from the consensus algorithms applied to the existing blockchain virtual currency system. That is, since the details of smart contracts are generally composed of string data that is much longer than the transaction history of virtual currency, when following the consensus algorithm of proof of work (POW), all nodes receive a hash key of a much longer string. The work is done to find, which leads to enormous energy and power losses. In addition, proof of ownership (POS) is a method in which more nodes with more cryptocurrency have more opportunities to create blocks, but in the case of blockchain smart contract system, it is not necessarily premised on cryptocurrency. Giving nodes with a lot of money a lot of opportunities to create blocks lacks justification as a consensus algorithm.

Accordingly, there is a demand for a consensus algorithm that can be effectively applied to a blockchain smart contract system.

Embodiments generate a network reputation of the nodes based on the performance data of the nodes, point to the node to generate a block containing the details of the smart contract based on the network reputation of the nodes, block the block generated by the indicated node We want to provide a process for inclusion in the chain.

Embodiments apply a deduction to a node's network reputation if the node generates an invalid block, and if the node generates a valid block more than a predetermined number of times in a row or first validates an invalid block, the node's network We want to provide a process for adding value to our reputation.

Through the above, it is intended to provide a blockchain smart contract system having a network reputation proof as a consensus algorithm, in which nodes participating in the blockchain smart contract system act and evaluate based on the network reputation.

Furthermore, embodiments provide a blockchain smart contract method and apparatus using a network reputation proof as a consensus algorithm for solving the problems mentioned in the background art and the problems in the related art.

According to an embodiment, there is provided a method of obtaining a smart contract from a smart contract node that has received a smart contract from a client, which is a subject of a smart contract. When the sequence number granted from the index server arrives, the consensus node that is to generate a block including the details of the smart contract among consensus nodes connected to the P2P-sub network is indicated. Making; Transmitting the details of the smart contract to the indicated consensus node; Obtaining a block containing the details of the smart contract from the indicated consensus node; Transmitting the block to at least one of the smart contract node, network nodes assigned a number from the index server, and consensus nodes connected to the P2P subnetwork; And including the block in the blockchain.

According to one embodiment, specifying a consensus node to generate the block comprises: obtaining performance data of the consensus nodes; Generating a network reputation of each consensus node based on the performance data of each consensus node; Based on the network reputation of each consensus node, generating a probability that each consensus node will be identified as a node to generate a block; Based on the probabilities, the method may include identifying a consensus node to generate a block.

According to an embodiment, the performance data of each consensus node includes information on the network connection environment of the corresponding consensus node, and the network reputation of each consensus node is a numerical value related to the responsiveness of the network connection environment of the consensus node. It may include.

The apparatus according to one embodiment may be controlled by a computer program stored in a medium in combination with hardware to carry out the method of any one of the aforementioned methods.

According to an embodiment, the device obtains the details of the smart contract from the smart contract node that has received the details of the smart contract from the client, which is the subject of the smart contract, and assigns the details of the smart contract from the index server. When the received sequence number arrives, the consensus nodes connected to the P2P-Sub network are selected from the consensus nodes to generate a block including the details of the smart contract, and the consensus node is designated as the consensus node. Transmits the details of the smart contract, obtains a block including the details of the smart contract from the indicated consensus node, receives the sequence number from the smart contract node, the index server, and the network node; A program that transmits the block to consensus nodes connected to the P2P subnetwork and includes the block in the blockchain. It can include documents.

Embodiments generate a network reputation of the nodes based on the performance data of the nodes, point to the node to generate a block containing the details of the smart contract based on the network reputation of the nodes, block the block generated by the indicated node It can provide a process for inclusion in the chain.

Embodiments apply a deduction to a node's network reputation if the node generates an invalid block, and if the node generates a valid block more than a predetermined number of times in a row or first validates an invalid block, the node's network It can provide a process of adding points to the reputation.

Through the above, it is possible to provide a blockchain smart contract system having a network reputation proof as a consensus algorithm, in which nodes participating in the blockchain smart contract system act and evaluate based on the network reputation.

On the other hand, the effects according to the embodiments are not limited to those mentioned above, and other effects that are not mentioned will be clearly understood by those skilled in the art from the following description.

1 is a diagram illustrating a blockchain smart contract system according to an exemplary embodiment.
2 is a diagram illustrating an operation of an index server and a network node, according to an exemplary embodiment.
3 is a diagram for describing a block generation process, according to an exemplary embodiment.
4 is a diagram illustrating an operation of a client, a smart contract node, a network node, and a consensus node according to an embodiment.
5 is a diagram illustrating an operation of a network node and a consensus node according to an embodiment.
6 is a flowchart illustrating a process of including a block in a blockchain according to an embodiment.
7 is a flowchart illustrating a process of pointing to a consensus node according to an embodiment.
8 is a diagram for describing a process of generating a network reputation according to an exemplary embodiment.
9 is an exemplary diagram of a configuration of an apparatus according to an embodiment.

Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings. However, various changes may be made to the embodiments so that the scope of the patent application is not limited or limited by these embodiments. It is to be understood that all changes, equivalents, and substitutes for the embodiments are included in the scope of rights.

Specific structural or functional descriptions of the embodiments are disclosed for purposes of illustration only, and may be practiced in various forms. Accordingly, the embodiments are not limited to the specific disclosure, and the scope of the present specification includes changes, equivalents, or substitutes included in the technical idea.

Terms such as first or second may be used to describe various components, but such terms should be interpreted only for the purpose of distinguishing one component from another component. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

When a component is referred to as being "connected" to another component, it should be understood that there may be a direct connection or connection to that other component, but there may be other components in between.

The terminology used herein is for the purpose of description and should not be construed as limiting. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, terms such as "comprise" or "have" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described on the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

In addition, in the description with reference to the accompanying drawings, the same components regardless of reference numerals will be given the same reference numerals and duplicate description thereof will be omitted. In the following description of the embodiment, when it is determined that the detailed description of the related known technology may unnecessarily obscure the gist of the embodiment, the detailed description thereof will be omitted.

Embodiments may be implemented in various forms of products, such as personal computers, laptop computers, tablet computers, smart phones, televisions, smart home appliances, intelligent cars, kiosks, wearable devices, and the like.

1 is a diagram illustrating a blockchain smart contract system according to an exemplary embodiment.

The blockchain smart contract system includes an index server 100; Network nodes (Network Nodes 110, 120, 130, 140); Smart contract nodes 115, 125, 135, and 145; Consensus nodes 111-113, 121-123, 131-133, 141-143; And clients 146 and 147. These are a combination of hardware and software, which may be a group or a group of devices capable of all kinds of wired and wireless communication such as a dedicated server, a general purpose server, a desktop PC, a laptop PC, a Mac, a smartphone, a smart pad, a tablet PC, and the like.

1 to 8, the index server 100 is shown in polka dots; Network nodes 110, 120, 130, 140 are shown in checkered; Smart contract nodes 115, 125, 135, and 145 are shown in horizontal stripes; Consensus nodes 111-113, 121-123, 131-133, 141-143 are shown in vertical pattern; Clients 146 and 147 are shown in a zigzag pattern.

In addition, the blockchain smart contract system may include a P2P network 109 and P2P sub-networks 119, 129, 139, 149. The P2P network 109 and the P2P subnetworks 119, 129, 139, and 149 are distributed connection structures that allow information exchange between nodes, and include 3G, LTE, 5G, Bluetooth communication, NFC network, and the Internet. , A dedicated line, a LAN, an intranet, or the like, may operate by at least one communication method, and a communication protocol such as TCP or UDP may be used.

1 and 3, the P2P Network 109 is shown in solid lines and the P2P Sub Networks 119, 129, 139, 149 are shown in broken lines.

The index server 100 may manage a group including at least one network node 110, 120, 130, 140. The index server 100 may join the network nodes 110, 120, 130, and 140 included in the group to the P2P network 109 through a verification procedure, and give the network nodes 110, 120, 130, and 140 to the network nodes 110, 120, 130, and 140. It may be assigned a sequence number that points to a consensus node to generate a block containing the details of the smart contract.

Each network node 110, 120, 130, 140 may manage a subgroup comprising at least one consensus node 111-113, 121-123, 131-133, 141-143, and manages itself. A network reputation (Reputation of Network) of consensus nodes belonging to a subgroup may be generated, stored, and updated. Each network node 110, 120, 130, 140 may point to a consensus node to generate a block when its turn arrives.

The consensus node may generate a block containing the details of the smart contract according to the point of the network node. Consensus nodes in a subgroup may be connected to other consensus nodes in the subgroup and a network node managing the subgroup in a P2P subnetwork. If the indicated consensus node generates a valid block in which the details of the smart contract have not been manipulated, compensation such as money or virtual currency may be paid.

For example, consensus node A1 111 included in a subgroup managed by network node A 110 and network node A 110; Consensus node A2 112; Consensus node A3 113 may be connected to each other to P2P sub-network A 119. Consensus node B1 121 included in a network node B 120 and a subgroup managed by network node B 120; Consensus node B2 122; Consensus node B3 123 may be connected to each other to the P2P sub-network B (129). Consensus node C1 131 included in network node C 130 and subgroups managed by network node C 130; Consensus node C2 132; Consensus node C3 133 may be connected to each other through a P2P sub-network C (139). Consensus node D1 141 included in network node D 140 and subgroups managed by network node D 140; Consensus node D2 142; Consensus node D3 143 may be connected to each other to P2P subnetwork D 149.

The process of forming the P2P sub network 119 may be as follows, but is not limited thereto. First, network node 110 may open a TCP-server for a P2P subnetwork. The consensus nodes 111, 112, 113 can then connect to the network node 110 with a TCP-client. In this case, communication may be performed between the P2P network 109 and the P2P subnetwork 119 in a TCP manner. In addition, multicast may be used between the P2P network 109 and the P2P subnetwork 119. The process of forming other P2P sub-networks 129, 139, and 149 may be the same.

The smart contract node 115, 125, 135, 145 connects the clients 146, 147, which are the subjects of the smart contract, with the P2P network 109 and the P2P subnetworks 119, 129, 139, 149. Do this. The smart contract nodes 115, 125, 135, and 145 may receive and store all details of the smart contract from the clients 146 and 147.

Each smart contract node 115, 125, 135, 145 may be responsible for a particular zonal unit called a region. Regions can be regional or national, where laws, tax rates, tariffs, rules, bylaws, exceptions, etc. are separated. Smart contracts made within a region can be sent to the smart contract node in charge of the region. This ensures, for example, that client X (146) and client Y (147) wishing to enter into a real estate sales contract in accordance with Korean law do not communicate all the details of the smart contract to the smart contract node 135 in Japan. have. The smart contract nodes 115, 125, 135, and 145 in charge of the region may function as a database to view all the details of the smart contracts occurring within the region.

Smart contract nodes 115, 125, 135, and 145 may be connected with network nodes and consensus nodes via P2P subnetworks 119, 129, 139, 149. For example, smart contract node A 115 may include P2P subnetwork A 119; The smart contract node B 125 may include a P2P sub-network B 129; Smart contract node C 135 includes P2P sub-network C 139; The smart contract node D 145 may be connected with the P2P subnetwork D 149. Through this, the details of the smart contract created in the region may be blocked in the P2P subnetwork of the region instead of the P2P subnetwork of the other region.

Clients 147 and 148 are subjects of the smart contract, and after entering into the smart contract, may transmit all the details of the smart contract to the smart contract node 145 in charge of the region. Clients 147 and 149 may be DApps or Personals. Meanwhile, the blockchain smart contract system may be linked with a real estate registry office, a vehicle registration office, a bank, a virtual currency exchange, and the like. Through this, when a smart contract between clients is concluded, the transfer of money or virtual currency can be made electronically immediately, and the registration or registration of property rights can also be made electronically immediately.

In summary, the clients 146 and 147 may conclude, for example, a smart contract in which the client X 146 buys and sells the real estate R owned by the client Y 147. The emergence of rights and obligations resulting from the conclusion of smart contracts can take place immediately. After the smart contract is concluded between the clients 146, 147, all details of the smart contract can be communicated to the smart contract node D 145. The smart contract node D 145 may transmit the details of the smart contract corresponding to all or part of all the details of the smart contract to the network node D 140. The network node D 140 generates a consensus node that will generate a block including the details of the smart contract among consensus nodes 141, 142, and 143 connected to the P2P sub-network D 149 when its turn arrives. can do. The indicated consensus node, such as consensus node D1 141, may generate a block containing the details of the smart contract and forward it to network node D 140. Network node D 140 is smart contract node D 145, other network nodes 110, 120, 130 connected to P2P network 109, and other consensus nodes 142 connected to P2P subnetwork D 149. , Block 143). Each node can then include the block in the blockchain.

2, an embodiment related to the operation of the index server and the network node will be described. 3, an embodiment related to a block generation process will be described. With reference to FIG. 4, an embodiment related to the operation of a client, a smart contract node, a network node, and a consensus node is described. 5, an embodiment related to the operation of a network node and a consensus node is described. Referring to FIG. 6, an embodiment related to a process of including a block in a blockchain will be described. 7, an embodiment related to the process of pointing to a consensus node is described. 8, an embodiment related to a process of generating a network reputation is described.

2 is a diagram illustrating an operation of an index server and a network node, according to an exemplary embodiment.

First, the index server 100 may join the network nodes 110, 120, 130, and 140 to the P2P network 109, and assign the order to the network nodes 110, 120, 130, and 140 ( 210).

The network nodes 110, 120, 130, 140 form a P2P network 109 between each other in the blockchain smart contract system; Manage consensus nodes 111-113, 121-123, 131-133, 141-143; By connecting to the smart contract node 115, 125, 135, 145 plays a pivotal role to connect the clients 146, 147 with the blockchain smart contract system. In order to perform these tasks, the performance of network nodes 110, 120, 130, 140 should generally be good.

Accordingly, the index server 100 may verify whether the network nodes 110, 120, 130, and 140 of the group managed by the index server are suitable to participate in the P2P network 109. The verification method may include a method of determining whether a network reputation of the network nodes 110, 120, 130, and 140 is greater than or equal to a threshold value.

Here, the network reputation may be represented by a numerical value and may be calculated based on performance data of the network node. Performance data can include network connectivity, hardware specifications, observability, and controllability. On the other hand, i) the process of calculating the network reputation of the network node based on the performance data of the network node and ii) the network connection environment, hardware specifications, observability, controllability included in the performance data of the network node with reference to Figure 8 Iii) the process of calculating the network reputation of the consensus node based on the performance data of the consensus node and iv) the network connection environment, hardware specification, observability, and controllability included in the performance data of the consensus node, i) And ii) will be replaced with descriptions of iii) and iv) which will be described later with reference to FIG. 8.

In addition, the network reputation of the network node can be deducted based on the performance of the network node in the blockchain smart contract system. For example, if the consensus node 111 pointed at by a particular network node 110 has generated an invalid block in which the details of the smart contract have been manipulated, the network reputation of the network node 110 may be penalized. When the network reputation of the network node 110 is lowered below the threshold by the deduction point, the network node 110 may be disconnected from the P2P network 109. When the network node is blocked from the P2P network 109 by the deduction of network reputation, the index server 100 may control that the network node cannot participate in the P2P network 109 again for a certain period of time.

The index server 100 may obtain IP addresses of the verified network nodes 110, 120, 130, and 140, and the verified network nodes 110, 120, 130, and 140 may perform the P2P network 109. Can be connected to each other. For example, in a situation where the network nodes A, B, and C 110, 120, and 130 participate in the P2P network 109 in advance, the network node D 140 completes the verification and newly joins the P2P network 109. If desired, the network node 140 may open a TCP-server for a P2P network. The index server 100 may transfer the IP address of the network node D 140 to be newly joined to the network nodes A, B, and C (110, 120, 130) already participating in the P2P network 109. The network nodes A, B, and C (110, 120, 130) that have received the information about the network node D 140 connect to the TCP-server opened by the network node D 140 to be newly joined as a TCP-client. The network nodes 110, 120, 130, 140 may be connected to each other via a P2P network 109.

Next, the index server 100 may give the network nodes 110, 120, 130, and 140 a sequence number for identifying a consensus node for generating a block. In detail, the index server 100 may give each network node 110, 120, 130, 140 a cyclic order according to a round robin list. At this time, the network node A 110 located at the physical location nearest to the physical location where the index server 100 is located may receive the first order of the round robin list. Next, the network node B 120 located at the physical location nearest to the physical location where the network node A 110 is located may receive the second turn of the round robin list. In this manner, the network node C 130 may be set to 3 times and the network node D 140 may be set to 4 times. By ordering the nodes in this manner, the distance of the communication line between the nodes and the distance of the communication line between the node and the index server 100 can be minimized, so that efficient and faster communication can be achieved between each other.

After the network nodes are numbered, the network nodes can identify consensus nodes that will generate blocks in the P2P subnetwork to which they are connected in turn, and if the consensus node generates a block and then informs the network node, the network node Block generation may be informed to other network nodes of the P2P network 109.

For example, network node A 110, which is sequence number 1, may designate a consensus node to generate a block in P2P subnetwork A 119, and a specific consensus node 111 connected to P2P sub network A 119 may select a block. After generating and notifying the network node A 110, the network node A 110 may notify other network nodes 120, 130, and 140 of the P2P network 109 that the block has been created. Next, the network node B 120, which is sequence 2, may perform the same process, and then, the network node C 130, which is sequence 3, may perform the same process, and in the following order. In step 4, the network node D 140 may perform the same process. Then, according to the circularity of the round robin list, network node B 120, which is sequence number 1 again, may perform the same process, and this cycle may be repeated.

The process of selecting a consensus node by the network node may be performed by a probability generated based on the network reputation of the consensus node. Also, after being notified that the block has been created, the network nodes may include the block in the blockchain and broadcast that a new block is generated in the P2P subnetwork to which the network node is connected. A detailed process of the network node pointing to the consensus node and a detailed operation performed by the network nodes notified that the block has been generated will be described later with reference to FIGS. 6 to 8.

3 is a diagram for describing a block generation process, according to an exemplary embodiment.

Each of the network nodes 110, 120, 130, and 140 participating in the P2P network 109 blocks blocks in the P2P subnetworks 119, 129, 139, and 149 to which the index server 100 is connected. Consensus nodes (111-113, 121-123, 131-133, 141-143) to be created can be indicated. Hereinafter, the order in which the network nodes 110, 120, 130, and 140 have a periodicity that designates a consensus node to generate a block is called a tier. The blockchain system can have a plurality of tiers. For example, as shown in FIG. 3, there may be Tier 1 310 and Tier 2 320. In FIG. 3, Tier 1 310 is shown by dashed line and Tier 2 320 is shown by dashed line.

Tier 1 310 is a network node 110, 120, 130, according to the order that the index server 100 is assigned to each network node (110, 120, 130, 140) based on a round robin list (Round Robin List) 140 may be an order to indicate a consensus node to generate a block. At this time, the network node A 110 located at the physical location nearest to the physical location where the index server 100 is located may receive the first order of the round robin list. Next, the network node B 120 located at the physical location nearest to the physical location where the network node A 110 is located may receive the second turn of the round robin list. In this manner, the network node C 130 may be set to 3 times and the network node D 140 may be set to 4 times. In this case, Tier 1 310 points to a consensus node where Network Node A 110, Network Node B 120, Network Node C 130, and Network Node D 140 will sequentially generate blocks. Again, the network node A 110 may have a periodicity that indicates a consensus node for generating a block.

Tier 2 320 may be an optionally operated tier. Tier 2 320 increases the number of network nodes included in the round robin list of Tier 1 310, such that the time it takes for a particular network node to re-point the consensus node in the P2P subnetwork to which it is connected is a specific time, For example, it can be operated when it exceeds 1 second. For example, Tier 2 320 may point to a consensus node where Network Node C 130, Network Node B 120, Network Node A 110, and Network Node D 140 will sequentially generate blocks. In addition, the network node C 130 may be in order of having a periodicity for identifying a consensus node for generating a block.

By operating a plurality of tiers as described above, when the number of network nodes participating in the P2P network 109 increases, the blockchain smart contract system may block more smart contracts and include them in the blockchain during a unit time.

Hereinafter, a process of generating a block will be described with reference to FIG. 3.

The blockchain smart contract system may generate blocks according to the tier 1 310 in an order having periodicity. Each network node 110, 120, 130, 140 points to a consensus node that will generate a block within the connected P2P subnetwork 119, 129, 139, 149 when the order according to tier 1 310 arrives. can do. The process of pointing to a consensus node may be made based on the network reputation of each consensus node, which will be described later with reference to FIGS. 6 to 8.

The indicated consensus node may then generate a block containing the details of the smart contract. If the indicated consensus node generates a valid block in which the details of the smart contract have not been manipulated, compensation such as money or virtual currency may be paid. The indicated consensus node may inform the network node connected to the P2P subnetwork to which it is connected to the generation of the block. Informing the generation of the block, the generated block can be transmitted together. The network node notified that the block has been created includes: a smart contract node connected to itself and a P2P subnetwork; Other network nodes; And it can inform the consensus nodes connected to the P2P sub-network to which it is connected that the block has been generated, and transmit the generated block together in this process.

More specifically, according to tier 1 310, network node A 110 first establishes consensus node A1 111, consensus node A2 112, and consensus node A3 113 connected to P2P subnetwork A 119. You can specify the consensus node in which to create the block. For example, network node A 110 may point to consensus node A1 111.

Thereafter, the consensus node A1 111 may generate a block containing the contents of the smart contract. The consensus node A1 111 may inform the network node A 110 connected to the P2P sub-network A 119 of generating the block and transmit the generated block together. Network node A 110 may include smart contract node A 115; Network nodes B, C, and D (120, 130, 140); And the consensus nodes A2 and A3 (112, 113) can be informed that the block is generated, and can also transmit the block generated in the process.

Next, a process corresponding to the above process may be performed around the network node B 120, which is the next order, according to the tier 1 310. That is, the network node B 120 may designate an agreement node to generate a block among the agreement node B1 121, the agreement node B2 122, and the agreement node B3 123 connected to the P2P subnetwork B 129. have. For example, network node B 120 may point to consensus node B1 121.

Thereafter, the consensus node B1 121 may generate a block including the contents of the smart contract. The consensus node B1 121 may inform the network node B 120 connected to the P2P sub-network B 129 of generating a block and transmit the generated block together. Network node B 120 may include smart contract node B 125; Network nodes A, C, D (110, 130, 140); And the consensus nodes B2 and B3 122 and 123 may be notified that the block is generated, and the generated block may be transmitted together in this process.

Next, a process corresponding to the above process may be performed centering on the next turn network node C 130, and a process corresponding to the above process may be performed centering on the next turn network node D 140. Afterwards, a cycle in which a process corresponding to the above process is performed may be started again based on the network node A 130. On the other hand, when the number of network nodes increases, so that the time it takes for the network node A 110 to re-point the consensus node exceeds a certain time, for example, 1 second, block generation according to the tier 2 320 is also performed. Can be operated together.

4 is a diagram illustrating an operation of a client, a smart contract node, a network node, and a consensus node according to an embodiment.

For example, consider a case where a smart contract is concluded where client X 146 buys and sells property R owned by client Y 147.

In this case, first, network node 140 may generate a network reputation of consensus nodes 141, 142 (410). The network node 140 may generate, store, and update the network reputation of the consensus nodes 141, 142 on its own or in conjunction with the index server 100. A detailed process of generating a network reputation will be described later with reference to FIG. 8.

Next, details of the first smart contract may be transmitted (421).

Specifically, a smart contract may be concluded in which client X 146 sells real estate R owned by client Y 147; Client Y 147 may send all details of the smart contract to smart contract node D 145; The smart contract node D 145 may transmit the details of the smart contract corresponding to all or part of all the details of the smart contract to the network node D 140.

Network node D 140 generates a probability that each consensus node will point to a consensus node to generate a block based on the network reputation of consensus node D1 141 and the network reputation of consensus node D2 142, and then the probability Can select a consensus node to generate a block based on. Network node D 140 may send the details of the smart contract to the indicated consensus node.

For example, if the network reputation of consensus node D1 141 is 600 and the network reputation of consensus node D2 142 is 400, then the probability that consensus node D1 141 is designated as the consensus node to generate a block is 60%. And the probability that consensus node D2 142 will be identified as the consensus node to generate the block may be set to 40%. The network node D 140 may designate the consensus node D1 141 as the consensus node to generate a block based on the probability, and transmit the details of the smart contract to the consensus node D1 141.

Here, the details of the smart contract may be all the details of the smart contract signed by the clients 146 and 147, or may be the core contents of the smart contract. For example, if a smart contract is concluded in which client X 146 buys and sells property R owned by client Y 147, the details of the smart contract include at least “Ow. Payments and registrations, which are the core subjects of the smart contract, such as "the payment was made." And "The transfer of ownership of property R from client Y (147) to client X (146) was made on the same date." have.

Next, nodes of the blockchain system may include a block including the details of the first smart contract in the blockchain (431).

First, the agreement node D1 141 that has received the details of the first smart contract may generate a block including the details of the smart contract. The block includes bibliographic information on the block creation (block creation date, node that created the block, etc.); Breakdown of smart contracts; The hash key used to validate the block can be included. If the indicated consensus node generates a valid block in which the details of the smart contract have not been manipulated, compensation such as money or virtual currency may be paid.

The consensus node D1 141 may inform the network node D 140 connected to the P2P subnetwork D 149 of the block generation, and transmit the generated block together. The network node D 140 may inform the smart contract node D 145 and the consensus node D2 142 that the block has been generated, and may transmit the generated block together. Smart contract node D 145; Network node D 140; Consensus node D1 141; And consensus node D2 142 may include the block in the blockchain.

At this time, each node includes a block in the blockchain may be different.

Specifically, the smart contract node includes bibliographic information (block creation date, node that generated the block, etc.) related to block generation included basically in the received block; Breakdown of smart contracts; In addition to the hash key used to validate the block, all details of the smart contract between the clients stored by the smart contract node can be included in the received block as a reference. Hereinafter, such a block is called a full block. Smart contract nodes can include blocks in the blockchain in the form of full blocks. In short, the smart contract node D 145 includes in the blockchain a block that contains all the details of the smart contract between client X 146 and client X 146 in the block generated by consensus node D1 141. You can.

On the other hand, bibliographic information (block creation date, node that generated the block, etc.) related to block generation included in the block as a basis; Breakdown of smart contracts; A block composed of a hash key used for validating a block is called a medium block. The network node and the consensus node that created the block may include the block in the blockchain in the form of a medium block. In short, network node D 140 and consensus node D1 141 may include a medium block in the blockchain.

In addition, consensus nodes connected to the same P2P sub-network as the consensus node that generated the block may include bibliographic information (block creation date, node that generated the block, etc.) related to block generation included in the received block as a basis; Breakdown of smart contracts; In the hash key used when validating the block, only the information about the citation and the hash key except the details of the smart contract can be left in the block. Hereinafter, such a block is called a light block. Consensus nodes connected to the same P2P subnetwork as the consensus node that created the block may include the block in the blockchain in the form of a light block. In other words, the consensus node D2 142 may include a block except for the details of the smart contract in the block generated by the consensus node D1 141 in the blockchain. Meanwhile, consensus nodes connected to the P2P subnetwork different from the consensus node that generated the block may not include the block in the blockchain.

As such, the blockchain smart contract system is configured to include different blocks for each node role in the blockchain, thereby enabling role sharing between nodes. First, the smart contract node in charge of the region or country where the law is divided can collect all the information about the smart contract of a specific region or country. The network node having a high storage capacity may serve as a comprehensive database by collecting details of smart contracts obtained through the P2P network 109. Consensus nodes with good computing power generate blocks, but do not store large amounts of data in the blockchain, allowing hardware and software performance to be concentrated on computing power.

Next, the details of the second smart contract may be transmitted (422).

First, the network node D 140 may acquire the details of the second smart contract through the same process as the process 421. Then, if the network reputation of consensus node D1 141 is 600 and the network reputation of consensus node D2 142 is 400, the probability that consensus node D1 141 will be designated as the consensus node to generate a block will be set to 60%. And the probability that the consensus node D2 142 will be identified as the consensus node to generate the block may be set to 40%. Network node D 140 may point consensus node D2 142 as a consensus node to generate a block based on the probability, and send details of the smart contract to consensus node D2 142.

Next, nodes of the blockchain system may include a block including the details of the second smart contract in the blockchain (432). Specifically, after generating the block, the consensus node D2 142 may inform the network node D 140 connected to the P2P sub-network D 149 of generating the block, and transmit the generated block together. The network node D 140 may inform the smart contract node D 145 and the consensus node D1 141 that the block has been generated, and transmit the generated block together. Smart contract node D 145 is in the form of a full block; Network node D 140 and consensus node D2 142 are in the form of medium blocks; The consensus node D1 141 may include the block in the blockchain in the form of a write block.

5 is a diagram illustrating an operation of a network node and a consensus node according to an embodiment.

First, network nodes may generate a network reputation of consensus nodes (510, 520). Specifically, the consensus node A1 111 may transmit its performance data to the network node A 110 connected to itself and the P2P subnetwork A 119, and the network node A 110 may agree to the consensus node A1 111. Create a network reputation. Consensus Node B1 121 may transmit its performance data to Network Node B 120 connected to itself and to P2P Sub-Network B 129, and Network Node B 120 may have network reputation of Consensus Node B1 121. Can be generated. A detailed process of generating a network reputation based on the performance data will be described later with reference to FIG. 8.

Next, nodes of the blockchain system may include the block generated by the consensus node A1 111 in the blockchain (511). First, the network node A 110 points to the consensus node A1 111 as the consensus node to generate a block when the turn according to the tier 1 310 arrives, and the smart contract to the consensus node A1 111. The details of the smart contract obtained from the node A 115 may be transmitted. If the network node A 110 does not have the details of the acquired smart contract, it passes the selection of the consensus node to generate the block and waits until the turn according to tier 1 310 comes back.

The indicated consensus node A1 111 may include bibliographic information on block generation (block creation date, node which generated the block, etc.); Breakdown of smart contracts; After generating a block including information about a hash key and the like used for validating the block, the network node A 110 is notified of the block generation. At this time, a block generated by the consensus node A1 111 may be transmitted to the network node A 110.

Network node A 110 then informs network node B 120 connected to the P2P network 109 of block generation, and network node B 120 connects itself with consensus node B1 (connected to P2P sub-network B 129). 121) tell block creation. In this process, a block generated by network node A 110 may be transmitted to each node.

Nodes that receive the block can include the block in the blockchain. The network node A 110 and the network node B 120 may include the block in the block chain in the form of a medium block. The consensus node A1 111 that generated the block may also include the block in the blockchain in the form of a medium block. Consensus node B1 121 connected to another P2P subnetwork with consensus node A1 111 may not include the block in the blockchain.

Next, the nodes of the blockchain system may include the block generated by the consensus node B1 121 indicated by the network node B 120 in the blockchain (521). First, network node B 120 points to consensus node B1 121 as a consensus node to generate a block when it arrives in turn after network node A 110 according to tier 1 310. The node B1 121 may transmit the details of the smart contract obtained from the smart contract node B 125. If the network node B 120 does not have the details of the acquired smart contract, it passes the selection of the consensus node to generate the block and waits until the turn according to tier 1 310 comes back.

The identified consensus node B1 121 includes bibliographic information on block generation (block creation date, node that generated the block, etc.); Breakdown of smart contracts; After generating a block including information about a hash key and the like used when validating the block, the network node B 120 is notified of the block generation. At this time, the block generated by the consensus node B1 121 may be transmitted to the network node B 120.

Network node B 120 then informs network node A 110 connected to the P2P network 109 of block generation, and network node A 110 connects itself with consensus node A1 (connected to P2P subnetwork A 119). 111) tell block creation. In this process, a block generated by the network node B 110 may be transmitted to each node.

Nodes that receive the block can include the block in the blockchain. The network node B 120 and the network node A 110 may include the block in the block chain in the form of a medium block. The consensus node B1 121 that generates the block may also include the block in the blockchain in the form of a medium block. Consensus node A1 111 connected to another P2P subnetwork with consensus node B1 121 may not include the block in the blockchain.

By repeating the above process, each network node 110, 120, 130, 140 of the P2P network 109 has its own turn, and the network nodes 110, 129, 139, and 149 are connected to each other. Point out consensus nodes (111-113, 121-123, 131-133, 141-143) to generate blocks, and blocks created from the indicated consensus nodes are blockchain smart contracts through network nodes pointing to consensus nodes. May be sent to nodes in the system. The network nodes and the consensus node that created the block are in the form of a medium block; Consensus nodes connected to the same P2P subnetwork as the consensus node that created the block are in the form of a light block; And the smart contract node connected to the same P2P sub-network as the consensus node that created the block, the block may be included in the block chain in the form of a full block.

6 is a flowchart illustrating a process of including a block in a blockchain according to an embodiment.

The network node described with reference to FIG. 6 may be the network node D 140 described above, and the smart contract node may be the smart contract node D 145 described above. In each process described with reference to FIG. 6, portions that overlap with the contents described with reference to FIGS. 1 to 5 will not be repeated.

First, the network node 140 may obtain the details of the smart contract from the smart contract node that has received the details of the smart contract from the client which is the subject of the smart contract (610). For example, consider a case where a smart contract is concluded where client X 146 buys and sells property R owned by client Y 147. The smart contract node 145 may obtain all the details of the smart contract signed by the clients 146, 147. The smart contract node 145 may transmit to the network node 140 the details of the smart contract corresponding to all or some of all the details of the smart contract. The details of the smart contract include at least “Client X paid client Y on OO OO of OOOO.” And “Registered ownership transfer of property R from client Y (147) to client X (146) on the same date. It is possible to include the payment details or the registration details, which are the core contents of the smart contract.

Next, when the sequence number received from the index server arrives, the network node 140 may designate a consensus node that will generate a block including details of the smart contract among consensus nodes connected to the P2P subnetwork (620). . In this case, the order assigned by the index server 100 may be the order by the round robin list described with reference to FIGS. 1 and 3.

On the other hand, the process that the network node 140, which has arrived in turn, specifies the consensus node to generate a block may be a series of processes based on the network reputation of the consensus node. For example, the network node 140 may generate a block from the consensus nodes 141, 142, and 143 connected to the P2P subnetwork 149 based on the network reputation, and generate a block of the consensus node 141. Can be identified as a consensus node. On the other hand, a specific process of pointing to the consensus node to generate a block will be described later with reference to FIG.

The network node 140 may then transmit 630 the details of the smart contract to the indicated consensus node 141. The indicated consensus node 141 may generate a block including the details of the smart contract received from the network node 140. The block includes bibliographic information on the block creation (block creation date, node that created the block, etc.); Breakdown of smart contracts; The hash key used to validate the block can be included.

In the following order, a block containing the details of the smart contract may be obtained from the indicated consensus node 141 (640). The indicated consensus node 141 may inform the network node 140 connected to the P2P subnetwork D 149 to generate the block. At this time, the consensus node D1 141 may transmit the generated block together.

Next, the network node 140 blocks at least one of the smart contract node 145, the network nodes 110, 120, and 130 that are assigned the order from the index server 100, and consensus nodes connected to the P2P subnetwork. 650 may be transmitted. For example, network node 140 may send a block to consensus nodes 142, 143 included in P2P subnetwork 149 in addition to the indicated consensus node 141. Meanwhile, each of the network nodes 110, 120, and 130 receiving the block may inform consensus nodes of the P2P subnetwork to which it is connected that the block is generated, and transmit the generated block together. Specifically, network node A 110 may transmit a block informing block generation A1 111, consensus node A2 112, and consensus node A3 113 connected to P2P subnetwork A 119 and informing a block generation. ; Network node B 120 may send a block to the consensus node B1 121, consensus node B2 122, and consensus node B3 123 connected to the P2P sub-network B 129, informing block generation; The network node C 130 may transmit a block to the consensus node C1 131, the consensus node C2 132, and the consensus node C3 133 connected to the P2P sub-network C 139 and inform the block generation.

The consensus nodes 111-113, 121-123, 131-133, 142, and 143 that have received the generated block are not valid when the indicated consensus node 141 manipulates the contents of the smart contract in the process of generating the block. It may be set to check whether or not a block has been created. To this end, the other consensus nodes 111-113, 121-123, 131-133, 142, 143 are connected to the network node 140 via the P2P network 109 and the P2P subnetwork 119, 129, 139, 149. Alternatively, the smart contract node 145 may receive the details of the unmanaged smart contract and combine the details of the unmanaged smart contract with the hash key of the received block and apply it to a hash function such as SHA256. . At this time, by checking whether the output hash is output below a predefined value, the validity of the block generated by the indicated consensus node 141 may be checked. In addition, any other validating method may be borrowed as long as the consensus node 141 whose speed at which other consensus nodes check the validity of the block is faster than the speed at which the consensus node 141 generates a block.

If the indicated consensus node 141 has generated a valid block, the indicated consensus node 141 may be rewarded with money or virtual currency, and if it generates consecutive blocks more than a certain number of times, the indicated consensus node ( 141) may be added to the network reputation. On the other hand, if the indicated consensus node 141 generates an invalid block, it may give an added value to the network reputation of the indicated consensus node 141, and the indicated consensus node 141 generates an invalid block. The first consensus node that discovers that it has done so can give network reputation an advantage. In this case, as can be seen in the following description with reference to FIGS. 7 and 8, the consensus node has a high probability of being selected as a consensus node to generate a block, and when a valid block is generated by selecting a consensus node to generate a block. Rewards such as money, money or virtual currency can be given. By contributing network reputation to consensus nodes that have validated such invalid blocks, it is possible to engage consensus nodes to actively discover invalid blocks.

Subsequently, nodes of the blockchain smart contract system may include the block in the blockchain (660). At this time, the smart contract node D 145 is in the form of a full block; The network nodes 110, 120, 130, 140 and the indicated consensus node 141 are in the form of medium blocks; Consensus nodes 142 and 143 connected to the P2P subnetwork 149 in addition to the indicated consensus node 141 may include the block in the blockchain in the form of a light block. As such, the blockchain smart contract system may include different blocks for each node role in the blockchain, and specific effects thereof may be confirmed in the above description with reference to FIG. 4.

7 is a flowchart illustrating a process of pointing to a consensus node according to an embodiment.

The process of selecting a consensus node to generate a block may be performed in the network node 140 or in conjunction with the index server 100 managing the network node 140.

First, the network node 140 may obtain performance data of the consensus nodes 141, 142, and 143 (621). The network node 140 may obtain its performance data from each of the consensus nodes 141, 142, and 143 and transmit the performance data to the index server 100.

In this case, the performance data may include information about the network connection environment of the consensus node. In addition, the performance data may include information about the hardware specification of the consensus node. In addition, the performance data may include information about the observability, whether the consensus node can detect the state variables that make up the system from the measurable output state within a given time for the system equation problem. In addition, the performance data may include information about controllability, such as whether a consensus node can transform a particular initial state for the system equation problem into a desired final state within a given time.

Next, network node 140 or index server 100 may generate a network reputation of each consensus node, based on the performance data of each consensus node (622). The network reputation of each consensus node 141, 142, 143 may be represented numerically. For example, the network reputation of consensus node D1 141 is 600; The network reputation of consensus node D2 142 is 300; The network reputation of consensus node D3 143 may be generated in 100 days. However, these numbers are only examples, and the network reputation may be represented by integers, rational numbers, or real numbers as well as natural numbers. The process of generating the network reputation of the consensus nodes by the network node 140 or the index server 100 will be described later with reference to FIG. 8.

Subsequently, network node 140 or index server 100 may generate, based on the network reputation of each consensus node, the probability that each consensus node will be identified as the node that will generate the block (623). Specifically, the probability that each consensus node is designated as a node to generate a block may be generated through the weight of the network reputation of a specific consensus node in the total sum of the network reputations of all the consensus nodes. For example, the network reputation of consensus node D1 141 is 600; The network reputation of consensus node D2 142 is 300; If the network reputation of consensus node D3 143 is 100, then the probability that consensus node D1 141 is designated as the node to generate the block is 60%; The probability that the consensus node D2 142 will be designated as the node to generate the block is 30%; The probability that the consensus node D3 143 will be identified as the node to generate the block may be generated at 10%.

Probability generated based on network reputation is only an example, and the probability may be generated according to any other calculation method. Specifically, the probability may be generated based on a value obtained by multiplying the consensus node's network reputation with an incentive that increases with the consensus node's network reputation. For example, the network node 140 or the index server 100 may determine that the network reputation of the consensus node D1 141 is 600 times the incentive 1.6; The network reputation of consensus node D2 142 is equal to 300, the value of incentive 1.3; The network reputation of consensus node D3 143 may generate a probability that each consensus node will be identified as the node that will generate the block, based on the value 110 multiplied by 100 by incentive 1.1. In this case, the probability that the consensus node D1 141 is designated as the node to generate the block is 66%; The probability that the consensus node D2 142 will be designated as the node to generate the block is 27%; The probability that the consensus node D3 143 will be identified as the node that will generate the block may be generated at 7%. With this approach, the higher the network reputation, the greater the incentive, so the higher the network reputation, the higher the probability of being identified as the node that will generate the block. This may motivate consensus nodes to act to increase network reputation.

In the following order, based on the probabilities, one can point to a consensus node to generate a block (624). For example, the network node 140 based on a probability generated by itself or a probability generated by the index server 100 and then transmitted, the node D1 141, the node D2 142, and the node D3. From 143, it can be identified as a consensus node to generate a block. For example, the probability that the consensus node D1 141 will be designated as the node to generate the block is 60%; The probability that the consensus node D2 142 will be designated as the node to generate the block is 30%; The probability that the consensus node D3 143 will be identified as the node to generate the block may be 10%, and the network node 140 may agree on the consensus node D2 142 to generate the block in the current sequence according to a 30% probability. Can be identified as a node.

8 is a diagram for describing a process of generating a network reputation according to an exemplary embodiment.

8, consensus node D2 142 first connected to P2P sub-network D 149; Then connected consensus node D3 143; And then among the connected consensus nodes D1 141, the consensus node D1 141 may have the highest network reputation; Consensus node D2 142 may then have the next highest network reputation; Consensus node D3 143 may then have the next highest network reputation. In the following, the process of calculating the network reputation of each consensus node 141, 142, 143 is described.

First, the network reputation of the consensus node may be generated based on the performance data of the consensus node.

Here, the performance data may include information on the network connection environment of the consensus node. Information about the network connection environment may include whether the consensus nodes 141, 142, and 143 connect to the P2P subnetwork 149 via wire or wirelessly; If connected via wireless, a communication scheme (5G, WiFi, 3G, LTE, etc.); Internet speed; It may include information about Internet service providers.

In this case, the network reputation of the consensus node may include a number related to the responsiveness of the connection environment of the network of the consensus node. In detail, when the P2P subnetwork 149 is connected via a wire, a higher value may be given than when the P2P subnetwork 149 is connected via a wireless connection. In addition, if connected to the P2P sub-network 149 via wireless, it is possible to give the highest value when using 5G, and higher than LTE or 3G when using Wifi. In addition, the Internet speeds of the consensus nodes 141, 142, and 143 expressed in gigabytes per second (GBps) or megabytes per second (MBps) may be scaled and used as numerical values. In addition, it can be reflected in the numerical value by referring to the indicators such as the market share of the Internet service provider.

As such, the numerical values relating to the responsiveness of the network connection environment of the consensus nodes 141, 142, and 143 are included in the network reputation of the consensus node. Can be. Through this, since the consensus nodes 141, 142, and 143 having excellent network connection environments will be identified as nodes that generate blocks with high probability, a fast block generation speed and the like can be ensured.

Furthermore, the performance data may include information about hardware specifications of the consensus nodes 141, 142, and 143. Specifically, CPU type and performance of consensus nodes 141, 142, 143; The number, type and performance of the GPUs; The size of the RAM; Information about the clock speed may be included.

In this case, the network reputation of the consensus node may include a number relating to the availability of the hardware specification of the consensus node. Specifically, when the CPU model is the latest model and has a larger number of cores, a higher number can be given. In addition, the larger the number of GPUs, the more recent model, and the higher the value indicating the performance of other GPUs, the higher the number. In addition, the numerical value may reflect the clock number of the consensus nodes 141, 142, and 143 and the value of the scale of the RAM.

As such, the numerical values relating to the availability of the hardware specifications of the consensus nodes 141, 142, and 143 are included in the network reputation of the consensus node, so that the consensus nodes 141, 142, and 143 having excellent hardware specifications may have a higher network reputation. Through this, since the consensus nodes 141, 142, and 143 having excellent hardware specifications will be identified as nodes that generate blocks with high probability, a fast block generation speed and the like can be ensured.

Further, the performance data may include information about observability, whether the consensus nodes 141, 142, and 143 can find the state variables that make up the system from a measurable output state within a given time for a system equation problem. Can be. Specifically, the consensus nodes 141, 142, 143 may be provided with a system equation problem from the network node 140, and may perform a task of calculating the problem for a given time.

In this case, the network reputation of the consensus node may include a number related to the observability of the consensus node. Specifically, if the consensus nodes 141, 142, 143 have solved the system equation problem for a given time, a certain number of points may be given. In addition, when the consensus nodes 141, 142, and 143 solve the system equation problem, the value obtained by scaling the remaining time from the given total time may be used as a numerical value.

As such, by including the numerical values related to the observability of the consensus nodes 141, 142, and 143 in the network reputation of the consensus node, the consensus nodes 141, 142, and 143 having excellent work processing performance may have a higher network reputation. Through this, since the consensus nodes 141, 142, and 143 having excellent job processing performance will be designated as nodes that generate blocks with high probability, a fast block generation speed and the like can be ensured.

In addition, the performance data may include information about controllability, which is whether the consensus nodes 141, 142, and 143 can convert a specific initial state to a desired final state in a given time for a system equation problem. Specifically, the consensus nodes 141, 142, 143 may be provided with a system equation problem from the network node 140, and may perform a task of calculating the problem for a given time.

In this case, the network reputation of the consensus node may include a number related to the controllability of the consensus node. Specifically, if the consensus nodes 141, 142, 143 have solved the system equation problem for a given time, a certain number of points may be given. In addition, when the consensus nodes 141, 142, and 143 solve the system equation problem, the value obtained by scaling the remaining time from the given total time may be used as a numerical value.

As such, by including the numerical values related to the observability of the consensus nodes 141, 142, and 143 in the network reputation of the consensus node, the consensus nodes 141, 142, and 143 having excellent work processing performance may have a higher network reputation. Through this, since the consensus nodes 141, 142, and 143 having excellent job processing performance will be designated as nodes that generate blocks with high probability, a fast block generation speed and the like can be ensured.

In addition, the performance data may include information consisting of a combination of the above-mentioned performance data, in which case the network reputation of the consensus node may include a value consisting of a combination of the above-mentioned values. Thus, the responsiveness of the network connection environment of the consensus nodes 141, 142, 143; Availability of hardware specifications; Observability; And by including the numerical value related to the controllability in the network reputation of the consensus node, the consensus nodes 141, 142, and 143 having excellent work processing performance may have a high network reputation. Since the higher the network reputation of the consensus node, the higher the probability, the higher the probability of block generation.

Further, the network reputation of the consensus node may be given additional points or deductions depending on how the consensus nodes 141, 142 and 143 behave in the blockchain smart contract system. For example, if it is found that the consensus node 141 has generated an invalid block containing the details of the manipulated smart contract, the consensus node 141 will be deducted from the network reputation and pointed to the node that will later generate the block. Chances of becoming On the other hand, if the consensus node 142 continuously generates a valid block containing the details of the correct smart contract more than a certain number of times, the consensus node 142 may receive points from the network reputation and be designated as a node to generate a block later. The odds can go up.

In addition, by allowing only one consensus node to generate a block based on the probability based on the network reputation per smart contract, the fork phenomenon of the block can be avoided. A consensus node with a high network reputation will generate blocks with a high probability, and a high network reputation means that the consensus node has continuously generated valid blocks, so that the blocks generated by the indicated consensus nodes are primarily valid. do.

Furthermore, when a block is generated, all other consensus nodes other than the consensus node 141 that generated the block can validate the generated block and send the network to the first consensus node 143 that validated the invalid block. Can add reputation. Allows any consensus node to validate the block, and the first consensus node 143 that validates an invalid block adds value to the network reputation, thereby motivating the consensus nodes to verify each other's generated blocks. Through this, consensus nodes with high network reputation can create invalid blocks to prevent 51% attack to take over the blockchain system.

In this way, if the consensus node generates an invalid block, the deduction is applied to the network reputation, and if the contiguous node generates a valid block more than a predetermined number of times or if the invalid block is first verified, the network reputation may be added. This may prevent consensus nodes from generating invalid blocks that contain the details of the manipulated smart contract, and may encourage generating valid blocks that contain the details of the correct smart contract.

Through the above, a blockchain smart contract system having a network reputation proof as a consensus algorithm in which nodes participating in the blockchain smart contract system behaves and is evaluated based on the network reputation can be formed.

9 is an exemplary diagram of a configuration of an apparatus according to an embodiment.

Device 901 according to one embodiment includes a processor 902 and a memory 903. Device 901 according to an embodiment is the above-described index server 100, network nodes (110, 120, 130, 140), smart contract nodes (115, 125, 135, 145), consensus nodes (111-113, 121-123, 131-133, 141-143) or clients 146, 147. The processor may include at least one of the devices described above with reference to FIGS. 1 through 8, or may perform at least one method described above with reference to FIGS. 1 through 8. The memory 903 may store information related to the above-described method, or may store a program in which the above-described method is implemented. The memory 903 may be a volatile memory or a nonvolatile memory.

The processor 902 may execute a program and control the apparatus 901. Code of a program executed by the processor 902 may be stored in the memory 903. The device 901 may be connected to an external device (eg, a personal computer or a network) through an input / output device (not shown) and exchange data.

The embodiments described above may be implemented as hardware components, software components, and / or combinations of hardware components and software components. For example, the devices, methods, and components described in the embodiments may include, for example, processors, controllers, arithmetic logic units (ALUs), digital signal processors, microcomputers, field programmable gates (FPGAs). It may be implemented using one or more general purpose or special purpose computers, such as an array, a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to the execution of the software. For the convenience of understanding, a processing device may be described as one being used, but a person skilled in the art will appreciate that the processing device includes a plurality of processing elements and / or a plurality of types of processing elements. It can be seen that it may include. For example, the processing device may include a plurality of processors or one processor and one controller. In addition, other processing configurations are possible, such as parallel processors.

The method according to the embodiment may be embodied in the form of program instructions that can be executed by various computer means and recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the media may be those specially designed and constructed for the purposes of the embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and floppy disk servers 100. magneto-optical media such as) k), and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

The software may include a computer program, code, instructions, or a combination of one or more of the above, and configure the processing device to operate as desired, or process it independently or collectively. You can command the device. Software and / or data may be any type of machine, component, physical device, virtual equipment, computer storage medium or device in order to be interpreted by or to provide instructions or data to the processing device. Or may be permanently or temporarily embodied in a signal wave to be transmitted. The software may be distributed over networked computer systems so that they may be stored or executed in a distributed manner. Software and data may be stored on one or more computer readable recording media.

Although the embodiments have been described with reference to the accompanying drawings, those skilled in the art may apply various technical modifications and variations based on the above. For example, the described techniques may be performed in a different order than the described method, and / or components of the described systems, structures, devices, circuits, etc. may be combined or combined in a different manner than the described method, or other components. Or even if replaced or replaced by equivalents, an appropriate result can be achieved.

Therefore, other implementations, other embodiments, and equivalents to the claims are within the scope of the following claims.

Claims (5)

Obtaining the details of the smart contract from a smart contract node that has received the details of the smart contract from a client, which is the subject of the smart contract;
When the sequence number granted by the index server arrives, the consensus node that is to create a block including the details of the smart contract among consensus nodes connected to a P2P-sub network is indicated. Making;
Transmitting the details of the smart contract to the indicated consensus node;
Obtaining a block containing the details of the smart contract from the indicated consensus node;
Transmitting the block to at least one of the smart contract node, network nodes assigned a sequence number from the index server, and consensus nodes connected to the P2P subnetwork; And
Including the block in a blockchain;
Including;
Pointing to the consensus node to generate the block,
Obtaining performance data of the consensus nodes;
Generating a network reputation of each consensus node based on the performance data of each consensus node;
Based on the network reputation of each consensus node, generating a probability that each consensus node will be identified as a node to generate a block;
Based on the probabilities, pointing to a consensus node to generate a block;
Including,
Blockchain smart contract method that uses proof of network reputation as a consensus algorithm.
delete The method of claim 1,
The performance data of each consensus node includes information on the network connection environment of the consensus node.
The network reputation of each consensus node includes a numerical value relating to the responsiveness of the network connection environment of the consensus node.
Blockchain smart contract method that uses proof of network reputation as a consensus algorithm.
A computer program stored in a computer readable recording medium in combination with hardware to carry out the method of claim 1.
Obtain the details of the smart contract from the smart contract node (Smart Contract Node) received the details of the smart contract from the client (Client), the subject of the smart contract,
When the sequence number granted by the index server arrives, the consensus node that is to create a block including the details of the smart contract among consensus nodes connected to a P2P-sub network is indicated. and,
Send the details of the smart contract to the specified consensus node,
Obtaining a block containing the details of the smart contract from the indicated consensus node,
Transmit the block to at least one of the smart contract node, network nodes assigned a number from the index server, and consensus nodes connected to the P2P subnetwork;
Processor to include the block in the blockchain
Including;
The process for the processor to point to a consensus node to generate the block includes:
Obtaining performance data of the consensus nodes;
Based on the performance data of each consensus node, generate a network reputation of each consensus node,
Based on the network reputation of each consensus node, generating a probability that each consensus node will be identified as a node to generate a block,
A process of pointing to a consensus node to generate a block based on the probabilities
Including,
Blockchain smart contract device that uses proof of network reputation as a consensus algorithm.

Images