agorix
AirdropMarketsCollectionsLeaderboardActivity
Agorix · Decentralized Marketplace
Independent · Resilient · Community-Run

A cross-chain marketplace, run by the community.

Discover, list, and trade across Bitcoin, Ethereum, and Solana on an open, community-run network.

Marketplace
CollectionsMarketsLeaderboardActivity
Network
GovernanceExplorerAirdropDocs
Account
ProfileSettings
Legal
Terms of ServicePrivacy PolicyYour Privacy Choices
agorix.io — Lasting Access
CID: 0xA60R1X · v0.1
AirdropMarketsCollections
D
Protocol Docs
GovernanceToken EconomicsMPC TreasuryMisbehavior StrikesDelegation SystemBurn Voting
Docs/Governance & Economics/Governance
Governance & Economics

Governance

1-Node-1-Vote governance across 13 configurable domains. Node voting, delegation, burn voting, proposal lifecycle, and foundation beta powers.

#Governance

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.

#13 Governance Domains

Every runtime parameter lives in one of 13 governance categories. Each category groups related parameters that can be proposed and voted on independently.

DomainKeyWhat It Controls
Gateway RoutinggatewayRoutingCache TTL, cohort sizing, node recommendation limits
Marketplace Fee SplitmarketplaceFeeSplitFoundation vs. reward pool allocation (default 50/50 at 5000 bps each)
Token Swap FeetokenSwapFeeMarketplace swap fee (default 200 bps = 2%, max 2000 bps)
Token RewardstokenRewardsIncentive rates, burn allocation, user reward share
Burn VotingburnVotingProposal creation cost, per-wallet caps, advisory quorum
Node EconomicsnodeEconomicsMin stake, admission fee, collateral types, cooldown periods
Node PerformancenodePerformanceBandwidth, latency, disk I/O, CPU score thresholds
Beta SafetybetaSafetyFoundation veto, config locks, label overrides
Governance PolicygovernancePolicyVote threshold, min voting power, open proposal limits
Witness ScalingwitnessScalingLogarithmic curve coefficients, min/max witnesses, quorum bps
Data RetentiondataRetentionEvent log TTL, media cache duration, PSBT cleanup, compaction
Reward ClaimsrewardClaimsClaim expiry, moderation reward amount, moderation quorum
MPC TreasurympcTreasuryThreshold bps, epoch frequency, reshare grace period

#1-Node-1-Vote

The voting model is deliberately flat:

  • Stake is the entry ticket. You must bond the minimum stake (currently $1,000 USD, demand-adjusted) to become a voting node.
  • Every node gets exactly one vote. A node that staked $10,000 has the same voting power as a node that staked $1,000.
  • Delegation amplifies influence. The only way to gain more than one vote is to receive delegations from other nodes (see the Delegation System page).
  • Effective voting power = 1 (own vote) + count of active delegations received.

#Three Governance Tracks

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.

#Proposal Lifecycle

Every governance proposal moves through a defined state machine:

text
PROPOSED  -->  Voting Period  -->  READY (quorum met)
                               -->  REJECTED (quorum failed or expired)
READY     -->  Applied by governance engine  -->  APPLIED

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

#Foundation Role (Beta Period)

During beta, the foundation master node (Node-1) holds temporary powers:

  • Veto governance votes -- can block any proposal during beta
  • Direct config changes -- can modify parameters without a vote
  • MPC ceremony activation -- manually triggers initial DKG
  • Reward token creation -- decides when to launch the token
  • Fee recipient -- receives admission fees and foundation fee split

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.

#Production Activation Sequence

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:

  • Network bootstrap — Foundation runs Node-1 and a small number of seed nodes; staking opens; admission fee flow live
  • Quorum formation — Once enough independent operators have joined and passed PoA challenges, real witness quorums form for transactions
  • MPC keygen activation — When the operator set is large and stake-distributed enough that no single party controls 33%, the foundation manually triggers the first DKG ceremony. Until this point mpcTreasury.enabled is true but autoInitiateCeremony is false, so DKG only happens on explicit activation
  • Reward token launch — Foundation deploys the reward token contract and mints the supply schedule. Only after this point do reward claims become claimable on-chain
  • Beta lock removal — As the network proves it can self-govern, the foundation submits proposals to remove its own veto and direct-config powers. Each lock is removed by a normal governance vote

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

#Beta Lock Behavior

While beta locks are active, three mechanisms cooperate to keep the foundation honest:

  • Default-locked keys are limited to marketplaceFeeSplit, governancePolicy, and betaSafety — the keys whose abuse would directly compromise economic guarantees
  • Lock changes themselves are foundation events — locking or unlocking a key is a signed protocol event visible in the explorer
  • No silent overrides — even when the foundation directly changes a parameter, a FOUNDATION_CONFIG_OVERRIDE event records the before/after value, the timestamp, and the foundation's signature

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

#Transparency

Every foundation action is a signed protocol event:

  • Gossiped to all nodes in the network
  • Stored in the protocolEvents table
  • Visible in the explorer UI

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

#Misbehavior Enforcement

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.

PreviousCollection Preseed QueueNext Token Economics

On this page

  • Governance
  • 13 Governance Domains
  • 1-Node-1-Vote
  • Three Governance Tracks
  • Proposal Lifecycle
  • Foundation Role (Beta Period)
  • Production Activation Sequence
  • Beta Lock Behavior
  • Transparency
  • Misbehavior Enforcement