Please vote NAY to this. The swap is no longer needed. Khala has won the slot.
This motion will trigger a registry.swap(2004, 2123) call by Khala's sovereign account on Kusama. It intends to swap the parachain lease with GM chain (id: 2123).
The raw call: 0x4603d40700004b080000
Khala's last lease period (35) will end very soon. Though Khala is bidding the last auction for the next lease periods, it only has 50% chance to win. If Khala lose, the tokenomic will pause and it will affect compute providers seriously. GM chain may be willing to help us. So this motion try to send the swap request to GM chain. Once the request is sent. We will need GM chain's acceptance to actually trigger the swap.
I suggest to initiate the swap request from Khala side, and then wait for the outcome of the current auction. If Khala fails, then GM chain can accept the swap. Otherwise the swap can be cancelled by Khala.
It's better to avoid swapping before the auction ends, because it may trigger some edge case exception on Kusama. Otherwise, if Khala wins the auction, it will end up win a "redundant" slot, which is likely to lock the bid on Kusama. We have to engage Kusama governance to sort it out.
The XCM and swap operation is tested with chopsticks xcm simulation.
Khala needs to swap the parachain lease with GM chain to avoid tokenomic pause.
Khala is bidding for the next lease periods but only has a 50% chance to win.
If Khala loses the auction, GM chain may accept the swap to help Khala.
It's better to wait for the auction outcome before swapping to avoid edge case exceptions.
The swap operation has been tested with chopsticks xcm simulation.