-
Notifications
You must be signed in to change notification settings - Fork 98
feat: XCM exchange asset #640
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
Conversation
…HydraDX-node into hack/xcm-exchange-asset
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #640 +/- ##
==========================================
+ Coverage 64.81% 65.01% +0.19%
==========================================
Files 135 137 +2
Lines 9800 9898 +98
==========================================
+ Hits 6352 6435 +83
- Misses 3448 3463 +15
☔ View full report in Codecov by Sentry. |
… for now. First we test the feature in basilisk
…y out the feature on basilisk.
enthusiastmartin
left a comment
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.
looks good to me. just some minor suggestions.
Co-authored-by: Martin Hloska <[email protected]>
Co-authored-by: Martin Hloska <[email protected]>
|
lgtm. although , one question : how this is integrated into runtime ? i see no changes in the runtime xcm config but there are already integration tests. |
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.
seems like we don't need to redefine the parameter, no?
It's not yet. Going to basilisk first (see galacticcouncil/Basilisk-node#639). Integration will look very similar. |
|
lgtm. altough , one question : how this is integrated into runtime ? i see no changes in the runtime xcm config
not sure what you mean. but assetexchange in xcm config is () in the master branch. i thought this was the one taking care of it. |
|
This is the implementation, but we want to test on Basilisk first, so it doesn't actually add it to the runtime, yet. I Imagine it will be a two step process with another PR. Same pattern as XCM rate limiter. |
this was about the particular review comments I left about implementation details, don't worry about it. |
ah right. makes sense. but still wondering how the integration tests work as it is not integrated. |
Description
Implementing the handling of ExchanceAsset xcm instruction
Adding custom XcmExecuteFilter to allow Transfer-And-Swap functionality and filter out non-desired xcm messages.
NOTE: The filter and exchange asset won't be configured for now in hydra runtime. First we want to enable this in basilisk to test it out.
Leftover TODOs: