-
Notifications
You must be signed in to change notification settings - Fork 295
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
Feature request: Add asset-registry
migration for XCMv4 multilocations
#1002
Comments
There is no reason to migrate to v4, which is exactly the same as v3 other than version bump and rename. Best to wait for V5 and migrate to it instead. |
To interact through the |
the only thing changed is version number and otherwise 100% compatible |
Thanks for the double-checking! |
Closing due to the isometry between V3 and V4 xcm locations. Thanks for your answers @xlc! |
When this repository started supporting XCMv3 as part of the update to Polkadot v0.9.38 in #886, the storage version of the asset registry was bumped and a migration was added to migrate v2 locations to v3.
I was wondering whether there are any plans to do the same for XCMv4 which was introduced in Polkadot SDK v1.7.0.
The text was updated successfully, but these errors were encountered: