Support merkalised metadata?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 293
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 3
Description
Do we want Subxt to be able to accept some merkalized metadata "proof" and use it to decode an extrinsic?
This would allow Subxt to be used in signers which are only passed this merkalized metadata and some TX bytes, and then decode this payload in order to show to the user, as well as then sign the TX taking this metadata proof hash into account.
Needs thought!
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 reading the issue discussion and the linked merkleized-metadata project. Clarify how Subxt should accept a metadata proof, decode extrinsic bytes, and account for the proof hash when signing. Done requires an agreed design and implementation scope for signer use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100