Gemini Tokenomics (Worker Rewards)
This document contains the Supply-end Tokenomics for Phala Network, which defines how workers get their rewards by sharing the computing power.
To read about how Demand-end users can stake PHA to use the network, see Stake to Compute.
After the approval of the āGemini Tokenomics upgrade" democratic referendum on the block height #1,467,069, we have updated the content of the Supply-end Tokenomics as follows:
Design Targets
The overall economic design is built to address these points:
Support Phala Networkās trustless cloud computing architecture
Consensus-Computation Separation
Linearly-scalable computing workers (100k order of magnitude number of workers)
Incentivize workers to join the network
Ensure payment for power supplied irrespective of demand, especially at network bootstrap
Subsidize mining pool with 70% of the initial supply over time
Bitcoin-like budget halving schedule
Power the Phala and Khala at the same time
Application pricing
On-chain performance
The following details some key elements of the economic model.
Overall Design
Related Workers
Phala Supply-end Tokenomics applies to any workers running on Phala or Khala.
Value Promise
A virtual score for an individual worker representing value earned which is payable in the future, to motivate workers to behave honestly and reliably
Equal to the expected value of the revenues earned by the worker for providing power for the platform
Changes dynamically based on the workerās behaviors and the repayment of Rewards
Mining honestly: grows gradually over time
Harmful conduct: punished by reduction of
Initial
A Worker will run a Performance Test and stake some tokens to get the initial :
is a Stake Multiplier set by the network (Khala or Phala).
is the worker stake; a Minimum Stake is required to start mining. The stake canāt be increased or decreased while mining, but can be set higher than the Minimum.
is the estimated cost of the worker rigs, inferred from the Performance Test.
is based on the workerās IntelĀ© SGX capabilities.
is always less than or equals to .
Params used in simulation:
for different Confidence Levels
Performance Test
A performance test measures how much computation can be done in a unit of time:
For reference,
Low-End Celeron
4
450
$150
Intel Xeon E Processor
6
1900
$500
Mid-End i5 10-Gen
8
2000
$500
High-End i9 9-Gen
10
2800
$790
The table is based on the version while writing of this documentation and is subject to changes.
The performance test will be performed:
Before mining to determine the Minimum Stake
During mining to measure the current performance, and to adjust the $V$ increment dynamically
Minimum Stake
- Performance Test score
- adjustable multiplier factor
Proposed parameter:
Locked state $PHA token can also be used for mining staking, e.g., Khala Crowdloan reward
Cost
is the current PHA/USD quote, dynamically updated on-chain via Oracles
is the initial Performance Test score.
In the early stages, we are compensating the equipment cost with a higher Value Promise.
In the future, we plan to compensate for higher amortization costs (adding equipment amortization cost to the running costs and ), thus increasing the speed of growth of the Workerās .
General mining process
Each individualās is updated at every block:
Increased by if the worker keeps mining
Decreased by if the worker got a payout
Decreased according to the Slash Rules if the worker misbehaves
When a worker gets a payout , they will receive the amount immediately in their Phala wallet. The payout follows Payout Schedule and cannot exceed the Subsidy Budget.
Finally, once the worker decides to stop mining, they will wait for a Cooling Down period $\delta$. They will receive an one-time final payout after the cooldown.
Value Promise
$V_t$
$V_{t+1}$
$\dots$
$V_T$
$\dots$
$\dots$
Payment
$w(V_t)$
$w(V_{t+1})$
$\dots$
$w(V_T)$
$0$
$\kappa \min(V_T, V^e)$
Block reward
ā¦
ā¦
Block reward
Cooling off for $\delta$ blocks
Final payout
Proposed parameter:
Update of
When thereās no payout or slash event:
is the unconditional increment factor for worker
is the operational cost to run the worker
represents a factor to compensate for accidental/unintentional slashing (ignored in simulated charts)
, where is the instant performance score, and $P$ is the initial score
If after the update, it will be capped to
Proposed parameters:
(hourly)
Payout Event
In order to stay within the subsidy budget, at every block the budget is distributed proportionally based on the current Worker Shares:
where is the current network subsidy budget for the given payout period.
Whenever is paid to a worker, his will be updated accordingly:
is the value promised at the last payout event, or if this is the first payout.
The update of V is limited to ensure the payout doesnāt cause to drop lower than it was in the last payout event. The limit is necessary to make sure workers are well incentives to always accumulate credits in the network. Otherwise, workers are incentivized to constantly reset their mining session if V decreases over time.
Share represents how much the worker is paid out from . We expect it will approximate the share baseline, but with minor adjustments to reflect the property of the worker:
contains the share of workers which are running on Phala or Khala with the same subsidy ratio.
Proposed algorithm:
is the instant performance score
Subsidy Budget
Relaychain
Polkadot/ Kusama
Budget for Mining
700 mln
Halving Period
180 days
Halving Discount
25%
Treasure Share
20%
First Month Reward
21.6 mln
Heartbeat & Payout Schedule
In any block , if the Workerās VRF is smaller than their current Heartbeat Threshold , they must send the Heartbeat transaction to the chain, which will update the on-chain record of their Value Promise and send a Mining Reward to their reward wallet:
If they fail to send the Heartbeat transaction to the chain within the challenge window, the update of their value promise will be
and their status is changed to unresponsive, and they will get repeatedly punished until they send a heartbeat, or stop mining. The slash amount is defined in the Slash section.
The target is to process around 20 heartbeat challenges per block. The heartbeat challenge probability will be adjusted to target this number of challenges.
Potential parameters:
(blocks)
Slash rules
The slash rules for workers are defined below. No slash rules have been implemented at the moment but will start in the near future.
Level1
Worker offline
0.1% V per hour (deducted block by block)
Level2
Good faith with bad result
1% from V
Level3
Malicious intent or mass error
10% from V
Level4
Serious security risk to the system
100% from V
Final payout
When a worker chooses to disconnect from the platform, they send an Exit Transaction and receive their Severance Pay after blocks.
After the cooling down period, the worker gets their final payout, representing the return of the initial stake. However, if goes lower than the initial , the worker will get less stake returned as a punishment:
where is the initial stake.
Last updated