paritytech / paritytech/json-rpc-interface-spec
block number to hash
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 37
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
It's not uncommon for people to want to query from a particular block number rather than hash.
Currently this is possible with the 'legacy' rpc mechanism in subxt to get a block hash for a particular block number, but is there a non-legacy mechanism?
(I saw on the subxt lounge element room that it's not uncommon to want to do such a thing and currently it's not as easy as it ought to be.)
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 reviewing the JSON-RPC interface specification and the existing legacy RPC path referenced in the issue. Determine whether a non-legacy block-number-to-hash query should be specified; done means the accepted mechanism and its interface requirements are documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100