IDPF/Poplar1: Revisit use of bitvec::prelude::Lsb0 order
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 122
- Forks
- 34
- Avg merge
- 5h 25m
- Merged PRs (30d)
- 4
Description
Implementing Encode and Decode for Poplar1AggregationParam is suggesting that Lsb0 may have not been a good choice for bit ordering in various intermediate storage data types. We may want to revisit this in the future to simplify things.
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 examining the Encode and Decode implementations for Poplar1AggregationParam and the intermediate storage data types that use bitvec::prelude::Lsb0. Determine whether the bit ordering choice complicates those implementations and identify the affected uses. Done means reaching and documenting a decision on whether revisiting Lsb0 would simplify the design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100