paritytech / paritytech/frame-decode
Add end to end decode examples
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
It'd be great if we had a couple of example binaries in this folder which use the absolute minimum of code to decode a specific block or storage entry from an RPC node.
Perhaps we'll end up with two separate commands/binaries like:
decode_storage --block 1234 --pallet System --entry Accounts --types types/polkadot_types.yaml --url wss://rpc.polkadot.iodecode_block --block 1234 --types types/polkadot_types.yaml --url wss://rpc.polkadot.io
These commands wouldn't do anything clever or have great error handling or whatever; just print basic information on decoding. To see the required logic we can look at the more complicated subcommands in https://github.com/jsdw/polkadot-historic-decoding-example/tree/main/src/commands.
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 existing example binaries in this folder and the more complicated subcommands in polkadot-historic-decoding-example/src/commands. Trace the minimum logic needed to connect to the RPC node and decode a block or storage entry using the supplied types file. Done means two commands accept the proposed arguments and print basic decoded information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100