Make a strict specification and 1.0 release
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 274
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
Description
Since trie logic is now part of the consensus, to avoid future reimplementation of similar prs (https://github.com/paritytech/trie/pull/42), implementation should follow strict specification and then never change in observable way.
Contributor guide
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 identifies trie logic as consensus-critical and asks for a strict specification followed by a 1.0 release. No files, tests, or concrete acceptance criteria are named; first review the existing trie implementation and related pull request #42, then establish observable behavior and release criteria with maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100