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/Delegation System
Governance & Economics

Delegation System

Vote delegation with fee forfeiture, escalating cooldowns, one-to-one constraints, and automatic revocation on exit.

#Delegation System

Not all nodes will actively participate in every governance vote. Delegation lets active operators represent passive ones, preventing governance stalls while maintaining the 1-Node-1-Vote principle.

#How Delegation Works

  • A node operator opts into delegate mode by publishing a NODE_DELEGATE_STATUS_CHANGED event with status ACTIVE.
  • Other nodes can delegate their vote to this delegate by publishing a NODE_DELEGATION_CHANGED event with action DELEGATE.
  • The delegate's effective voting power becomes: 1 (own vote) + count of active delegations received.
  • Nodes that have delegated their vote away have 0 effective power and cannot vote directly.

#Fee Forfeiture

Delegates forfeit their own fee eligibility entirely. This is a deliberate design trade-off:

  • When a node enters delegate mode, its feeEligible flag is set to false.
  • The node cannot earn NODE_FEE_REIMBURSEMENT or NODE_INCENTIVE claims while in delegate mode.
  • This mirrors a "politician" model: you represent others, you do not also collect marketplace fees.
  • Fee forfeiture is enforced at the stake position level and broadcast as a NODE_STAKE_UPDATED event.

#Escalating Unstake Cooldown

The longer a node stays in delegate mode, the longer its unstake cooldown becomes:

text
cooldown = min(baseCooldownHours + daysInDelegateMode * 24, 8760)

Where baseCooldownHours is the governance-configured unstakeCooldownHours (default: 24 hours) and the maximum plateau is 8760 hours (1 year).

Days in Delegate ModeEffective Cooldown
024 hours
7192 hours
30744 hours
902,184 hours
3658,760 hours (max)

This prevents delegates from accumulating political power and then quickly unstaking to exit without consequence.

#Constraints

  • One delegation per delegator. Each node can only delegate to one other node at a time. Changing delegates requires revoking the current delegation first.
  • No chaining. A delegate cannot re-delegate votes received from other nodes. Delegated power is not transitive.
  • No self-delegation. A node cannot delegate to itself.
  • Stake required. Both the delegator and the delegate must have an ACTIVE stake position.

#Auto-Revocation

When a delegate exits delegate mode (publishes NODE_DELEGATE_STATUS_CHANGED with status EXITED):

  • All incoming delegations are automatically revoked.
  • Each delegator receives their vote back (effective power returns to 1).
  • NODE_DELEGATION_CHANGED events with action REVOKE are published for each affected delegator.
  • The former delegate's fee eligibility can be restored (subject to the escalated cooldown for unstaking).

#Database Schema

Two tables track delegation state:

nodeDelegateRegistrations -- Tracks which nodes are in delegate mode:

  • agentPubkey: The node that registered as a delegate
  • status: ACTIVE or EXITED
  • enteredAt: Timestamp when delegate mode was activated (used for cooldown calculation)
  • exitedAt: Timestamp when delegate mode was deactivated

nodeDelegations -- Tracks individual delegation relationships:

  • delegatorPubkey: The node giving its vote away
  • delegatePubkey: The node receiving the delegated vote
  • revokedAt: Null while active, set when revoked

#Voting Power Calculation

When a governance vote is tallied:

  • Each non-delegating, non-penalized, ACTIVE node counts as 1 vote.
  • Each active delegate counts as 1 + (number of active incoming delegations).
  • Nodes that have delegated their vote count as 0.
  • Penalized or banned nodes count as 0 regardless of delegation status.

The total eligible voting power equals the count of ACTIVE, non-penalized nodes (both direct voters and delegates). The quorum is calculated against this total.

PreviousMisbehavior StrikesNext Burn Voting

On this page

  • Delegation System
  • How Delegation Works
  • Fee Forfeiture
  • Escalating Unstake Cooldown
  • Constraints
  • Auto-Revocation
  • Database Schema
  • Voting Power Calculation