Girazoki support both pre and post 0.9.16 anchoring logics for native token #1232
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.
What does it do?
It adds support for mapping both pre and post 0.9.16 anchoring changes to the same token (in this case, the native token).
The reanchoring logic change will stop from marking us see our token as
To make it see it as
This PR does yet not add the possibility of transferring the local token for Moonriver and Moonbeam. I wanted this review to be easier, so I will make a follow up PR enabling transfer of the local asset in XCM
What important points reviewers should know?
Is there something left for follow-up PRs?
Adding the possibility of transferring the local token for Moonriver and Moonbeam
What alternative implementations were considered?
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
What value does it bring to the blockchain users?