Accept HRMP channel from Picasso - motion #217

1. This is a proposal to fix some mistakes that were made before.
2. They want to send a message to another network called Picasso Network.
3. They want to register something called PICA on Khala.
4. They have enough money to do this.
5. They have some specific information about PICA that they need to use.

Open Khala -> Picasso Network HRMP & Register PICA on Khala (4) - motion #215

Khala Runtime Upgrade v1247 - motion #213

Here is a summary of the SubSquare post:

- This is a retry of a previous motion that didn't work because there wasn't enough PHA or votes.
- The motion will trigger a message on Kusama to request a connection with Picasso Network and register PICA on Khala.
- A specific call will be made with a code that includes recipient, proposed max capacity, and proposed max message size.
- Phala's account already has enough deposit to open the channels.
- The PICA registry information includes an ID, path, symbol, decimal, and execution price.

Open Khala -> Picasso Network HRMP & Register PICA on Khala (3) - motion #212

Khala Runtime Upgrade v1246 - motion #210

Here's a summary of the post content:

- The post talks about a motion that is being retried.
- The motion is about opening a HRMP request to Picasso Network and registering PICA on Khala.
- A transact message will be sent on Kusama to initiate the HRMP request.
- The post provides a code that will be used to perform the transact on Kusama.
- The post also provides information about the PICA registry.

Open Khala -> Picasso Network HRMP & Register PICA on Khala (2) - motion #209

Khala Runtime Upgrade v1245 - motion #208

- A proposal was made to allow HRMP channel to InvArch Tinkernet.
- The proposal failed multiple times due to technical problems or not enough votes.
- The opposition party did not give a clear reason for their disagreement.
- A new motion has been proposed to bring the proposal back to democracy and attract more votes.
- The motion will trigger two Transact messages on Kusama to accept and send the HRMP request from InvArch Tinkernet.

Accept & Open HRMP channel with InvArch Tinkernet (4) - motion #206

- Two motions were not executed correctly due to a mistake.
- This motion is trying to fix the mistake and execute one of the motions again.
- The motion will trigger two Transact messages on Kusama to accept and send a request.
- Khala's account already has enough deposit to open the channels.
- People should vote Nay on the wrong motion and vote on this proposal instead.

Accept & Open HRMP channel with InvArch Tinkernet (3) - motion #205

- Phala Network is a blockchain platform that rewards workers for computing tasks.
- The platform uses a token called PHA to pay for these rewards.
- Recently, the Phala team moved some PHA rewards from an Ethereum subsidy pool to a Khala subsidy pool.
- This motion proposes moving all the remaining PHA rewards from the Ethereum subsidy pool to the Phala subsidy pool.
- In the future, funds will be periodically transferred between the two subsidy pools to ensure there are enough tokens to pay for rewards.

Adjust bridge reservation for the 308.2M PHA compute reward unlock - motion #197

Khala Runtime Upgrade v1241 - motion #196

1. There are two messages that will be sent on Kusama to accept and send a request from InvArch Tinkernet.
2. The first message is a call to hrmp.hrmpAcceptOpenChannel with the sender being 2,125.
3. The second message is a call to hrmp.hrmpInitOpenChannel with the recipient being 2,125, proposedMaxCapacity being 1,000, and proposedMaxMessageSize being 102,400.
4. Khala's sovereign account already has enough deposit to open the channels.
5. These messages are important for communication between different networks.

Accept & Open HRMP channel with InvArch Tinkernet - motion #194

Khala Runtime Upgrade v1230 - motion #195

- A motion is being retried because a newer motion overrode it before.
- The original proposal is to accelerate the voting process.
- The technical committee will fast track the proposal if it passes.
- The voting period will still be 7 days.
- The motion is being discussed on a website called Khala.

Accelerate proposal #20: launch gemeni tokenomic on Phala (2nd try) - motion #191

SubSquare had a problem with their ChainBridge migration issue on ZLK after they upgraded to XCM v3. They made a proposal to fix it, which contained 6 calls. The first two calls set ZLK to a temporary location and then back to its real location, which triggered ZLK resource id to update to the proper value automatically. The next two calls force burned and minted `196247848001219224432700` units of ZLK from old and new reserve accounts. The last two calls force burned and minted `2026420000000000000000` units of ZLK to external and temporary accounts. There were 5 transactions that had their ZLK locked in the temporary account, and the external account will bridge ZLK to user accounts on Moonriver.

Fix ChainBridge migration for ZLK (2nd try) - motion #190

Khala Runtime Upgrade v1210 - motion #187

Swap Khala parachain slot with parachain 2264 - motion #186

- There is a proposal to redo some previous motions that were either not voted on in time or had issues with their execution.
- The proposal involves sending a message on Kusama to accept and send a request from Litmus Network.
- The message will be sent using a specific code that includes information about the sender, recipient, and proposed maximum capacity and message size.
- Khala's account already has enough money to open the channels.
- One of the previous motions failed because it should have been an external referendum instead of a simple motion.

Accept & Open HRMP channel with Litmus (5th try, sadly) - motion #180

Khala Runtime Upgrade v1210 - motion #181

- There is a proposal to redo some previous motions in Khala Subsquare.
- The motions were not successful due to various reasons.
- The new motion will trigger a message on Kusama to accept and send a request from Litmus Network.
- The message will be sent using a specific code that includes information about the sender, recipient, and proposed capacity and message size.
- Khala's account has enough deposit to open the channels.

Accept & Open HRMP channel with Litmus (4th try) - motion #178

- There is a proposal to redo two previous motions, Motion 176 and Motion 174.
- The proposal involves sending a message on Kusama to accept and send a request from Litmus Network.
- The message will be sent on Polkadot using a specific code that includes information about the sender and recipient.
- The purpose of the message is to open channels between Khala and Litmus Network.
- Khala already has enough deposit to open the channels.

Accept & Open HRMP channel with Litmus (3rd try) - motion #177

- The compute reward subsidy pool has only 7M left.
- They want to unlock 155M PHA and move it as the Khala reward.
- They will add 155M to the locked account on both Khala and Phala.
- Then they will move the locked balance on Ethereum to Khala via bridge transfer.
- They will mint 155M PHA on a temporary account on Khala and transfer it to the bridge reservation account.

Tech. Comm. Proposals