This is a referendum to upgrade Kusama to <a href="https://github.com/polkadot-fellows/runtimes/releases/tag/v1.4.0">v1.4</a>. See the&nbsp;<a href="https://github.com/polkadot-fellows/runtimes/releases/tag/v1.4.0">fellowship release notes</a>&nbsp;for more details.
Of special note is enabling nomination pools participation in governance, removing funding to Kappa Sigma Mu Society, allowing burn parameters to be set via OpenGov, lowering parachains and data deposits on Kusama, adding all assets in pool with native xcm payment on Asset Hub, delegate stake pools in Kusama and improving bridges usage.
Enactment is set for block <a href="https://kusama.subscan.io/block/27155056">27155056</a> around 8am UTC on 19th Feb
Edited to fix an error and to add the enactment date.

[Whitelisted Caller] Upgrade Kusama to v1.4.0

dispatch_whitelisted_call_with_preimage

This proposal assigns a core to the People Chain directly on the relay effective immediately.
As it stands the People Chain will only start making blocks in 12 days at its next assignment, as the previous assignment came before the core was ready on the relay chain.

Assign core for People Chain directly on relay

This Referendum registers the People Chain and gives it a core straight away.

To avoid having to wait for two sale boundaries for the People Chain to be given a core, the Coretime Chain is also upgraded to the [Fellowship v1.2.3 release](https://github.com/polkadot-fellows/runtimes/releases/tag/v1.2.3).

This upgrade to the Coretime Chain includes a migration to reserve a core for the people chain without delay. It also cleans up some entries in storage from the old sale.

Register People Chain and upgrade Coretime Chain to v1.2.3

The four accounts on this proposal made extrinsics in the past that lost funds due to bugs in the runtime at that time. The extrinsics were: <a href="https://kusama.subscan.io/extrinsic/21678807-20">1</a>, <a href="https://kusama.subscan.io/extrinsic/21577634-3">2</a>, <a href="https://kusama.subscan.io/extrinsic/21734857-2">3</a> and <a href="https://kusama.subscan.io/extrinsic/21605077-2">4</a>
You can see that each has a <code>polkadotXcm.Attempted</code> event which shows that it failed, however, there should be a <code>polkadotXcm.AssetsTrapped</code> event too. This was due to a bug that the assets were not trapped and therefore lost. This bug was present in the version used in these extrinsics, 1.1.0 of Kusama. The accounts attempted to cross-chain transfer all their funds and didn't have enough to pay for delivery fees, since they were taken from the account itself. This was fixed in version 1.1.2, after changes from <a href="https://github.com/paritytech/polkadot-sdk/pull/3085">PR 3085</a> were included.
Since these funds were lost due to a bug, they should be reimbursed, while extrinsics where assets were trapped (not included in this proposal) can be reclaimed.