-
Notifications
You must be signed in to change notification settings - Fork 20
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
fix!: Patch XCM Executor #526
Conversation
…hed polkadot version
Crate versions that have been updated:
Runtime version has been increased. |
Codecov Report
@@ Coverage Diff @@
## master #526 +/- ##
==========================================
+ Coverage 81.21% 81.24% +0.02%
==========================================
Files 19 20 +1
Lines 1927 1930 +3
==========================================
+ Hits 1565 1568 +3
Misses 362 362
Continue to review full report at Codecov.
|
Task linked: CU-2rgt0pz Patch XCM executor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just minor suggestions.
Co-authored-by: Martin Hloska <martin.hloska@gmail.com>
Use a patched version of Polkadot that fixes the XCM executor to trap assets on failed instructions.
Description
This PR adds an integration test for asset trapping on receiving unknown assets and uses a patched Polkadot version that ensures the asset is trapped (and not burned).
Related Issue
Based on paritytech/polkadot@release-v0.9.17...apopiak:polkadot:apopiak/fix-xcm-executor-atomicity
Motivation and Context
Assets that are not recognized on
BuyExecution
(and thus trigger an error) get burned in the XCMv2 executor.How Has This Been Tested?
Checklist: