-
Notifications
You must be signed in to change notification settings - Fork 674
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
Fix migrations for pallet-xcm #6148
base: master
Are you sure you want to change the base?
Conversation
# Conflicts: # polkadot/runtime/westend/src/lib.rs
…RemoteLockedFungibles`
bot fmt |
@bkontur https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/7624303 was started for your command Comment |
@bkontur Command |
/cmd prdoc |
Co-authored-by: Francisco Aguirre <[email protected]>
Relates to: #4826
Relates to: #3214
Description
pallet-xcm
stores some operational data that usesVersioned*
XCM types. When we add a new XCM version (XV), we deprecate XV-2 and remove XV-3. Without proper migration, this can lead to issues with undecodable storage, as was identified on the XCMv5 branch where XCMv2 was removed.This PR extends the existing
MigrateToLatestXcmVersion
to include migration for theQueries
,LockedFungibles
, andRemoteLockedFungibles
storage types. Additionally, more checks were added totry_state
for these types.TODO
polkadot-fellows
Migration forpallet_xcm
data:Queries
,LockedFungibles
, andRemoteLockedFungibles
polkadot-fellows/runtimes#492MigrateToLatestXcmVersion
for westendQueries
V2
was removed fromVersioned*
stuff, but we have a live data with V2 e.g. Queries - e.g. Kusama or Polkadot relay chainsRemoteLockedFungibles
LockedFungibles
Follow-ups
pallet_xcm
internal data changes proposal #6188