Finalize input signature design
Open
Nobody has claimed this yet.
Consensus
- Dominant language
- C++
- Stars
- 22
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
We require a signature on all inputs just to combat rogue key attacks. Right now we're just using the same message on all inputs, but we may be able to use the input signature message in a more useful way (perhaps to prevent replay attacks?).
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
The issue names no files, tests, or entry points. Begin by tracing how input signatures are currently constructed and verified, then clarify the security requirements for rogue-key and replay attacks. Done means an agreed input-signature design with its security goals and implementation scope documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100