-
Notifications
You must be signed in to change notification settings - Fork 77
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
feat: xcm exchange asset #714
Conversation
Crate versions that have been updated:
Runtime version has been increased. |
@@ -210,7 +216,7 @@ impl pallet_xcm::Config for Runtime { | |||
type SendXcmOrigin = EnsureXcmOrigin<RuntimeOrigin, LocalOriginToLocation>; | |||
type XcmRouter = XcmRouter; | |||
type ExecuteXcmOrigin = EnsureXcmOrigin<RuntimeOrigin, LocalOriginToLocation>; | |||
type XcmExecuteFilter = Nothing; | |||
type XcmExecuteFilter = AllowTransferAndSwap<MaxXcmDepth, MaxNumberOfInstructions, RuntimeCall>; |
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.
why is this change necessary? i dont think we are planning to execute xcm messages locally and xcm::execute extrinsic is call filtered anyway currently
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.
We want it in combination with changing the call filter to allow UIs to interact with the chain through pallet_xcm::execute
. This is part of the XCM exchange asset stuff.
Concretely you could imagine our UI swapping tokens on Hydra and then sending them to the destination in one extrinsic/with one XCM.
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.
did you try to exchange something from some sibling parachain using chopstics?
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.
Any problems with this?
Description
We enable AssetExchange xcm message instruction in hydra.
It also means that we needed to change the
XcmFilter
of pallet_xcm fromNothing
toAllowTransferAndSwap
, which is a more permissive in terms of allowed xcm instructions.Related Issue
Motivation and Context
How Has This Been Tested?
Checklist: