XCM to v2 proposal

inWhitelisted Caller
4 years ago
Executed

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.

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:

Make sure to revire and please vote at your convenience!

Comments (2)

4 years ago

In the future, shouldn't the default be changed before the functionality is removed?

(but yes of course I support this.)

profile
ChaosDAO_Referendum_Commission
4 years ago

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

Polkassembly is now a read-only archive. Commenting is disabled.

Proposal Passed

    Polkassembly - Referendum #167