Cancel Referendum 241 (runtime upgrade) due to XCM issue
Due to an issue with Polkadot runtime 1'000'000 (seen after the equivalent runtime upgrade on Kusama), I am proposing this Referendum to cancel Referendum 241 proposing to upgrade Polkadot to it. Details: https://twitter.com/XiliangChen/status/1722546330382565572
Comments (6)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (129)0.0 DOT
Support0.0 DOT
Nay (0)0.0 DOT
Voting Data
Approval%
Support%
Threshold0.00%
Threshold0.00%
Comments (6)
After yesterday’s upgrade of the Kusama relay chain to v1000000, a new issue was reported concerning XCM transfers, resulting in a failed transaction. Specifically, the new runtime appends a SetTopic instruction with every XCM program. XCM v2 does not support this instruction. Since this instruction does not exist on v2, any destination that the Kusama relay chain thinks uses v2 (even if it actually uses v3) will issue an error, resulting in a failed transaction. Parachains can fix this issue by setting their XCM version to v3.
This proposal aims to cancel and halt Referendum 241 for the upcoming runtime upgrade on Polkadot until the fix is available.
Hi Bill, team Pioneer will support you in any case.
After yesterday’s upgrade of the Kusama relay chain to v1000000, a new issue was reported concerning XCM transfers, resulting in a failed transaction. Specifically, the new runtime appends a SetTopic instruction with every XCM program. XCM v2 does not support this instruction. Since this instruction does not exist on v2, any destination that the Kusama relay chain thinks uses v2 (even if it actually uses v3) will issue an error, resulting in a failed transaction. Parachains can fix this issue by setting their XCM version to v3.
This proposal aims to cancel and halt Referendum 241 for the upcoming runtime upgrade on Polkadot until the fix is available.
Hi Bill, team Pioneer will support you in any case.