XCM to v2 proposal
As XCM v1 has been completely removed from Kusama Network, and the safe version should be XCM v2, this proposal aims to forceDefaultXcmVersion to 2.
-
The original call data:
0x63050102000000 -
Screenshot: here
However, we are submitting this on Whitelisted Caller track, so the proposal is wrapped on this particular track, along with the Fellowship proposal to whitelist the hash for successful execution:
-
Preimage for the Fellowship referendum: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2000882c00c51a0b602437445d110cabd1ff002d3700e393a01d62ca98d24973505303a752
-
Fellowship referendum to whitelist the call: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x17002b0f0253b6e253ec0fb2624e9743727e15fa01ea184cdd55e8cada91c20e4efa06815322000000010a000000
-
Preimage for the public referendum: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x2000242c0363050102000000
-
Public referendum to dispatch the call: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.polkadot.io#/extrinsics/decode/0x15002b0d02f5570f94b7fdf7487d1f9876af264d81c8bcbf9a06a63bb3a0742cdb8942187e09000000010a000000
Make sure to revire and please vote at your convenience!
Comments (2)
Proposal Passed
3
of 3Summary
0%
Aye
0%
Nay
Aye (273)0.0 DOT
Support0.0 DOT
Nay (13)0.0 DOT
Voting Data
Approval%
Support%
Threshold0.00%
Threshold0.00%
Comments (2)
In the future, shouldn't the default be changed before the functionality is removed?
(but yes of course I support this.)
ChaosDAO, in efforts to bolster transparency within the community, has offered the below rationale for its decision to Aye Referendum 167.
This whitelisted referendum is to force XCMv2 to be the default data messaging system for the Kusama Network. These two versions were working side by side with v1 as the default, but since it has been deemed safe by audits and multiple functioning use cases - v2 was recommended by the fellowship to now be the default.
We as a DAO agreed unanimously and are looking forward to seeing v3 become the default in due time!
100% Aye
In the future, shouldn't the default be changed before the functionality is removed?
(but yes of course I support this.)
ChaosDAO, in efforts to bolster transparency within the community, has offered the below rationale for its decision to Aye Referendum 167.
This whitelisted referendum is to force XCMv2 to be the default data messaging system for the Kusama Network. These two versions were working side by side with v1 as the default, but since it has been deemed safe by audits and multiple functioning use cases - v2 was recommended by the fellowship to now be the default.
We as a DAO agreed unanimously and are looking forward to seeing v3 become the default in due time!
100% Aye