mGirazoki controlled xtokens fee#2
Merged
tgmichel merged 17 commits intomoonbeam-polkadot-v0.9.13from Dec 2, 2021
Merged
Conversation
…_multiasset_with_Fee
…girazoki-controlled-xtokens-fee
girazoki
changed the base branch from
moonbeam-polkadot-v0.9.12
to
moonbeam-polkadot-v0.9.13
girazoki
pushed a commit
that referenced
this pull request
Dec 17, 2021
mGirazoki controlled xtokens fee
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This just adds two new extrinsics to be able to provide the fee as a separate argument to the asset to be transferred. For now I assumed both the fee and asset are of the same kind (i.e., you need to use the same asset (but potentially a different amount) to pay for the fee)