- Ethereum and Khala networks are connected by a bridge.
- There is a shortage of liquidity on the Khala network due to high usage.
- A proposal has been made to transfer 500K PHA from one account to another on both Phala and Khala networks.
- This proposal will help to ensure the bridge works properly.
- The transfer will be triggered by a specific code on the blockchain.

[Second round] Move 500K PHA from ChainBridge to SygmaBridge - motion #226

- SubSquare has made an upgrade to Khala and Phala networks.
- SygmaBridge pallets have been enabled on those two networks.
- SygmaBridge will help in transferring assets between parachain and EVM chains.
- A proposal has been created to move 500K PHA from ChainBridge reserve account to SygmaBridge reserve account on both Khala and Phala network.
- The proposal will trigger an extrinsic on blockchain which will force transfer 500K PHA from the source account to dest account.

Move 500K PHA from ChainBridge to Sygma Bridge - motion #221

Khala Runtime Upgrade v1250 - motion #220

- Doyle wants to become a Registrar on Khala network.
- He wants to help more people with efficient on-chain certification.
- Doyle is dedicated to promoting more vaults for better staking rewards.
- He believes Phala will have outstanding growth and success.
- Doyle wants to work with the community to build a brighter future for Phala.

Proposal for nominating Doyle as a Khala Registrar

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

- A person accidentally transferred 8849 Phala from the Phala app dashboard to a KSM address.
- The system created a statemine address linked to this KSM address, and the 8849 Phala are blocked on this Khala address.
- The person is proposing a force transfer of their 8849 Phala so as not to lose them forever and that no one will ever recover.
- The person has provided transaction links to support their request.
- The new Khala address with the 8849 Phala lock can be found at https://khala.subscan.io/account/44757Jrc3YZGPSQSnYU6EQU6xWb8fy55T8tHtpKkeACMjxAU.

Untitled - public proposal #21

- 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

- This proposal wants to make changes to the Phala network to allow for Gemini Tokenomics and access to computing power for the Phat Contract.
- The changes will make the Phala network more similar to the Khala network, which will encourage more usage and growth.
- The proposal includes updates to the Phala network, such as a budget balancer and independent components for computing providers.
- Workers on both Khala and Phala networks will receive equal rewards, and there is no need for workers on Khala to do any upgrade operations.
- The Phala team will supply the computing power for workers on the Phat mainnet, and in Q2, they will develop the necessary components for community workers to provide support.

invalid referendum

Khala Runtime Upgrade v1241 - motion #196

Khala Runtime Upgrade v1230 - motion #195

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.

Democracy Referenda