Use of hedged signatures
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
Peer id specs currently enforce RFC-6979 for creating signatures.
Ed25519 signatures follow the normal Ed25519 standard.
then sign it using the standard Bitcoin EC signature algorithm (BIP0062
then sign it with the ECDSA standard algorithm
Meanwhile there is an attempt to improve the security of signing via "hedging" with additional entropy:
https://datatracker.ietf.org/doc/draft-irtf-cfrg-det-sigs-with-noise/
Should the spec be relaxed to allow for use of this?
Related:
- article describing hedged signatures: https://paulmillr.com/posts/deterministic-signatures/
- PR where this issue was raised: https://github.com/ChainSafe/zig-discv5/pull/1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the peer ID signature requirements described in this issue alongside RFC 6979, RFC 8032, BIP0062, and the linked hedged-signature draft. Check the related ChainSafe/zig-discv5 pull request for context. Done means reaching and documenting a decision on whether the specification should allow additional signing entropy.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100