paritytech / paritytech/smoldot
chain_getBlockHash not implemented properly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 328
- Forks
- 81
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 13
Description
chain_getBlockHash is very problematic to implement. If the JSON-RPC client requests for example block number 2,000,000 while the head is for example around 9,000,000 then we have no reasonable way to know it.
Asking a full node for the block with that number works, but because we have no proof of ancestry we have no guarantee that this block is the correct one.
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 locating the chain_getBlockHash JSON-RPC handling and reviewing how block-number lookups establish ancestry. The issue does not name files, tests, or a specific implementation path; done would require a defined way to verify that the requested block belongs to the canonical chain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, blockchain
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100