AssetHub Migration: move documentation, tests and examples to reference AssetHub instead of relay chain
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 293
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 3
Description
When Polkadot relay chain functionality is due to migrate to AssetHub, we should:
- Update examples and documentation around Subxt to make use of AssetHub rather than the relay chain (including light client chainspecs).
- Make it simpler for users to instantiate an AssetHubConfig, or provide one out of the box if possible (will be useful in order to do 1). This is complicated by the fact that our current attempts to build an AssetHubConfig rely on generated code to provide the AssetId type (a fairly complex MultiLocation type.
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 Subxt examples, documentation, tests, and generated code referenced in the issue, then inspect how AssetHubConfig and its AssetId are currently constructed. Confirm the migration scope for relay-chain references and verify that AssetHub examples, light-client chainspecs, tests, and documentation use the new configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, documentation, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100