fix: update foreign asset location construction #377
Merged
Conversation
This file contains 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
add foreign asset transfer to examples for polkadot and kusama
…tance junction added adds examples for kusama and polkadot foreign asset tx construction
bee344
reviewed
Mar 1, 2024
examples/kusama/assetHub/foreignAssetTransfers/local/assetHubForeignAssetsTransfer.ts
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR fixes a bug where foreign asset locations had their
PalletInstanceprepended to them.This is incorrect behavior which should be removed.
Changes
constructForeignAssetMultilocationfunction from the APIresolveMultiLocationto require the correct xcm version for theGlobalConsensustypecloses: #376