1-Node-1-Vote governance across 13 configurable domains. Node voting, delegation, burn voting, proposal lifecycle, and foundation beta powers.
The protocol is governed by a 1-Node-1-Vote system. Stake gets you in, but every bonded node gets exactly one vote regardless of how much it staked. This prevents whale domination while still requiring skin in the game.
Every runtime parameter lives in one of 13 governance categories. Each category groups related parameters that can be proposed and voted on independently.
| Domain | Key | What It Controls |
|---|---|---|
| Gateway Routing | gatewayRouting | Cache TTL, cohort sizing, node recommendation limits |
| Marketplace Fee Split | marketplaceFeeSplit | Foundation vs. reward pool allocation (default 50/50 at 5000 bps each) |
| Token Swap Fee | tokenSwapFee | Marketplace swap fee (default 200 bps = 2%, max 2000 bps) |
| Token Rewards | tokenRewards | Incentive rates, burn allocation, user reward share |
| Burn Voting | burnVoting | Proposal creation cost, per-wallet caps, advisory quorum |
| Node Economics | nodeEconomics | Min stake, admission fee, collateral types, cooldown periods |
| Node Performance | nodePerformance | Bandwidth, latency, disk I/O, CPU score thresholds |
| Beta Safety | betaSafety | Foundation veto, config locks, label overrides |
| Governance Policy | governancePolicy | Vote threshold, min voting power, open proposal limits |
| Witness Scaling | witnessScaling | Logarithmic curve coefficients, min/max witnesses, quorum bps |
| Data Retention | dataRetention | Event log TTL, media cache duration, PSBT cleanup, compaction |
| Reward Claims | rewardClaims | Claim expiry, moderation reward amount, moderation quorum |
| MPC Treasury | mpcTreasury | Threshold bps, epoch frequency, reshare grace period |
The voting model is deliberately flat:
1. Node Voting (Binding)
Bonded node operators propose and vote on runtime configuration changes. These votes directly modify protocol parameters. Different parameters have different quorum requirements based on sensitivity. The governance policy controls the vote threshold (default: 2 nodes minimum) and limits on open proposals per key (16) and per node (4).
2. Token Burn Voting (Advisory)
Public token holders signal preferences by burning tokens. USD-indexed, not fixed token count. Advisory only -- burn votes never directly change parameters. See the Burn Voting page for full details.
3. Delegation
Nodes can delegate their voting power to a trusted operator. Delegates forfeit their own fee eligibility and accrue escalating unstake cooldowns. No chaining allowed -- a delegate cannot re-delegate received votes. See the Delegation System page for full details.
Every governance proposal moves through a defined state machine:
PROPOSED --> Voting Period --> READY (quorum met)
--> REJECTED (quorum failed or expired)
READY --> Applied by governance engine --> APPLIEDDuring beta, the foundation can lock specific config keys. Proposals targeting locked keys are rejected with a BETA_LOCKED status. The default locked keys are: marketplaceFeeSplit, governancePolicy, and betaSafety.
During beta, the foundation master node (Node-1) holds temporary powers:
These powers are gated by a betaMode flag. As the network matures and decentralizes, beta powers get progressively removed through governance votes. The goal is full removal of all foundation special privileges.
In a fresh production launch, several capabilities start dormant on purpose. Distributing key shares before there are enough independent operators to make threshold security meaningful would just hand the network to whoever holds the early shares. The foundation activates these capabilities in a defined order as decentralization milestones are reached:
mpcTreasury.enabled is true but autoInitiateCeremony is false, so DKG only happens on explicit activationThe dev cluster shortcuts this sequence for convenience: instrumentation.ts auto-triggers DKG immediately so local development does not require manual ceremony coordination. Production never takes this shortcut.
While beta locks are active, three mechanisms cooperate to keep the foundation honest:
marketplaceFeeSplit, governancePolicy, and betaSafety — the keys whose abuse would directly compromise economic guaranteesFOUNDATION_CONFIG_OVERRIDE event records the before/after value, the timestamp, and the foundation's signatureThe end-state for every beta lock is the same: a governance vote unlocks it permanently. Once removed, only the regular proposal process can change the parameter — even the foundation must propose and pass a vote like everyone else.
Every foundation action is a signed protocol event:
protocolEvents tableEvent kinds include FOUNDATION_CONFIG_OVERRIDE, FOUNDATION_VETO, FOUNDATION_MPC_TRIGGER, FOUNDATION_TOKEN_MINT, and FOUNDATION_TREASURY_TX. There are no hidden admin actions. The explorer supports filtering specifically for foundation events.
Nodes that violate protocol rules face escalating strikes: 24h fee suspension, then 72h, then 7 days, then permanent ban. All misbehavior proofs are public protocol events with full evidence. See the Misbehavior Strikes page for the complete strike system.