feat: refactor empty range proofs and add more tests
Open
- Dominant language
- Go
- Stars
- 122
- Forks
- 53
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 5
Description
current code validates empty range proofs using `isValidEmptyRangeProof`. It is not very clear what is valid and what is not. Also, there is not enough test coverage for empty range proof.
Contributor guide
Research direction
Start by locating `isValidEmptyRangeProof` and reading how empty range proofs are currently validated. Review the existing proof tests, add coverage for valid and invalid empty range proofs, and consider the refactor complete when the validation intent is clearer and the expanded tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100