Compute Pools
How causes are funded, how staking works, and why depth beats breadth.
What Are Compute Pools
When users mint CPT, the underlying reserve generates yield that funds a protocol-level compute pool. This pool is allocated across all causes and funds the baseline development output of the protocol.
Staking CPT into a specific cause creates dedicated compute for that cause on top of its protocol-level allocation. The more CPT staked into a cause, the more dedicated compute it receives, and the more software it can build. This creates a direct link between community commitment and development output.
Staking: Breadth vs Depth
Holding CPT without staking gives you broad access: you can vote across all causes and receive a base share of protocol-wide revenue. Staking CPT into a cause trades that breadth for depth.
Stakers receive amplified voting power within their chosen cause, a boosted share of that cause's software revenue, and pro-tier access to that cause's products. Longer commitments result in stronger voting weight and additional benefits that are unlocked related to the cause.
Key Properties
- Cause-specific: Each stake targets a single cause
- No minimum: Any amount can be staked
- Commitment rewards: Longer commitment results in higher voting power and yield share
- Splittable: Stake across multiple causes, with power proportional to each allocation
Pool Growth
Compute pools grow through new CPT stakes, commission payments, and revenue reinvestment. Every source of capital is permanent. Once in the reserve, it generates yield forever. This means a cause's compute capacity only ever increases.
Pool Permanence
Once a cause pool reaches sufficient scale and passes an allocation threshold, it becomes permanent and cannot be shut down or merged. This guarantees that a chosen cause will continue to receive compute and build software indefinitely, regardless of protocol-level governance decisions.