Skip to content
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

Migration for pallet_xcm data: Queries, LockedFungibles, and RemoteLockedFungibles #492

Open
2 tasks
bkontur opened this issue Oct 23, 2024 · 0 comments
Open
2 tasks

Comments

@bkontur
Copy link
Contributor

bkontur commented Oct 23, 2024

Description

pallet-xcm stores some operational data that uses Versioned* XCM types. When a new XCM version (XV) is added, XV-2 is deprecated and XV-3 is removed. Without proper migration, this can lead to issues with undecodable storage, as was observed on the XCMv5 branch where XCMv2 was removed. If we inspect Polkadot/Kusama chains, we can still find Versioned*::V2 XCM data, as shown in screenshots at the end.

pallet_xcm includes a MigrateToLatestXcmVersion migration, which has been added to all runtimes. However, we need to bump pallet_xcm to the version that contains the fix from this PR. This update should be deployed to live chains before introducing XCMv5 to the runtimes, as XCMv2 is removed in that version.

Progress

Data examples

image
image
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant