You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Description
pallet-xcm
stores some operational data that usesVersioned*
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 findVersioned*::V2
XCM data, as shown in screenshots at the end.pallet_xcm
includes aMigrateToLatestXcmVersion
migration, which has been added to all runtimes. However, we need to bumppallet_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
pallet_xcm
version when Fix migrations for pallet-xcm paritytech/polkadot-sdk#6148 releasedData examples
The text was updated successfully, but these errors were encountered: