mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-26 01:47:55 +00:00
Francisco Aguirre
650886683d
If an XCM execution fails or ends with leftover assets, these will be trapped. In order to claim them, a custom XCM has to be executed, with the `ClaimAsset` instruction. However, arbitrary XCM execution is not allowed everywhere yet and XCM itself is still not easy enough to use for users out there with trapped assets. This new extrinsic in `pallet-xcm` will allow these users to easily claim their assets, without concerning themselves with writing arbitrary XCMs. Part of fixing https://github.com/paritytech/polkadot-sdk/issues/3495 --------- Co-authored-by: command-bot <> Co-authored-by: Adrian Catangiu <adrian@parity.io>
23 lines
988 B
Plaintext
23 lines
988 B
Plaintext
# Schema: Polkadot SDK PRDoc Schema (prdoc) v1.0.0
|
|
# See doc at https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/prdoc/schema_user.json
|
|
|
|
title: "Add `claim_assets` extrinsic to `pallet-xcm`"
|
|
|
|
doc:
|
|
- audience: Runtime User
|
|
description: |
|
|
There's a new extrinsic in `pallet-xcm` for claiming assets.
|
|
This means that if your assets ever get trapped while teleporting or doing reserve asset transfers,
|
|
you can easily claim them by calling this new extrinsic.
|
|
- audience: Runtime Dev
|
|
description: |
|
|
There's a new extrinsic in `pallet-xcm` that needs a new configuration item for its benchmarks.
|
|
It's a simple function in `pallet_xcm::benchmarking::Config`, `get_asset`, that returns a valid asset
|
|
handled by the AssetTransactor of the chain.
|
|
If you're already using `pallet-xcm-benchmarks`, then you already have this function there and can
|
|
just copy and paste it.
|
|
|
|
crates:
|
|
- name: pallet-xcm
|
|
- name: staging-xcm
|