# Merkle signature scheme

In hash-based cryptography, the Merkle signature scheme is a digital signature scheme based on hash trees (also called Merkle trees) and one-time signatures such as the Lamport signature scheme. It was developed by Ralph Merkle in the late 1970s and is an alternative to traditional digital signatures such as the Digital Signature Algorithm or RSA.

The advantage of the Merkle signature scheme is that it is believed to be resistant against quantum computer algorithms. The traditional public key algorithms, such as RSA and ElGamal would become insecure in case an effective quantum computer can be built (due to Shor's algorithm). The Merkle signature scheme however only depends on the existence of secure hash functions. This makes the Merkle signature scheme very adjustable and resistant to quantum computing. Note that Merkle signature is a one time signature with finite signing potential; the work of Moni Naor and Moti Yung on signature based on one-way permutations and functions (and the invention of universal one-way hash function) give a way to extend a Merkle-like signature to a complete signature scheme.[citation needed]

## Key generation

The Merkle signature scheme can be used to sign a limited number of messages with one public key ${\text{pub}}$ . The number of possible messages must be a power of two, so we denote the possible number of messages as $N=2^{n}$ .

The first step of generating the public key ${\text{pub}}$ is to generate $N$ private/public key pairs $(X_{i},Y_{i})$ of some one-time signature scheme (such as the Lamport signature scheme). For each $1\leq i\leq 2^{n}$ , a hash value of the public key $h_{i}=H(Y_{i})$ is computed.

With these hash values $h_{i}$ a hash tree is built, by placing these $2^{n}$ hash values as leaves and recursively hashing to form a binary tree. Let $a_{i,j}$ denote the node in the tree with height $i$ and left-right position $j$ . Then, the hash values $h_{i}=a_{0,i}$ are the leaves. The value for each inner node of the tree is the hash of the concatenation of its two children. For example, $a_{1,0}=H(a_{0,0}||a_{0,1})$ and $a_{2,0}=H(a_{1,0}||a_{1,1})$ . In this way, a tree with $2^{n}$ leaves and $2^{n+1}-1$ nodes is built.

The private key of the Merkle signature scheme is the entire set of $(X_{i},Y_{i})$ pairs. One of the major problems with the scheme is that the size of the private key scales linearly with the number of messages to be sent.

The public key ${\text{pub}}$ is the root of the tree, $a_{n,0}$ . The individual public keys $Y_{i}$ can be made public without breaking security. However, as they are not needed in the public key, it is more practical to keep them secret to minimize its size.

## Signature generation

To sign a message $M$ with the Merkle signature scheme, the signer picks a key pair $(X_{i},Y_{i})$ , signs using the one-time signature scheme, and then adds additional information to prove that it was indeed one of the original key pairs (rather than one newly generated by a forger).

First, the signer chooses a $(X_{i},Y_{i})$ pair which had not previously been used to sign any other message, and uses the one-time signature scheme to sign the message, resulting in a signature ${\text{sig}}'$ and corresponding public key $Y_{i}$ . To prove to the message verifier that $(X_{i},Y_{i})$ was in fact one of the original key pairs, the signer simply includes intermediate nodes of the Merkle tree so that the verifier can verify $h_{i}=a_{0,i}$ was used to compute the public key $a_{n,0}$ at the root of the tree. The path in the hash tree from $a_{0,i}$ to the root be $n+1$ nodes, call them $A_{0},\ldots ,A_{n}$ , with $A_{0}=a_{0,i}=H(Y_{i})$ being a leaf and $A_{n}=a_{n,0}={\text{pub}}$ being the root.

We know that $A_{i}$ is a child of $A_{i+1}$ . To let the verifier calculate the next node $A_{i+1}$ given the previous, they need to know the other child of $A_{i+1}$ , the sibling node of $A_{i}$ . We call this node ${\text{auth}}_{i}$ , so that $A_{i+1}=H(A_{i}||{\text{auth}}_{i})$ . Hence, $n$ nodes ${\text{auth}}_{0},\ldots ,{\text{auth}}_{n-1}$ are needed, to reconstruct $A_{n}=a_{n,0}={\text{pub}}$ from $A_{0}=a_{0,i}$ . An example of an authentication path is illustrated in the figure on the right.

These nodes ${\text{auth}}_{0},\ldots ,{\text{auth}}_{n-1}$ , the $Y_{i}$ , and the one-time signature ${\text{sig}}'$ , together constitute a signature of $M$ using the Merkle signature scheme: ${\text{sig}}=({\text{sig}}'||Y_{i}||{\text{auth}}_{0}||{\text{auth}}_{1}||\ldots ||{\text{auth}}_{n-1})$ .

Note that when using Lamport signature scheme for signing, the ${\text{sig}}'$ contains a part of the private key $X_{i}$ .

## Signature verification

The receiver knows the public key ${\text{pub}}$ , the message $M$ , and the signature ${\text{sig}}=({\text{sig}}'||Y_{i}||{\text{auth}}_{0}||{\text{auth}}_{1}||\ldots ||{\text{auth}}_{n-1})$ . First, the receiver verifies the one-time signature ${\text{sig}}'$ of the message $M$ using the one-time signature public key $Y_{i}$ . If ${\text{sig}}'$ is a valid signature of $M$ , the receiver computes $A_{0}=H(Y_{i})$ by hashing the public key of the one-time signature. For $j=1,\ldots ,n-1$ , the nodes of $A_{j}$ of the path are computed with $A_{j}=H(A_{j-1}||{\text{auth}}_{j-1})$ . If $A_{n}$ equals the public key ${\text{pub}}$ of the Merkle signature scheme, the signature is valid.