proposal

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.

calls

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.

gatekeeper

Add Gatekeeper operated by the Phala team - motion #56

Phala Runtime Upgrade v1246 - motion #55

Phala Runtime Upgrade v1245 - motion #54

Here's a summary of the SubSquare post content:

- The motion will launch the first cluster with a list of selected workers.
- The public good cluster is a special contract cluster operated by the council.
- It allows anyone to deploy Phat Contracts without permission on Phala Network.
- The owner is responsible for managing the cluster configuration and deployment.
- The owner account can be reproduced with a multisig setting.

owner

permission

deployWorkers

deposit

gasPrice

depositPerItem

depositPerByte

treasuryAccount

Launch the first Phat Contract Public Good Cluster (2) - motion #53

code

Incorrect motion - motion #50

- Phala Network is launching a new cluster called the public good cluster.
- This cluster allows anyone to deploy Phat Contracts without permission.
- The cluster has specific parameters such as gasPrice, depositPerByte, depositPerItem, treasuryAccount, and owner.
- The owner is a multisig account of the current council members responsible for managing the cluster configuration and deployment.
- The multisig account is made up of 8 members who need to approve any changes made to the cluster.

Launch the first Phat Contract Public Good Cluster - motion #52

Set System Contract Code - motion #51

- Phala Network is upgrading its software to improve its performance.
- The upgrade is called Phala Network Runtime v1244.
- The upgrade will fix some problems with the software and make it more stable.
- The upgrade will also enable a new feature called PhalaRegistry::register_worker_v2 in StakePoolManager Proxy.
- This upgrade is part of the Phala Compute & Phat Contract launch.

Phala Runtime Upgrade v1244 - motion #49

SubSquare has made a post about a motion with some important points. Here they are:

- The motion sets up some rules for a network called Khala.
- The reward budget for this network will be 5 PHA per block.
- Three Gatekeepers have been registered with the network.
- A heartbeat has been enabled.
- There is another motion (Motion 46) that has a mistake, so people should vote against it and consider this motion (Motion 47) instead.

Prepare for Phala Network Compute Launch (4) - motion #47

- A motion is being retried because it failed before due to an error in the length of a reference code.
- The original motion is about upgrading the Phala Network Runtime to version v1243.
- The upgrade will enable Phala Compute & Phat Contract pallets and fix some issues with the Gatekeeper launch sequence.
- The upgrade will also improve the stability of the Node client.
- You can find more details about the upgrade in the provided link.

Council Motions