Increase sequence id on failed operation
Open
- Dominant language
- Go
- Stars
- 44
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
When an operation fails but the signature was legit, e.g. an attempt to overdraft, we should increase the sequence ID, otherwise replay attacks are made possible.
Contributor guide
Research direction
Start by locating the sequence ID handling for failed operations and the validation path for legitimate signatures, then trace the overdraft example described in the issue. Done means a legitimately signed operation that fails still advances the sequence ID and replay attacks are no longer possible; no file or test is named, so the relevant coverage must first be identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100