proposalHash

votingPeriod

delay

Khala Runtime Upgrade v1272 - Council motion #284

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

codeHash

checkVersion

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

source

dest

value

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.

[3rd round] Move 2M PHA from ChainBridge to SygmaBridge - motion #228

- 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

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.

Democracy External Proposals