This is a proposal to upgrade Kusama to the Relay Chain 9381 and System Parachains 9382 releases. As with the previous (cancelled) referenda, this includes the upgrade to XCM v3. This proposal is a bit dense, so will break it down. It's a `force_batch`, meaning that even if one of the calls fails, it will still execute the later ones.

The first two calls are `xcm.send` extrinsics that send `authorize_upgrade` messages to Statemine and the BridgeHub.

The next two schedule calls on the Relay Chain to set the XCM version it uses to communicate with Statemine and the BridgeHub to `3`. They are scheduled for 600 blocks (1 hour) later because that is the upgrade delay imposed on parachains. So it should update to 3 at about the same time that the parachains upgrade. We've done a lot of testing on local networks, but please be careful around this time with calls that handle funds (teleport, reserve asset transfers).

The last call is the Relay Chain runtime upgrade, wrapped in its `with_weight` dress.

Finally, I configured this to enact, if passed, at block 17,335,450. If I calculated right, this should be about 11:00 UTC on Tuesday 04 April. This should be a _convenient enough_ time for most time zones.

Releases where I took the runtime Wasm files:

- [Relay Chain](https://github.com/paritytech/polkadot/releases/tag/v0.9.38-rc12)
- [Parachains](https://github.com/paritytech/cumulus/releases/tag/parachains-v9382)

:

1. Call xcm.send for authorizing upgrade on Statemine and BridgeHub
2. Schedule calls on Relay Chain to set XCM version to 3
3. Run Relay Chain runtime upgrade
4. Upgrade to be enacted at 11 UTC on Tuesday 04 April

#134 Kusama Runtime Upgrade 938*

No Active Proposals