KR101924026B1 - System and method for blockchain using hash-based signature scheme - Google Patents

Abstract

The present invention relates to a block chain system and method using a hash-based signature scheme. Each node of the block chain system includes: a transaction signature part which generates a transaction signature, which is a signature for a transaction using a hash-based signature scheme, and stores the transaction signature in the transaction; a block chain generation part which generates a merkle signature corresponding to each transaction to be included in the block, and generates a block including transactions in which the merkle signature is stored; and a transaction verification part which verifies the transaction signature of the transaction to be verified and verifies the transaction through verification of the merkle signature of the transaction to be verified. So, a block chain service can be provided.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to a block-

The following embodiments are intended to provide a structure having more robust quantum immunity characteristics than the conventional block chain structure.

Recently, block chaining has attracted the interest of encrypted money such as bit coin and etherium, and the interest of block chain, which is a security technology of encrypted money, is increasing. In the case of the existing financial transaction method, the validity of the transaction is confirmed by using a trusted third party (TTP) as an intermediary, while in the case of the block chain, by sharing the transaction book with all the network participants, The reliability of transactions is maintained by verifying the mutual transactions in the form of distributed public transaction books. A block chain is a concatenated block. Each block consists of transactions (transaction details) for a specific time, an algorithm related field, and an information field for the block. The right to create such a block generates a block by selecting a specific participant node (network participant) through a consensus algorithm (PoW, PoS, DpoS, etc.), and through this agreement algorithm, a malicious block generation due to monopolization of a specific participant is prevented .

Currently, ECDSA is used as a transaction - specific signature algorithm in the block chaining based on bit coin. However, the ECDSA (Elliptic Curve Digital Signature Algorithm) digital signature algorithm is based on the Discrete Logarithm Problem (DLP), which is an elliptic curve based cryptographic algorithm, and the discrete logarithm problem is based on the Shor's algorithm It is possible to attack within an efficient time. These problems make the existing block chain system vulnerable to the quantum computing environment.

Therefore, a robust tolerance transaction signature algorithm is required in a quantum computing environment.

