sunny-g/Lamport-Merkle.js

Issues

• deploy to NPM

  #9 opened 9 years ago by sunny-g
  0

• [research] CMSS - generating Lamport private keys from seed to avoid storing all private keys

  #7 opened 9 years ago by sunny-g
  0

• [research] GMSS

  #8 opened 9 years ago by sunny-g
  0

• refactor Lamport.sign to publish the pubKey in the signature

  #3 opened 10 years ago by sunny-g
  2

• Use an ancestor tree instead of array of arrays for storing the hashes in the Merkle tree

  #6 opened 10 years ago by sunny-g
  0

• refactor to use Browserify

  #5 opened 10 years ago by sunny-g
  0

• use a single 16kb Buffer for Lamport._privKey instead of 256 * 64 byte Array tuples

  #4 opened 10 years ago by sunny-g
  0

• break out of the Lamport verification process if at any point the hashed number doesn't match the public key hash

  #1 opened 10 years ago by sunny-g
  0

• give user a warning if they're about to use their last key (instead of throwing an error)

  #2 opened 10 years ago by sunny-g
  0