- 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

- 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

1. Doyle wants to be a Registrar on Phala.
2. He wants to help more people in the community with efficient on-chain certification.
3. Doyle wants to encourage more people to use vaults for reliable staking rewards.
4. Phala is a growing blockchain technology.
5. Doyle is excited to work with the community to build a brighter future for Phala.

Proposal for nominating Doyle as a Phala Registrar

- 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

Open Phala -> Composable HRMP channel - motion #59

Phala Runtime Upgrade v1247 - motion #57

Phala Runtime Upgrade v1246 - motion #55

Phala Runtime Upgrade v1245 - motion #54

- 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

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

Phala Runtime Upgrade v1243 (2nd) - motion #48

Phala Runtime Upgrade v1243  - motion #45

- Phala Network is getting an upgrade called Phala Network Runtime v1242.
- This upgrade will have new features like Phala Compute, Stake Pool, and Phat Contract pallets.
- There was a syncing problem that will be fixed with this upgrade.
- The upgrade is a part of the Phala Compute & Phat Contract launch.
- For more information, you can check out the link provided.

Phala Runtime Upgrade v1242 - motion #43

Here are 5 important points about the SubSquare post:

- There is a proposal to upgrade the Phala Network Runtime to v1230.
- This upgrade will add a new feature called inDEX pallet.
- The upgrade will also prepare for the launch of Phala Compute & Phat Contract.
- The substrate (Polkadot v0.9.40) will be upgraded with database stability improvements.
- However, the post recommends voting Nay to this proposal because it has been replaced by Motion #37.

Phala Runtime Upgrade v1230 - motion #36

SubSquare is proposing to move 308.2 million PHA tokens from the Ethereum subsidy pool to the Phala subsidy pool to pay for compute rewards to workers on the Phala chain. This will enable PHA transfer. 

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

There are still 127 million tokens left in the Khala subsidy pool and 308.2 million tokens locked in the Ethereum subsidy pool. 

In the future, funds will be periodically transferred between the Phala and Khala subsidy pools based on their balances to ensure that both chains have sufficient tokens to pay computation rewards. 

The rules for distributing rewards will be implemented by a dedicated budget balancer introduced in the referendum.

Adjust bridge reservation for the 308.2M PHA compute reward unlock - motion #41

Prepare for Phala Network Compute Launch (3) - motion #40

Phala team was planning to release a new version of their software called Phala Network Runtime v1230. However, they found a mistake in the SubBridge asset registry migration, so they decided to skip v1230 and release v1240 instead. The new version includes all the features of v1230 and a bug fix for SubBridge. The features of v1230 include adding inDEX pallet, preparing for Phala Compute & Phat Contract launch, and upgrading upstream substrate (Polkadot v0.9.40) with database stability improvements. For more details, please check the provided link.

Phala Runtime Upgrade v1240 - motion #37

- Phala Network is going to be upgraded to a new version called runtime v1221.
- This version doesn't have any new features, it just updates the network to the latest substrate.
- The previous upgrade was cancelled because it missed some important storage migration.
- The new upgrade will also update the Phala council to match the Khala council members.
- The upgrade is expected to fix the issues from the previous attempt.

Democracy Referenda