This proposal aims to upgrade Kusama to the lastest release ([1.2.2](https://github.com/polkadot-fellows/runtimes/releases/tag/v1.2.2)): aiming to fix some issues encountered with core sales and bridges. 

When Kusama upgraded to the [1.2.0 runtime](https://kusama.polkassembly.io/referenda/373) it migrated itself to Coretime. This migration is done by iterating the current state of parachains and sending this information to the Coretime chain using multiple Xcm messages. One of these Xcm messages is setting up the leases to match the leases of the old auction model (this should ensure that parachains that won leases using the old auction model still get Coretime until the end of their lease). However, this Xcm message failed to execute because of a Weight mismatch (the third `message.Processed` event [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-coretime-rpc.polkadot.io#/explorer/query/0x006a92a7615a939866e74f90889b9b12d1268edc67a473359a66e50c2ba012c4%5D(https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fkusama-coretime-rpc.polkadot.io%23/explorer/query/0x006a92a7615a939866e74f90889b9b12d1268edc67a473359a66e50c2ba012c4)) showing success false). Basically this means that the message announced would use less weight than what it would actually use and this made the Xcm message fail. This is a security measurement to ensure that Xcm messages cannot stall a chain.

For this reason, a runtime upgrade is proposed that reruns the Xcm message, but also includes a [fix](https://github.com/paritytech/polkadot-sdk/pull/4089) that ensures that every parachain that had a lease before core sales start can renew their core. The side effect of this runtime upgrade is that the sales state is reset, meaning that the sales start 7 days after this runtime upgrade is applied.

**Changes on Kusama BridgeHub 1.2.2 upgrade**

The Polkadot-GRANDPA-light-client running on Kusama BH doesn’t correctly handle a corner case involving validator set changes following validator slashing. As a result of the bug, the GRANDPA light-client can fail to recognise the other side's validator set change and thus start refusing to accept subsequent validator set changes as well. More details can be found on [this forum post](https://forum.polkadot.network/t/polkadot-kusama-bridge/2971/45). 

We have encountered this bug on the Polkadot BH, resulting in Kusama->Polkadot traffic being stuck. This upgrade fixes the bug for Kusama BH so that it is protected from encountering the same issue.

Please note this proposal is submitted on Whitelisted Caller track - a parallel submission is up for vote on Fellowship to whitelist this proposal.


See [`Pallet::dispatch_whitelisted_call_with_preimage`].

- **Problem Statement:** Upgrading Kusama to version 1.2.2 to address issues with core sales, bridges, and Xcm message failures.
- **Significance:** Ensuring that parachains can renew their core leases and fixing bugs in the GRANDPA light-client to prevent traffic disruptions.
- **Proposed Solution:** Implementing a runtime upgrade that includes fixes for Xcm message failures and GRANDPA light-client bugs.
- **Expected Outcomes:** Improved functionality, security, and stability for Kusama through the proposed upgrades.

#380 Kusama Runtime Upgrade to 1.2.2

No Active Proposals