However, (2017), block chain-based IoT device authentication scheme. Journal of the Korea Institute of Information Security and Cryptology, 27 (2), 343-351. (http://www.dbpia.co.kr/Journal/ArticleDetail/NODE07160266)

It is an object of the present invention to provide a method of generating a transaction signature based on a hash-based One Time Signature (OTS) algorithm having robust immunity even in a quantum computing environment.

Specifically, the present invention generates a transaction signature using a hash-based OTS algorithm, constructs a merge tree using the transaction's verification key, generates a merge signature for each transaction, and performs a two-step verification of the transaction signature and the merge root value It is intended to provide a method for verifying a transaction.

In order to achieve the above object, a node of a block-chain system applying a hash-based signature scheme according to an embodiment of the present invention generates a transaction signature, which is a signature of a transaction, using a hash-based signature scheme, To the transaction; A block generator for generating a block signature corresponding to each transaction to be included in the block and generating a block including transactions in which the header signature is stored; And a transaction verification unit for verifying the transaction signature of the transaction to be verified and verifying the transaction through verification of the merge signature of the transaction to be verified.

In this case, the node includes a block chain function unit for performing processing according to a consensus algorithm, connecting the generated block to a block chain, and configuring a block header; And a communication unit for communicating with other nodes of the block chain system to transmit and receive a transaction, and to share a block.

At this time, the transaction signature generator generates a pair of keys composed of a signature key and a verification key, generates the transaction signature using the transaction and the signature key based on a hash-based One Time Signature (OTS) algorithm, The transaction signature and the verification key may be stored in the transaction.

In this case, the block generator generates a merge tree by arranging a verification key of each transaction included in the block in the leaf node of the tree, stores the merge root value of the merge tree in the header of the block, Generate the merge signature of each of the transactions, and store the merge signature in each transaction to be included in the block.

At this time, the muffle signature may include a transaction signature, a verification key, and an authentication path, and the authentication path may be a value required to calculate the muckroot value without using the muckle tree.

At this time, the transaction verifier verifies the transaction signature stored in the transaction to be verified based on the hash-based One Time Signature (OTS) algorithm using the verification key stored in the transaction to be verified, If it is determined that the verification is successful, the verification of the merge signature stored in the transaction to be verified is performed, the merge root value is calculated using the verification key and the authentication path included in the merge signature, Header, and if the calculated muckroute value is equal to the stored muckroute value, it can be determined that the verification of the muckle signature is successful.

At this time, if the verification of the muffle signature is successful, the transaction verification unit can transmit to the network that verification of the transaction to be verified is successful.

At this time, if the verification on the transaction signature fails or the verification on the muffle signature fails, the transaction verifier can transmit to the network that the verification on the transaction to be verified has failed.

A method for verifying a transaction in a block-chain system applying a hash-based signature scheme according to an embodiment of the present invention includes generating a transaction signature that is a signature for a transaction using a hash-based signature scheme, storing the transaction signature in the transaction ; And generating a block including transactions in which the muck signature is stored, and verifying a transaction signature of a transaction to be verified among the transactions included in the block, And verifying the transaction through verification of the merge signature of the transaction to be verified.

The step of generating the transaction signature and storing the transaction signature in the transaction may comprise: generating a pair of keys comprising a signature key and a verification key; Generating the transaction signature using the transaction and the signature key based on a hash-based One Time Signature (OTS) algorithm; And storing the transaction signature and the verification key in the transaction.

The generating of the block may include: generating a merge tree by arranging a verification key of each transaction included in the block in a leaf node of the tree; Storing a merge root value of the merge tree in a header of the block; Generating the merge signature of each transaction to be included in the block; And storing the muckle signature in each of the transactions to be included in the block.

At this time, the muffle signature may include a transaction signature, a verification key, and an authentication path, and the authentication path may be a value required to calculate the muckroot value without using the muckle tree.

The verifying the transaction may include verifying a transaction signature stored in the transaction to be verified based on a hash-based One Time Signature (OTS) algorithm using the verification key stored in the transaction to be verified; If the transaction signature is successfully verified, confirming a muffle signature stored in the transaction to be verified; Calculating a merge root value using the verification key and the authentication path included in the muffle signature; Checking a merge root value stored in a block header of a corresponding block including the transaction to be verified; And comparing the calculated muckroute value with the stored muckroute value to determine that the verification of the muckle signature is successful if they are the same.

The verification of the transaction may further include transmitting to the network that verification of the transaction to be verified is successful if the verification of the muffle signature is successful.

Wherein verifying the transaction may further include transmitting to the network that verification of the transaction to be verified has failed, if verification of the transaction signature fails or verification of the couch signature fails have.

The present invention relates to a block-chaining system and method using a hash-based signature scheme, and has a robust effect on a quantum algorithm by using a hash-based signature scheme resistant to a quantum algorithm, In addition, it is possible to confirm the integrity of the entire transaction included in the block and whether the transaction includes a block, and since the signature generation and verification of the hash-based signature scheme is faster than that of the existing ECDSA, (SHA-256), it is possible to have a security strength that does not fall behind the existing digital signature algorithm (ECDSA) when a hash-based signature scheme is applied.

1 is a block diagram of a node of a block-chain system to which a hash-based signature scheme according to an embodiment of the present invention is applied.
2 is a diagram illustrating a method of calculating a muckroute value included in a block header in a block-chain system according to an embodiment of the present invention.
FIG. 3 is a view showing that, when a block is generated in a block-chain system according to an embodiment of the present invention, each transaction includes merge signature information.
4 is a diagram illustrating a process of verifying a transaction in two stages in a block chain system according to an embodiment of the present invention.
5 is a flowchart illustrating a process of generating a block and verifying a transaction in a node of a block chain system according to an embodiment of the present invention.
6 is a flowchart illustrating a process of generating a transaction signature at a node of a block-chain system according to an embodiment of the present invention.
7 is a flowchart illustrating a process of generating a block in a node of a block-chain system according to an embodiment of the present invention.
FIG. 8 is a flowchart illustrating a process of verifying a transaction in a node of a block-chain system according to an embodiment of the present invention.

It is to be understood that the specific structural or functional descriptions of embodiments of the present invention disclosed herein are only for the purpose of illustrating embodiments of the inventive concept, But may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein.

Embodiments in accordance with the concepts of the present invention are capable of various modifications and may take various forms, so that the embodiments are illustrated in the drawings and described in detail herein. However, it is not intended to limit the embodiments according to the concepts of the present invention to the specific disclosure forms, but includes changes, equivalents, or alternatives falling within the spirit and scope of the present invention.

The terms first, second, or the like may be used to describe various elements, but the elements should not be limited by the terms. The terms may be named for the purpose of distinguishing one element from another, for example without departing from the scope of the right according to the concept of the present invention, the first element being referred to as the second element, Similarly, the second component may also be referred to as the first component.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between. Expressions that describe the relationship between components, for example, "between" and "immediately" or "directly adjacent to" should be interpreted as well.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, the terms "comprises ", or" having ", and the like, are used to specify one or more other features, numbers, steps, operations, elements, But do not preclude the presence or addition of steps, operations, elements, parts, or combinations 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 to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the meaning of the context in the relevant art and, unless explicitly defined herein, are to be interpreted as ideal or overly formal Do not.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, the scope of the patent application is not limited or limited by these embodiments. Like reference symbols in the drawings denote like elements.

Hereinafter, a block-chaining system and method using a hash-based signature scheme according to an embodiment of the present invention will be described in detail with reference to FIGS. 1 to 8. FIG.

1 is a block diagram of a node of a block-chain system to which a hash-based signature scheme according to an embodiment of the present invention is applied.

1, a node 100 of a block chain system includes a control unit 110, a transaction signature generation unit 112, a block generation unit 114, a transaction verification unit 116, a block chain function unit 118, It is possible to secure the security of the blocks included in the block chain even in the quantum computing environment by generating a transaction signature using the hash-based signature scheme using the communication unit 120 and the storage unit 130. [

The communication unit 120 is a communication interface device including a receiver and a transmitter, and transmits and receives data by wire or wireless. The communication unit 120 transmits and receives transactions with other nodes included in the network of the block-chain system, and communicates to share blocks.

The storage unit 130 stores an operating system, an application program, and the like for controlling the overall operation of the node 100. The storage unit 130 may store blocks generated by the block generation unit 114 and block chains managed by the block chain system.

The transaction signature generator 112 generates a transaction signature, which is a signature for the transaction, using a hash-based signature technique, and stores the transaction signature in the transaction.

More specifically, the transaction signature generator 112 generates a pair of keys composed of a signature key and a verification key, generates a transaction signature using a transaction and a signature key based on a hash-based One Time Signature (OTS) algorithm, Store the transaction signature and verification key in the transaction.

The block generation unit 114 generates a muckle signature corresponding to each transaction to be included in the block, and generates a block including the transactions in which the muck signature is stored.

More specifically, the block generation unit 114 generates a merge tree by arranging the verification keys of the respective transactions to be included in the block in the leaf nodes of the tree as shown in the example of FIG. 2 below, .

2 is a diagram illustrating a method of calculating a muckroute value included in a block header in a block-chain system according to an embodiment of the present invention.

Referring to FIG. 2, the block generator 114 generates a verification key (Y _A , Y _B , Y _C , and Y _D ) of each of the transactions 211, 212, 213, , 222, 223, and 224 and hash. The new parent nodes 231 and 232 are generated by hashing the data obtained by concatenating the leaf nodes 221, 222, 223 and 224 two by two, and the new parent nodes 231 and 232 are repeatedly calculated to store the muckle root value 204 in the header of the block do.

The structure of the block generated by the block generation unit 114 is roughly divided into four blocks. A 4-byte block size field 201 indicating the total block size, a total of 80 bytes of a block header field, a transaction number field 208 having a variable size of 1 to 9 bytes indicating the number of transactions stored in the block, And a transaction field for storing transactions 211, 212, 213, and 214.

The details of the configuration of the block header are as follows. First, the version field 202 consisting of 4 bytes indicates an upgrade version for the block chain software or the protocol to be used.

The previous block header size field 203 composed of 32 bytes stores a value obtained by hashing a portion of the block header (80 bytes) before the current block in the block chain. At this time, the previous block header is hashed using the SHA-256 hash function based on the block coin of the bit coin.

The merge root field 204 composed of 32 bytes constitutes a merge tree using all the transactions stored in the corresponding block, stores the root value of the tree, verifies the integrity of all the transactions held by the block, It can be confirmed whether it is included in the block or not.

A time stamp field 205 consisting of 4 bytes is a field indicating the block creation time, and stores a value calculated in seconds from the Unix base date.

The difficulty target field 206 and the nonce field 207 each consisting of 4 bytes are used in the process of mining.

In terms of mining, mining produces electronic money, verifies the validity of the transaction on the block, and connects the block to the block chain. Numerous miners participate in the mining process, and the coins are obtained through compensation mechanisms among numerous miners, and blocks are created and miners are connected to the block chain. This consensus mechanism is achieved through the proof of work in the bit coin, and the hash cash problem is used as proof of work. As the computing performance improves, the hash cash problem is quickly solved. In this case, the time to solve the hash cash problem can be adjusted by modifying the difficulty target field value.

3, the block generator 114 generates a header signature of each transaction to be included in the block, and stores the header signature in each transaction to be included in the block.

FIG. 3 is a view showing that, when a block is generated in a block-chain system according to an embodiment of the present invention, each transaction includes merge signature information.

Referring to FIG. 3, the block generator 114 generates and stores a muckle signature for each transaction. For example, for a transaction (T _X A) transaction signature (T _X A σ _OTS), verification key (Y _A), and the certification path transaction to generate a meokeul signature containing _{(Hash (Y B), H} CD) (T _X A).

At this time, the authentication path (AP) (A _s = {a ₀ , ..., a _H-1 }) is a value required to calculate the muckroute value 204 without a merge tree, Represents the sibling node of the node having the height h on the authentication path, and the authentication path index calculation formula is as follows.

[Equation 1]

The transaction verification unit 116 verifies the transaction signature of the transaction to be verified (verification step 1) and verifies the transaction through verification of the merge signature of the transaction to be verified (verification step 2) as shown in the example of FIG. 4 below .

4 is a diagram illustrating a process of verifying a transaction in two stages in a block chain system according to an embodiment of the present invention.

Referring to FIG. 4, the transaction verifying unit 116 can finally verify the transaction through two checks: a verification step 1 for verifying a transaction signature and a verification step 2 for a merge signature verification of a transaction.

In the first verification step, the transaction verifying unit 116 uses the verification key 410 stored in the transaction to be verified to generate a transaction stored in the transaction 411 to be verified based on the hash-based OTS (One Time Signature) The signature 413 can be verified.

More specifically, a value obtained by hashing 412 the transaction 411 and a verification key of the transaction 411 based on the hash-based One Time Signature (OTS) algorithm 414 and the transaction signature 413 are generated, If the verification key is compared with the verification key 410 stored in the transaction 411, it can be determined that the transaction signature 413 has succeeded in verification.

In the second verification step, the transaction verification unit 116 confirms the merge signature stored in the transaction to be verified and verifies the verification key 421 and the authentication paths 423 and 423 included in the Muffle signature, And checks the merge root value 420 stored in the block header of the corresponding block including the transaction to be verified. If the calculated merge root value 426 and the stored merge root value 426 are identical, (420) are the same, it can be judged that the verification of the muffle signature is successful. More specifically, the transaction verifier 116 hash 424 the authentication path 423 with the hash 422 of the verification key 421 to compute the merge root value 426, and the hash value 424 And the authentication path 425 to calculate the muckle value 426. [

At this time, if the transaction verification unit 116 succeeds in verification of the muffle signature, it can transmit to the network that the verification of the transaction to be verified is successful.

If the transaction verifier 116 fails verification of the transaction signature or fails verification of the muffle signature, it may transmit to the network that the verification of the transaction to be verified has failed.

The block chain function unit 118 performs a process according to a consensus algorithm, and connects the generated block to a block chain and constitutes a block header.

The controller 110 can control the overall operation of the node 100. [ The controller 110 may perform functions of the transaction signature generation unit 112, the block generation unit 114, the transaction verification unit 116, and the block chain function unit 118. The control unit 110, the transaction signature generation unit 112, the block generation unit 114, the transaction verification unit 116, and the block chain function unit 118 are separately shown to distinguish the functions. Accordingly, the control unit 110 includes at least one processor configured to perform the functions of the transaction signature generation unit 112, the block generation unit 114, the transaction verification unit 116, and the block chain function unit 118 . The control unit 110 may also be configured to perform at least one of the functions of the transaction signature generation unit 112, the block generation unit 114, the transaction verification unit 116 and the block chain function unit 118, Of processors.

Hereinafter, a method of generating a block and verifying a transaction in a node of the block chain system according to the present invention will be described with reference to the drawings.

5 is a flowchart illustrating a process of generating a block and verifying a transaction in a node of a block chain system according to an embodiment of the present invention.

Referring to FIG. 5, the node 100 of the present invention generates a transaction signature that is a signature for a transaction using a hash-based signature scheme, and stores the transaction signature in a transaction (510). A more specific process of generating a transaction signature to which a hash-based signature scheme is applied will be described later with reference to FIG.

The node 100 may then generate a muckle signature corresponding to each of the transactions to be included in the block, and generate a block containing transactions in which the muckle signature is stored (520). A more concrete process of generating a block to which the hash-based signature scheme is applied will be described later with reference to FIG.

Then, the node 100 can verify the transaction signature of the transaction to be verified among the transactions included in the block, and verify the transaction through verification of the merge signature of the transaction to be verified 530. A more specific process of verifying a transaction to which a hash-based signature scheme is applied will be described later with reference to FIG.

6 is a flowchart illustrating a process of generating a transaction signature at a node of a block-chain system according to an embodiment of the present invention.

Referring to FIG. 6, the node 100 generates 610 a pair of keys comprising a signature key and a verification key to generate a transaction signature.

Then, the node 100 generates a transaction signature using a transaction and a signature key based on a hash-based One Time Signature (OTS) algorithm (612).

The node 100 then stores the transaction signature and the verification key in the transaction (614).

7 is a flowchart illustrating a process of generating a block in a node of a block-chain system according to an embodiment of the present invention.

Referring to FIG. 7, a node 100 generates a merge tree by placing a verification key of each transaction included in a block in a leaf node of a tree to generate a block (710).

The node 100 then computes the muckroot value located at the root of the muckree tree (712).

Then, the node 100 stores the merge root value of the merge tree in the header of the block (714).

Then, the node 100 generates a muckle signature of each transaction to be included in the block, and the node 100 stores the muckle value of the muckree in the header of the block (716). At this time, the muffle signature includes the transaction signature, the verification key, and the authentication path, where the authentication path represents the value required to calculate the muckroot value without the muckle tree.

Then, the node 100 stores a merge signature in each transaction to be included in the block (718).

Then, the node 100 checks or generates other information (version, previous block header hash, time stamp, difficulty goal, nonce, etc.) stored in the block header (step 720).

The node 100 generates a block header using the information confirmed and generated in step 720 and the merge root value, and stores the transactions including the merge signature in the payload of the block to generate a block (722).

FIG. 8 is a flowchart illustrating a process of verifying a transaction in a node of a block-chain system according to an embodiment of the present invention.

Referring to FIG. 8, when an event for verifying a transaction included in a block occurs, the node 100 performs a verification based on a hash-based One Time Signature (OTS) algorithm using a verification key stored in a transaction to be verified (810). ≪ / RTI >

In step 810, the node 100 verifies whether the transaction signature has been successfully verified as a result of the verification of the transaction node (step 812).

If it is determined in step 812 that the transaction signature is successfully verified, the node 100 confirms the coupon signature stored in the transaction to be verified (814).

Then, the node 100 calculates the muckle value using the verification key and the authentication path included in the muckle signature (816).

Then, the node 100 confirms the value of the muckle stored in the block header of the corresponding block including the transaction to be verified (818).

The node 100 then verifies the muckle signature by comparing the calculated muckroot value with the stored muckroot value (820).

Then, the node 100 confirms whether the verification of the muffle signature is successful (822) whether the calculated muffle value and the stored muffle value are the same.

If it is determined in step 822 that the calculated muckle value is the same as the stored muckle value, the node 100 determines that the verification of the transaction to be verified is successful. (824).

If the verification of the transaction signature is unsuccessful as a result of step 812, or if the verification of the merge signature fails in step 822, the node 100 determines that the verification of the transaction to be verified has failed, (826).

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. The apparatus and components described in the embodiments may be implemented, for example, as a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA) unit, 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 execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be permanently or temporarily embodied in a transmitted signal wave. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in 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 to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, 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 machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI > or equivalents, even if it is replaced or replaced.

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

100; Node in a block-chain system
110; The control unit
112; The transaction signature generation unit
114; The block-
116; The transaction verification unit
118; Block Chain Function
120; Communication section
130; The storage unit

Claims (16)

A transaction signature generator for generating a transaction signature that is a signature for a transaction using a hash-based signature scheme, and storing the transaction signature in the transaction;
A block generator for generating a block signature corresponding to each transaction to be included in the block and generating a block including transactions in which the header signature is stored; And
A transaction verification unit for verifying a transaction signature of a transaction to be verified and verifying a transaction through verification of a merge signature of the transaction to be verified;
A node in a block - chain system applying a hash - based signature scheme that includes.
The method according to claim 1,
A block chain function unit for performing processing according to a consensus algorithm, connecting a generated block to a block chain, and configuring a block header; And
A communication unit that transmits and receives a transaction with other nodes of the block chain system,
A node of a block-chain system applying a hash-based signature scheme further comprising:
The method according to claim 1,
Wherein the transaction signature generator comprises:
Generating a pair of keys comprising a signature key and a verification key, generating the transaction signature using the transaction and the signature key based on a hash-based One Time Signature (OTS) algorithm, Store in a transaction
A node in a block - chain system applying a hash - based signature scheme.
The method according to claim 1,
Wherein the block generator comprises:
Wherein a merge tree of the merge tree is stored in the header of the block, and the merge signature of each of the transactions to be included in the block is stored in the header of the block. And stores the muck signature in each of the transactions to be included in the block
A node in a block - chain system applying a hash - based signature scheme.
5. The method of claim 4,
The above-
A transaction signature, a verification key, and a certification path, the certification path being required to calculate the muckrou value without the mucktree
A node in a block - chain system applying a hash - based signature scheme.
The method according to claim 1,
Wherein the transaction verifying unit comprises:
Wherein the signature verification unit verifies the transaction signature stored in the transaction to be verified based on a hash-based One Time Signature (OTS) algorithm using the verification key stored in the transaction to be verified, and if the verification of the transaction signature is successful, The method includes verifying a merge signature stored in a transaction, calculating a merge root value using the verification key and the authentication path included in the merge signature, and calculating a merge root value stored in a block header of the corresponding block including the transaction to be verified And compares the calculated muffle root value with the stored muffle root value to determine that the verification of the muffle signature is successful
A node in a block - chain system applying a hash - based signature scheme.
The method according to claim 6,
Wherein the transaction verifying unit comprises:
If the verification of the merge signature is successful, it is transmitted to the network that verification of the transaction to be verified is successful
A node in a block - chain system applying a hash - based signature scheme.
The method according to claim 6,
Wherein the transaction verifying unit comprises:
If verification on the transaction signature fails or verification on the muckle signature fails, it is transmitted to the network that verification of the transaction to be verified has failed
A node in a block - chain system applying a hash - based signature scheme.
Generating a transaction signature that is a signature for the transaction using a hash-based signature scheme, and storing the transaction signature in the transaction;
Generating a muckle signature corresponding to each of the transactions to be included in the block, and generating a block including the transactions in which the muck signature is stored; and
Verifying a transaction signature of a transaction to be verified among the transactions included in the block and verifying a transaction through verification of a merge signature of the verified transaction
A method for verifying a transaction in a block-chain system employing a hash-based signature scheme.
10. The method of claim 9,
Generating the transaction signature and storing the transaction signature in the transaction comprises:
Generating a pair of keys comprising a signature key and a verification key;
Generating the transaction signature using the transaction and the signature key based on a hash-based One Time Signature (OTS) algorithm; And
Storing the transaction signature and the verification key in the transaction
A method for verifying a transaction in a block-chain system employing a hash-based signature scheme.
10. The method of claim 9,
Wherein the generating the block comprises:
Generating a merge tree by arranging a verification key of each transaction included in the block at a leaf node of the tree;
Storing a merge root value of the merge tree in a header of the block;
Generating the merge signature of each transaction to be included in the block; And
Storing the merge signature in each transaction to be included in the block
A method for verifying a transaction in a block-chain system employing a hash-based signature scheme.
12. The method of claim 11,
The above-
A transaction signature, a verification key, and a certification path,
Wherein the authentication path is necessary to calculate the muckroot value without the muckle tree
A method of verifying a transaction in a block - chain system applying a hash - based signature scheme.
10. The method of claim 9,
Wherein verifying the transaction comprises:
Verifying the transaction signature stored in the transaction to be verified based on a hash-based One Time Signature (OTS) algorithm using the verification key stored in the transaction to be verified;
If the transaction signature is successfully verified, confirming a muffle signature stored in the transaction to be verified;
Calculating a merge root value using the verification key and the authentication path included in the muffle signature;
Checking a merge root value stored in a block header of a corresponding block including the transaction to be verified; And
Comparing the calculated muffle root value with the stored muffle root value and determining that the verification of the muffle signature is successful if it is the same
A method for verifying a transaction in a block-chain system employing a hash-based signature scheme.
14. The method of claim 13,
Wherein verifying the transaction comprises:
If the verification of the muffle signature is successful, transmitting to the network that verification of the transaction to be verified is successful
A method for verifying a transaction in a block-chain system employing a hash-based signature scheme.
14. The method of claim 13,
Wherein verifying the transaction comprises:
Transmitting to the network that verification of the transaction to be verified has failed, if verification of the transaction signature fails or verification of the couch signature fails;
A method for verifying a transaction in a block-chain system employing a hash-based signature scheme.
A computer-readable recording medium having recorded thereon a program for executing the method according to any one of claims 9 to 15.

Images