Skip to main content
added 22 characters in body
Source Link
  1. Security is the same.

  2. Efficiency. Producing and transmitting Merkle proofs can become inefficient if the tree is too unbalanced.

On the other hand, an extremely unbalanced tree (where only only a single branch grows[1]) can be used in a hash-based signature scheme where it is expected that signatures are going to be very rare with likelihood of being singular - such that every signature bloatsincreases the size of all signatures that follow. If it's expected that a single signature is all that will ever be produced with the next oneoption to make more if necessary, it's a good (optimal?) scheme.

[1] /
/
/
/\

    /\
   /\
  /\
 /\  
  1. Security is the same.

  2. Efficiency. Producing and transmitting Merkle proofs can become inefficient if the tree is too unbalanced.

On the other hand, an extremely unbalanced tree (where only only a single branch grows[1]) can be used in a hash-based signature scheme where it is expected that signatures are going to be very rare with likelihood of being singular - such that every signature bloats the size of the next one.

[1] /
/
/
/\

  1. Security is the same.

  2. Efficiency. Producing and transmitting Merkle proofs can become inefficient if the tree is too unbalanced.

On the other hand, an extremely unbalanced tree (where only only a single branch grows[1]) can be used in a hash-based signature scheme where it is expected that signatures are going to be very rare with likelihood of being singular - such that every signature increases the size of all signatures that follow. If it's expected that a single signature is all that will ever be produced with the option to make more if necessary, it's a good (optimal?) scheme.

[1]

    /\
   /\
  /\
 /\  
Source Link

  1. Security is the same.

  2. Efficiency. Producing and transmitting Merkle proofs can become inefficient if the tree is too unbalanced.

On the other hand, an extremely unbalanced tree (where only only a single branch grows[1]) can be used in a hash-based signature scheme where it is expected that signatures are going to be very rare with likelihood of being singular - such that every signature bloats the size of the next one.

[1] /
/
/
/\