Skip to content

fix: support LOG_LIFETIME = 2 in generalized XMSS - #64

Open
devfelipenunes wants to merge 1 commit into
leanEthereum:mainfrom
devfelipenunes:fix/xmss-log-lifetime-two
Open

devfelipenunes wants to merge 1 commit into
leanEthereum:mainfrom
devfelipenunes:fix/xmss-log-lifetime-two

Conversation

@devfelipenunes

Copy link
Copy Markdown

Summary

  • Allow even Merkle tree depths of 2 when constructing XMSS bottom trees, matching GeneralizedXMSSSignatureScheme::key_gen's documented minimum LOG_LIFETIME.
  • Add a deterministic regression test that generates a key, signs, and verifies all four epochs at LOG_LIFETIME = 2.

Closes #62

Validation

  • cargo test --lib: 112 passed, 0 failed, 1 ignored.
  • cargo fmt --check
  • git diff --check
  • cargo clippy --all-targets --all-features -- -D warnings reports three existing must_use_candidate warnings in src/symmetric/message_hash/poseidon.rs and src/symmetric/tweak_hash/poseidon.rs, unrelated to this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GeneralizedXMSSSignatureScheme accepts LOG_LIFETIME = 2, but key_gen panics in new_bottom_tree

1 participant