proposal

Phala Runtime Upgrade v1253 - motion #79

Phala Runtime Upgrade v1252 - motion #78

calls

Whitelist inDEX worker for closed test  - motion #77

- A new version of a program called pruntime has been added to the blockchain registry.
- The new version has some improvements, like upgraded versions of SubXT and Polkadot, and new features like batch HTTP requests and configurable timeout and retries.
- Some issues have been fixed, like problems with restarting and memory leaks.
- The program now allows for bigger storage values and has a new feature called safe handover.
- If you want to learn more, you can check out the full list of changes on the program's Github page.

pruntimeHash

Add pruntime v2.1 - motion #76

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

Open Phala -> Polkadex HRMP (2nd try) - motion #72

Phala Runtime Upgrade v1251 (2nd try) - motion #71

Open Phala -> Polkadex HRMP - motion #70

Phala Runtime Upgrade v1251 - motion #69

- There was a big transfer of money from Ethereum to Khala.
- This caused a shortage of money on the Khala network.
- To fix this problem, a proposal was created to move 2 million PHA from ChainBridge reserve accounts on Khala, Phala, and Ethereum networks.
- The proposal will transfer the money from the source account to the destination account.
- This will help make the bridge work properly.

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

- Ethereum and Khala networks are connected by a bridge.
- Khala network is running out of liquidity due to high usage.
- A proposal has been made to move 500K PHA from one reserve account to another on both Phala and Khala networks.
- This proposal will force transfer 500K PHA from the source account to the destination account.
- This will help maintain the bridge's proper functioning.

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

- SygmaBridge is a tool that helps transfer assets between different chains.
- It has been enabled on Khala and Phala networks.
- A proposal has been made to move 500K PHA from one account to another on both networks.
- This will trigger an action that will force transfer the PHA.
- This will help with transferring assets between different networks.

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

Accept Composable -> Phala Network Open HRMP Request - motion #65

Phala Runtime Upgrade v1250 (2nd try) - motion #64

Phala Runtime Upgrade v1250 - motion #63

- This is a proposal to try again something that didn't work before.
- They want to send a message to ask for something called HRMP request to Composable.
- They will use a code to do this on Polkadot.
- Phala has enough money to do this.
- They are using a different version of something called XCM because the old one didn't work.

Open Phala -> Composable HRMP channel (2) - motion #61

- A mistake in the calculation of halving value in Gemeni Balancer Phat Contract has been fixed.
- Two Gatekeepers, maintained by the Phala team, have been registered with confidence levels 1 and 2 respectively.
- These actions were triggered by a motion.
- This motion is related to another motion called the Khala motion.
- The details of the Gatekeepers and the Phala team are not provided.

Update Gemini Balancer Phat Contract and register GKs - motion #62

Here are five important points about the SubSquare post:

- The post talks about a new motion for Phala Network.
- The motion will add two new GKs and a tokenomic balancer.
- Two workers will be removed from the contract cluster.
- The tokenomic balancer will be controlled by a Phat Contract.
- The contract code is available on GitHub.

Setup GK and Gemini tokenomic balancer (2) - motion #60

Open Phala -> Composable HRMP channel - motion #59

- Two new GKs (0x52dd554813e99c4efe9b086fc385b9ea91c22cbc8967669f66c341da0041f261 and 0x4ce6d07252f7735b88a9c83f048d959b52780fb49405147b3747677f28d07863) are added to Phala Network.
- The new GKs will replace the shutdown workers (0xbc58464ce13637151c51235a31a56472b7fc1fbc76aa4adb10d14c20a79df14a and 0xda9c7aa880cfadddabf9b1667a2daaabfa7c1c421b34e3387dfe67c9284ae179).
- The tokenomic balancer will be controlled by a Phat Contract.
- The contract controlled account is generated within the Phat Contract at 0xaaa789d2b1232cb53e2f3e964d7bf924069becc4979451f9c67935521a7f500e.
- The contract code is available at <https://github.com/Phala-Network/tokenomic-contract>.

Setup GK and Gemini tokenomic balancer - motion #58

Phala Runtime Upgrade v1247 - motion #57

- Phala Network is adding another Gatekeeper for more redundancy.
- The new Gatekeeper is already registered on the blockchain with confidence level 2.
- The Gatekeeper has a pubkey and ecdhPubkey.
- The Gatekeeper has a runtimeVersion and lastUpdated timestamp.
- The Gatekeeper has an operator, attestationProvider, confidenceLevel, initialScore, and features.

Council Motions