-
Notifications
You must be signed in to change notification settings - Fork 683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add claim_assets
extrinsic to pallet-xcm
and make it available in next runtime release
#3495
Comments
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 #3495 --------- Co-authored-by: command-bot <> Co-authored-by: Adrian Catangiu <adrian@parity.io>
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 #3495 --------- Co-authored-by: command-bot <> Co-authored-by: Adrian Catangiu <adrian@parity.io>
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 paritytech#3495 --------- Co-authored-by: command-bot <> Co-authored-by: Adrian Catangiu <adrian@parity.io>
Merged to the fellows main as a part of polkadot-fellows/runtimes#187 What about backport to 1.8.0? |
I am generally against unneeded/unrequested backports. We could do it lazily when someone requests it. We know that for system runtimes we don’t need it in 1.8 |
Fixed in polkadot-fellows/runtimes#187 |
yes, agree, but if we want to release next polkadot 1.3.0 just with 1.8.0 (without 1.9.0) we will need to backport anyway |
i think i need this, i have an issue that requires claiming 1499 DOT that just got trapped in Polkadot chain, the call i have curated cannt be called because it would exhaust block limits. can someone give me a pointer? |
Yes, you need this, also answered on SE. |
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Motivation
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.
Request
Add new extrinsic in
pallet-xcm
to allow users to easily claim their assets, without concerning themselves with writing arbitrary XCMs.Backport the solution to polkadot-sdk v1.7.0, release patched
pallet-xcm
crate, add it to https://github.com/polkadot-fellows/runtimes to make it available with upcoming v1.2.0 runtimes release.Solution
claim_assets
extrinsic topallet-xcm
#3403Are you willing to help with this request?
Yes!
The text was updated successfully, but these errors were encountered: