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/Misbehavior Strikes
Governance & Economics

Misbehavior Strikes

Escalating strike system for protocol violations. Fee suspensions, permanent bans, strike decay, and public misbehavior proofs.

#Misbehavior Strikes

Nodes that violate protocol rules face an escalating strike system. Each confirmed misbehavior proof increments the node's strike counter and triggers progressively harsher penalties.

#Strike Escalation

StrikePenaltyDuration
1stFee eligibility suspended24 hours
2ndFee eligibility suspended72 hours
3rdFee eligibility suspended168 hours (7 days)
4th+Permanent banIrreversible

When a strike is applied, the node's feeEligible flag is set to false on its stake position. A NODE_STAKE_UPDATED event is broadcast to all nodes so the entire network knows the node is suspended.

#Strike Decay

Strikes are not permanent (unless you hit 4):

  • After 30 days of clean behavior (no new misbehavior proofs), one strike decays automatically.
  • Decay is checked at the time a new strike would be applied -- if enough time has passed since the last proof, the counter decrements by 1 before the new strike is added.
  • A node with 3 strikes that stays clean for 30 days drops to 2. Another 30 clean days drops to 1. Another 30 drops to 0.
  • Banned nodes cannot benefit from decay. Once a node hits strike 4 and receives a permanent ban, the banned flag is irreversible regardless of time elapsed.

#Misbehavior Proof Types

Each proof type targets a specific protocol violation:

Proof TypeWhat It Catches
FEE_OUTPUT_MISMATCHTransaction fee outputs do not match the expected fee structure
ROYALTY_MISMATCHCreator royalty payments are missing or incorrect
QUOTE_SIGNATURE_INVALIDThe node submitted a quote with an invalid or forged signature
WITNESS_SELECTION_MISMATCHThe node manipulated witness selection to favor specific nodes

Additionally, the poa_wrong_answer kind covers nodes that give definitively wrong chain data during Proof-of-Access challenges.

#Proof Structure

Every misbehavior proof contains:

  • txid: The transaction where the violation occurred
  • orderId: The order associated with the violation
  • proofType: One of the four proof types above
  • expected: What the correct values should have been
  • actual: What the node actually submitted
  • evidencePointers: References to on-chain data or protocol events that prove the violation

#Fee Eligibility Suspension

When a node is struck:

  • The nodeMisbehaviorPenalties table records the new strike count, suspension timestamp, and suspension end time.
  • The node's stake position has feeEligible set to false.
  • A NODE_STAKE_UPDATED event propagates the change across the network.
  • During suspension, the node is not fee-eligible and cannot earn NODE_FEE_REIMBURSEMENT or NODE_INCENTIVE claims.
  • When the suspension expires, fee eligibility is restored during the next heartbeat processing cycle.

For permanent bans (strike 4+), there is no suspendedUntil timestamp -- the ban has no end date.

#Integration with Other Systems

  • Eligibility checks: The isNodePenalized check removes a penalized node's fee eligibility and blocks it from voting on governance config.
  • Fee distribution: Only nodes with feeEligible = true and status = "ACTIVE" participate in fee splits.
  • Delegation: A banned node's delegations are effectively worthless since the node cannot participate.
  • Explorer: All misbehavior proofs and strike events are visible in the protocol event explorer.

#Public Accountability

All misbehavior proofs are public protocol events:

  • The MISBEHAVIOR_PROOF event contains the full proof payload with evidence.
  • Any node or user can verify the proof independently using the evidence pointers.
  • The explorer displays strike history per node, including proof details and suspension timelines.
  • There is no private or hidden enforcement -- every penalty is auditable.
PreviousMPC TreasuryNext Delegation System

On this page

  • Misbehavior Strikes
  • Strike Escalation
  • Strike Decay
  • Misbehavior Proof Types
  • Proof Structure
  • Fee Eligibility Suspension
  • Integration with Other Systems
  • Public Accountability