[Fix 224] Expand invulnerables set on Asset-Hub Kusama

Hey everyone,

I’m proposing this referendum today, it aims to fix the only XCM instruction that failed to execute from the successful outcome of referendum 224.

Brief Summary
The previous referenda 224 was all about decentralizing the collator set on both system chains – Bridge-hub Kusama and Asset-hub Kusama with a call tabled with five XCM instructions. From these five instructions, four were successfully executed and only the call related to the expansion of the invulnerables set on Asset-Hub Kusama failed to execute. The reason for the failed instruction was due to the fact of missing onchain session keys from one of the collators by the time the referenda moved into the execution phase.

At the time, knowing that the runtime v1000000 would bring new extrinsics to better handle such cases and also facilitate add/remove invulnerables, was than discussed by all parties involved that would make sense to wait until the current runtime was active on chain to propose a new referenda that would fix the previous XCM instruction, and such referenda could also be used as an opportunity to try out the new extrinsic – collatorSelection.addInvulnerable.

As a result I’m proposing this referendum asking the community to vote on it.

What to expect from this referendum
With the successful outcome we could expect the following:

• 6 new invulnerables, changing the total number from 2 to 8 (Note: the following list of collators were the ones already previously selected on referenda 224)
  TurboFlakes: H1tAQMm3eizGcmpAhL9aA9gR844kZpQfkU7pkmMiLx9jSzE
  LuckyFriday: HPUEzi4v3YJmhBfSbcGEFFiNKPAGVnGkfDiUzBNTR7j1CxT
  ParaNodes: J11Rp4mjz3vRb2DL51HqRGRjhuEQRyXgtuFskebXb8zMZ9s
  Polkadotters: EPGHRDFaBbQz4uF8DgnuScxYp4rvvtpL5MTed7VvGprNQmm
  Stake.Plus: E5G5qLNBF7nwhemokqNrNwUCQ7oHrLsBVjSc7XhTdRq8672
  IcebergNodes: Eicei1RVHvqHBPJAY2fZpLy2KtCMjY7Kwjo3svjmGLH7FmT

• 3 out of the 9 active permissionless collators will automatically switch to invulnerables with the remaining 6 keeping their active slot.

Thanks for your vote and time
paulo // apps.turboflakes.io