- The proposal aims to increase the Council members' seats to 8 in Q4 for both Phala Network and Khala Network.
- Anyone can apply for the council seat, but candidates should understand the Phala council election algorithm and the delegation process, have contributed to the community before, and commit their time to the Phala community.
- To apply to be a council member, follow the instructions on the Khala Network website.
- Council members won't get paid, but they will have the right to participate in Phala/Khala on-chain governance, supervise the treasury usage, and have chances to be a Curator of Treasury Bounties.
- The Bounty Spending proposals aim to delegate the curation activity of spending proposals to experts called Curators, who are selected by the council after the bounty proposal passes and need to add an upfront payment to take the position.

Adding up Khala/Phala council seats into 8 - public proposal #17

- A message will be sent on Kusama to accept a request from Crust and open a channel to Turing.
- The message has a special code that tells Kusama what to do.
- Khala has enough money to open the channels.
- The channel will allow for communication between different groups.
- The message is like a secret code that tells Kusama what to do.

Establish Khala<->Crust HRMP - motion #114

Untitled - public proposal #16

Khala Runtime Upgrade v1170 - motion #122

SubSquare is proposing to create 44 million PHA tokens for the SubBridge reservation account. SubBridge connects Khala and Ethereum to transfer PHA between them. Khala should have 1 billion PHA supply, but there are still 463.2 million PHA locked for mining subsidy and 38 million locked for crowdloan reward. Khala's total supply should be 498.8 million PHA. However, there is an imbalance in the supply due to the miscalculation in the initial bridge launch. In this proposal, they will fix the 6 million PHA imbalance and add the 38 million crowdloan funds to the reservation.

Mint reserved funds for Phala crowdloan unlock - motion #119

- A motion is being made to redo a previous motion.
- The motion is about accepting a request from Crab Network.
- A message will be sent on Kusama.
- The message will have a specific call to accept the request.
- Khala's account already has enough deposit to open the channels.

Redo: Accept Crab -> Khala HRMP - motion #117

Open Khala -> Crab Network HRMP - motion #110

Accept HRMP channel from Basilisk & Calamari - motion #104

Khala Runtime Upgrade v1160 - motion #95

Open Khala->Basilisk HRMP - motion #94

Open Khala->Calamari HRMP - motion #91

Untitled - public proposal #13

- A message will be sent to Kusama to accept a request from Turing and open a channel.
- The message has a special code that tells Kusama what to do.
- Khala has enough money to open the channel.
- The channel will be used to send messages between Khala and Turing.
- The channel has a limit on how much can be sent and how big the messages can be.

Accept and open Khala<->Turing HRMP  - motion #88

Khala Runtime Upgrade v1150 - motion #89

The dawning realization my hash is incorrect #14

Release some locked XCM PHA transfer from Karura (2) - motion #86

Thibaut is a French software developer who wants to help Phala expand. He has experience in Java and Ethereum security and has been developing for over 7 years. He wants to become a registrar for Phala because he believes in their potential and wants to contribute to the community. Thibaut thinks that privacy is important and wants to be a leading actor in solving the lack of knowledge about Polkadot in France. He can speak French, English, and Spanish and is learning Mandarin. Thibaut can be contacted through Telegram, Discord, Matrix, or email. He has a document that explains how he will make his decisions.

Thibaut Gautier / Registrar Application - public proposal #15

- There is a problem with Karura's app that caused two users' XCM transfer to get stuck.
- The XCMs were executed on Karura but not on Khala due to an incorrect weight issue.
- The assets are burnt on Karura but not distributed to the users on Khala.
- A motion is proposed to transfer the locked funds directly to the destination user using "balances.forceTransfer".
- A detailed user list can be found on the provided link.

Release some locked XCM PHA transfer from Karura - motion #84

Accept 2004 and 2111 swap on Kusama - motion #83

Update tokenomic parameter to match 15s block time - motion #78

Khala Runtime Upgrade v1140 - motion #79

Emergent chain data recovery - motion #76

Khala runtime upgrade v1131 and batch fixes - motion #75

Accept Moonriver->Khala HRMP channel - motion #70

- Phala and Khala are two blockchains that share the same PHA token.
- The proposal aims to merge the reward pools of both blockchains to balance the computing resources between them.
- The mining reward on both blockchains will converge to the same level based on the on-chain metrics.
- The two blockchains will share all the parameters except the subsidy budget, which will be maintained through a bridge between the two chains.
- The proposal will be discussed in the community, followed by a public vote, and if passed, the tokenomic runtime upgrade will take place.

Democracy Referenda