Whitelisting Kusama Runtime Upgrade 2.3 through the Polkadot<->Kusama bridge: https://kusama.subsquare.io/referenda/651

Thanks to Karol for testing it!

The XCM Call from Collectives looks like this. It has to make a stopover on Polkadot Hub, since Collectives only exposes Relay and Siblings as XCM routable destinations. From Polkadot Hub we can then jump to Kusama Hub via a InitiateTransfer with an attached remoteXcm:

{
    "dest": {
      "V5": { "parents": 1, "interior": { "X1": [{ "Parachain": 1000 }] } }
    },
    "message": {
      "V5": [
        { "UnpaidExecution": { "weightLimit": "Unlimited", "checkOrigin": null } },
    "dest": {
      "V5": { "parents": 1, "interior": { "X1": [{ "Parachain": 1000 }] } }
    },
    "message": {
      "V5": [
        { "UnpaidExecution": { "weightLimit": "Unlimited", "checkOrigin": null } },
        {
          "InitiateTransfer": {
            "destination": {
              "parents": 2,
              "interior": { "X2": [{ "GlobalConsensus": "Kusama" }, { "Parachain": 1000 }] }
            },
            "remoteFees": null,
            "preserveOrigin": true,
            "assets": [],
            "remoteXcm": [
              {
                "Transact": {
                  "originKind": "Xcm",
                  "fallbackMaxWeight": null,
                  "call": { "encoded": "0x5e00<CALL_HASH>" }
                }
              },
              { "ExpectTransactStatus": "Success" }
            ]
          }
        }
      ]
    }
  }

The <CALL_HASH> is the hash to be whitelisted on Kusama Hub: 0x3ad2bf340fd1fe8c8434d8ac346d6afc77e7bb2d1c76340d47a0c2983225e64b.