Is there any docs or words to explain way pr#142 change the leaf node from storing normal value to a hashed node?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 274
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
Description
relate to #142 and substrate pr https://github.com/paritytech/substrate/pull/9732
I don't know why you design this feature, to change the leaf node from storing a normal value to a hashed node related to threshold.
This change causes a migration for substrate node, but I do not understand this feature is necessary.
It seems that this feature uses one more hash to bring less cause for calculating state root? or something else?
I do not find any discuss for this. Can you explain more reason for this feature?
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
Start by reading issue #142 and the linked Substrate PR #9732 to understand the leaf-node change and its migration impact. Trace the rationale for hashed leaves, including the threshold and state-root implications mentioned here. Done means adding documentation that clearly explains why the change is necessary, its costs, and the migration consequences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100