- A plan to move PHA tokens from Khala to Phala and Ethereum.
- Step 1: Create new PHA tokens to reach a total of 1 billion.
- Step 2: Move PHA tokens from Khala wallets to Phala wallets.
  - Some tokens go to the Treasury.
  - Some tokens go to XCM holdings.
  - Some tokens go to Phala Mining Subsidy.
  - Some tokens go to a special wallet for moving to Ethereum.
- Next step: Send PHA tokens from the special wallet to Ethereum to prepare for the token change.

Khala PHA migration - Council motion #106

proposalHash

votingPeriod

delay

Phala Runtime Upgrade v1272 - Council motion #105

Phala Network Runtime v1271 Updates:

- Fixed a bug where vault force withdraws could burn stake pool shares.
- Removed the gas fee requirement for syncing GK messages.
- For more details, visit the [release page](https://github.com/Phala-Network/khala-parachain/releases/tag/v0.1.27-1).

codeHash

checkVersion

Phala Runtime Upgrade v1271 - motion #104

Close HRMP channels to Parallel - motion #103

Phala Network is moving 47.25M PHA from the Phala compute reward pool to the Khala compute reward pool. This is to balance the unlocked rewards between Phala and Khala. 

Gemini was launched on 8/4/2022 and since then, Phala's team has moved 381.8M PHA rewards from the locked compute reward subsidy reservation on Ethereum to the Khala subsidy pool in two separate transactions. 

The mining rewards on Khala have been issued to the workers, so the reward budget for the next 2 halving periods will be calculated based on the mining rewards on Khala now. 

Phala and Khala share the same compute reward schedule and subsidy pool after the Gemini Update. 

The force transfer target account is a 2-of-3 multisig wallet owned by the Phala team.

Move 47.25M PHA mining subsidy from Phala to Khala - motion #101

- This is a proposal to update something called the Tokenomic Budget Balancer used by Phala & Khala Network.
- It has two parts: (1) point to the new budget balancer, and (2) transfer the gas fee from the old one to the new one.
- The budget balancer was upgraded to follow a new upgrade, and the maximum value of the budget has been limited.
- The source code for the upgrade is available at a website called GitHub.
- This is a resubmission of a previous proposal because of a mistake in the code.

Retry: Upgrade Tokenomic Balancer Phat Contract - motion #98

- Phala & Khala Network are updating their Tokenomic Budget Balancer.
- The update includes pointing permission to the upgraded budget balancer and force transferring gas fees from the old contract to the new one.
- The upgrade was necessary because the old API was deprecated and the Subscan API is now used for block information queries.
- The maximum value of the budget has been limited.
- The source code is available at a GitHub link.

Upgrade Tokenomic Balancer Phat Contract - motion #97

- This is a resubmission of a previous motion (#94) that didn't get executed quickly enough.
- They want to submit the same proposal again to get a chance to be fast-tracked.
- They changed the preimage to avoid a "duplicated proposal" problem.
- The proposal is about using `ParachainSystem.authorizeUpgrade` in a `Utility.batch` call.
- For more information on the original proposal, please refer to motion #94.

Accelerate motion 94 - motion #96

Phala Network has made some updates to their system, which include:
- Support for DCAP by jasl
- Correct DCAP constants by jasl
- Prevention of crashes if there are no advisoryIDs by nanometerzhu
- Addition of HashedDescription XCM location converter and removal of TinkernetMultisig configs by arrudagates
- Allowing add in set_reimbursements and switching migration account by h4x3rotab

For more information, please visit the release page on GitHub.

Phala Runtime Upgrade v1270 - motion #94

Phala Runtime Upgrade v1263 - motion #92

Phala Runtime Upgrade v1262 - motion #90

Re-trigger preimage referenda #55 - motion #88

source

dest

value

Move ChainBridge liquidity to Sygma - motion #86

Phala Runtime Upgrade v1261 - motion #84

- Phala Network is getting an upgrade called Phala Network Runtime v1260.
- The upgrade will make the network faster and more stable.
- There was a bug in the old version that made it hard for workers to register, but that will be fixed in the new version.
- There will also be a new feature called RPC pha_getStorageChangesWithRoot that will help with data verification.
- You can find more information about the upgrade on the release page.

Phala Runtime Upgrade v1260 - motion #83

Phala Runtime Upgrade v1256 - motion #82

Phala Runtime Upgrade v1255 - motion #81

Phala Runtime Upgrade v1254 - motion #80

Phala Runtime Upgrade v1253 - motion #79

Phala Runtime Upgrade v1252 - motion #78

- SubSquare proposed something before, but nobody voted for it.
- They want to propose it again and make sure people vote this time.
- They want to send a message to Polkadot to open a request to Polkadex Network and receive a request from AssetHub.
- They will use some messages to do this.
- Phala's account already has enough money to do this.

Open HRMP with Polkadex & AssetHub (2nd try) - motion #75

Open HRMP with Polkadex & AssetHub - motion #74

- There is a network called Khala that needs more money to keep working properly.
- They want to move 4 million PHA coins from one account to another account on different networks.
- This will help make sure the bridge between the networks keeps working well.
- They have a plan to make this happen by triggering something called an extrinsic on the blockchain.
- This will force the transfer of the 4 million PHA coins from one account to the other.

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

- Phala wants to send a message to Polkadex.
- They will use a code to send the message.
- The code means they want to open a channel with Polkadex.
- Phala has enough money to open the channel.
- They need other people to agree to this plan.

Democracy External Proposals