Invalid proposal

- Phala Network proposes retiring Khala chain by January 10, 2025.
- Khala will be replaced due to Intel discontinuing SGX-IAS support in April 2025.
- All Khala assets will migrate to Ethereum, which supports Intel TDX and Nvidia GPUs.
- The transition aims to simplify the ecosystem and use advanced technology.
- A TEE marketplace will be launched on Ethereum for TDX cloud services.
- Phala World NFTs will be reclaimed, and holders will be refunded.
- The proposal focuses on future-proofing Phala Network for decentralized cloud computing.

Proposal: Sunsetting Khala Chain and Consolidating Phala Network on Polkadot and Ethereum ecosystem

- 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

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

Phala Network is upgrading its 'Delegate to Earn' mechanism on the Khala network. This will introduce a Delegation NFT that will act as a certificate for users' delegations, which can be traded on a secondary marketplace for immediate liquidity. Delegator rewards will be automatically compounded, and a new feature called Vault will be introduced, which will allow users to pass the management of delegation to the Vault operator. Vault operators will manage delegations to individual StakePools on behalf of their delegators, which will further enhance delegation efficiency and lower the barrier to entry. The upgrade process will take up to five days, and computing rewards will be delayed for eight days. The Phala App will also be updated to deal with this on-chain upgrade.

Proposal: StakePool V2 and Vault Launch

- A proposal has been made for the community referendum.
- The proposal suggests opening Khala transfer and launching Khala-Ethereum bridge for $PHA transfer.
- If the community votes "AYE", two fast-track proposals will be implemented separately.
- The first motion will open Khala transfer on Day 0 using runtime_update.
- The second motion will launch Khala-Ethereum bridge on Day +5 using runtime_update.
- To participate in the democratic structures, one can read the guidelines provided on the given link.

Motion #6: Open Khala Transfer and Bridge to Ethereum 

Khala Network Runtime v1271 Updates:
- Fixes a bug in vault force withdraw.
- Removes gas fee for syncing GK messages.
- More details are available on the [release page](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.27-1).

Khala Runtime Upgrade v1271 - motion #281

- This is a proposal to update something called the Tokenomic Budget Balancer used by Phala & Khala Network.
- There are two things that need to be done to update it: (1) point to the new budget balancer, and (2) transfer the gas fee from the old balancer to the new one.
- The Tokenomic Budget Balancer was upgraded to follow the upstream upgrade.
- The old API was deprecated, so a new one called Subscan API is being used for block information queries.
- The maximum value of the budget has been limited and you can find the source code at a website called Github.

Retry: Upgrade Tokenomic Balancer Phat Contract - motion #266

- Phala & Khala Network is updating their Tokenomic Budget Balancer.
- The update includes pointing permission to the upgraded budget balancer and force transferring the gas fee from the old balancer's contract held account to the new one.
- The Tokenomic Budget Balancer was upgraded to follow the upstream upgrade.
- The Subscan API is now used for block information queries due to Subsquid deprecating the old API.
- The maximum value of the budget has been limited.

Upgrade Tokenomic Balancer Phat Contract - motion #265

- Khala Network Runtime v1270 is getting an upgrade.
- The upgrade includes new features like DCAP support and HashedDescription XCM location converter.
- Some bugs have been fixed, like preventing crashes and allowing add in set_reimbursements.
- The migration account has been switched.
- You can find more information about the upgrade on the release page.

Khala Runtime Upgrade v1270 - motion #264

- 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.

Initiate parachain slot swap with GM chain - motion #263

Khala Runtime Upgrade v1263 - motion #261

Redo Motion 257 Khala Runtime Upgrade v1262 - motion #258

Khala Runtime Upgrade v1262 - motion #257

Move ChainBridge liquidity to Sygma - motion #251

Khala Runtime Upgrade v1261 - motion #248

- Khala Network Runtime is getting an upgrade
- The upgrade will improve stability and performance
- Bugs in PhalaPhatContracts pallet will be fixed
- A new feature called RPC pha_getStorageChangesWithRoot will be added
- For more information, check the release page on GitHub.

Khala Runtime Upgrade v1260 - motion #247

Khala Runtime Upgrade v1256 - motion #246

Khala Runtime Upgrade v1255 - motion #245

Khala Runtime Upgrade v1254 - motion #244

Khala Runtime Upgrade v1253 - motion #240

Khala Runtime Upgrade v1252 - motion #239

- The Khala network is running out of liquidity due to a large amount of cross-chain transfers.
- A proposal has been made to move 4 million PHA from ChainBridge reserve accounts on Khala, Phala, and Ethereum networks.
- The proposal involves transferring the PHA from one account to another using blockchain technology.
- This transfer will help ensure that the bridge between the networks continues to function properly.
- The proposal will be executed by triggering an extrinsic on the blockchain.

[4th round] Move 4M PHA from ChainBridge to SygmaBridge - motion #233

Khala Runtime Upgrade v1251 - motion #231

- Ethereum and Khala are two different networks that allow people to send and receive money.
- Recently, a lot of money was sent from Ethereum to Khala, which caused a problem because there wasn't enough money in Khala.
- To fix this problem, a proposal was made to move 2 million PHA from a reserve account on both Khala and Phala networks to a different account called SygmaBridge.
- This proposal will make sure that there is enough money in Khala and Phala networks so that people can keep sending and receiving money.
- This transfer will happen automatically through something called a blockchain, which is like a computer program that keeps track of all the money transfers.

Democracy Referenda