Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

XCM: Asset trap to avoid accidental burning of Holding Register contents #3694

Closed
gavofyork opened this issue Aug 23, 2021 · 0 comments · Fixed by #3727
Closed

XCM: Asset trap to avoid accidental burning of Holding Register contents #3694

gavofyork opened this issue Aug 23, 2021 · 0 comments · Fixed by #3727

Comments

@gavofyork
Copy link
Member

No description provided.

@gavofyork gavofyork mentioned this issue Aug 23, 2021
Closed
47 tasks
@gavofyork gavofyork changed the title Provide a new XCM Order::AssetTrap, which places any remaining assets in the holding account into a special storage item (keyyed under the origin location), even (especially) in the case of error. A secondary XCM instruction DrainTrap can fetch those assets and do something with them. XCM: Asset trap to avoid accidental burning of Holding Register contents Aug 23, 2021
@gavofyork gavofyork mentioned this issue Aug 26, 2021
Merged
2 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

XCM: Allow reclaim of assets dropped from holding paritytech/polkadot
1 participant
@gavofyork