- **What:** Request for funds to run public blockchain infrastructure for Phala and Khala in 2025.  
- **Why Needed:** Running blockchain nodes is hard, expensive, and requires expert skills.  
- **Solution:** A shared service makes it easier and cheaper for developers to use Phala and Khala.  
- **Benefits:** Fast, reliable, and low-cost access to blockchain nodes worldwide.  
- **Performance:** Achieved 100% and 99.99% uptime for Phala and Khala in 2024.  
- **Cost:** Total request is $16,490 USD for services in early 2025.  
- **Goal:** Help developers build apps on Phala and Khala without high costs or technical challenges.

proposalId

High Performance Public Infrastructure (Q1 & Q2 2025)

Dwellir - Phala Public RPC Endpoint Services (Q1 & Q2 2025)

- Some Khala account balances were not reported correctly in motion #106.
- The missing amounts were added on Ethereum.
- Three transactions were made to fix this.
- The team needs to move money from the bridge account to fix the ledger.

proposal

Supplement transfer to balance the migration ledger - Council motion #108

accountId

Update tokenomic budget balancer root - Council motion #107

- 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

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

Phala Runtime Upgrade v1271 - motion #104

Close HRMP channels to Parallel - motion #103

Phala Network is seeking funding to extend and enhance the Phala Network Ambassador Program for the second half of 2024. The allocated funds will be used to support and expand the ambassador community, which is integral to increasing brand awareness, fostering community engagement, and driving the adoption of Phala Network's products and ecosystem. 

The current 21 Phala Ambassadors cover languages including Spanish, French, Italian, Portuguese, and more. To increase the number of Phala ambassadors is to cover more time zones and languages, ensuring Phala’s global representation and outreach. 

The objectives are to expand the Ambassador Program, strengthen community engagement, and promote brand awareness. To achieve these objectives, a total budget of 1.43m $PHA is requested for community building initiatives and ambassador incentives and rewards. 

The implementation plan includes recruitment, training and onboarding, and monitoring and evaluation. The community KPIs for H2 2024 are to onboard 30 new Ambassadors and have 40 ambassador-led events globally. 

By funding this proposal, the Phala Network community will directly benefit from a strengthened ambassador program, leading to greater brand visibility, enhanced community engagement, and increased adoption of Phala Network’s innovative AI solutions.

Phala Community Budget - H2 2024

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

- Phala team is adding two new gatekeepers to their system
- The gatekeepers have unique identification numbers
- There are two workers, Worker1 and Worker2, who are associated with the gatekeepers
- Each worker has a set of features and information such as their operator and attestation provider
- The gatekeepers and workers are part of the Phala system, which is used to keep things secure

calls

Add Gatekeepers - motion #100

pruntimeHash

Whitelist pruntime v2.2.1 - motion #99

- 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

- This is a motion to register pruntime v2.2.0 on Phala Network.
- There are two versions of pruntime v2.2.0, one for DCAP SGX remote attestation, and one for IAS.
- The IAS version has a specific mr_enclave and mr_signer, and the DCAP version has a different mr_enclave.
- Both versions have the same isv_svn, isv_prod_id, and git revision.
- The pruntime registration hash is different for each version and includes the mr_enclave and mr_signer.

Pruntime v2.2.0 upgrade - motion #95

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

Update Gatekeepers - motion #93

Phala Runtime Upgrade v1263 - motion #92

Whitelist pruntime 2.1.1 - motion #91

Phala Runtime Upgrade v1262 - motion #90

location

assetId

properties

0x50494e4b

Register PINK on Phala - motion #89

Re-trigger preimage referenda #55 - motion #88

- Three old Gatekeepers are being replaced with three new Gatekeepers.
- The new Gatekeepers are being hosted by the Phala team.
- This change is necessary to maintain the Gatekeepers.
- The new Gatekeepers have a confidence level of 2.
- The new Gatekeepers have specific features and are associated with certain operators.

Council Motions