Note: if you already have opengov-cli installed you'll need to update to get the changes from opengov-cli#34
We'll schedule these to enact first on Kusama, then on Polkadot a week later. Both scheduled times will be morning UTC on a weekday when most engineers are online. Kusama runtime upgrades usually confirm in about 7 days, Polkadot more like 9 or 10 depending on backing. I'm posting them both on 20250210 (a Monday), so Kusama should be scheduled for 9 days and Polkadot 16 days from now (20250219 and 20250226 respectively). Grabbing some block numbers to make this coincide with roughly 8am UTC on these days gives us:
Kusama enactment block: 27155056
Polkadot enactment block: 24899075
https://github.com/polkadot-fellows/runtimes/releases/tag/v1.4.0
Submit the preimage for the Fellowship referendum:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.dwellir.com#/extrinsics/decode/0x2000882c00740edba4531f2695dc8762141c48fa857efaded3f126e67e1d912a80b64e42fb
Open a Fellowship referendum to whitelist the call:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.dwellir.com#/extrinsics/decode/0x17002b0f02b0d94fdc83d6a0d4812da1d774fd1d7d3ffae85b0dacb9fd14a8ce61b17bf64722000000010a000000
Open a public referendum to dispatch the call:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-rpc.dwellir.com#/extrinsics/decode/0x15002b0d0272282a8971a9df79ef27ebebf9a4bff4499df9f7657deaf286dc4b8aa19fcc994001000000705a9e01
We can fork the network with chopsticks and check that the XCMs are sent and that we can upgrade the chains without error.
Submit the preimage for the referendum on localhost:8005 (kusama relay) using the call from opengov-cli
whitelist the call from the fellows origin using the same call output by opengov-cli in the js window:
dispatch the referendum call manually from the whitelistedcaller origin in the js window:
Then go through each chain (available at 800n) with n in [0,5] and compare its system->authorizedUpgrade
hash in state to the hash for each runtime in the fellows release. You should be able to upload the wasm for each chain with the system->applyAuthorizedUpgrade
https://github.com/polkadot-fellows/runtimes/releases/tag/v1.4.0
This will include all system parachains in the upgrade.
Submit the preimage for the Fellowship referendum:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-collectives-rpc.polkadot.io#/extrinsics/decode/0x2b00d41f0004010004082f0000060342c78b76216f88170023491956e1a07d55bf6fa0ac7a90404bdb2fe16599064d4ccaf82c22f1c72f21
Open a Fellowship referendum to whitelist the call:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-collectives-rpc.polkadot.io#/extrinsics/decode/0x3d003e0202623e4656d33843d987d5dfa54e31f7434f8c85fdea3a06916490fae72787459935000000010a000000
Open a public referendum to dispatch the call:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-rpc.dwellir.com#/extrinsics/decode/0x1500160d021e4765ea1528d5f3e3367133191bc501cc5bf4fbacf9b16704dba45aec6f92753f0100000003ee7b01
Batch to submit on Polkadot Collectives Chain:
https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-collectives-rpc.polkadot.io#/extrinsics/decode/0x2804082b00d41f0004010004082f0000060342c78b76216f88170023491956e1a07d55bf6fa0ac7a90404bdb2fe16599064d4ccaf82c22f1c72f213d003e0202623e4656d33843d987d5dfa54e31f7434f8c85fdea3a06916490fae72787459935000000010a000000
We can fork the network with chopsticks and check that the XCMs are sent and that we can upgrade the chains without error.
Submit the preimage for the referendum on localhost:8005 (polkadot relay) using the call from opengov-cli
whitelist the call from the fellows origin using the same call output by opengov-cli in the collectives js window:
You can see the events on the relay whitelisting the call and requesting the preimage.
Upload the public referendum preimage from opengov-cli to the relay chain.
Dispatch the referendum call manually from the whitelistedcaller origin in the relay chain js window:
Then go through each chain (available at 800n) with n in [0,5] and compare its system->authorizedUpgrade
hash in state to the hash for each runtime in the fellows release. You should be able to upload the wasm for each chain with the system->applyAuthorizedUpgrade