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
Public APISmart ContractsSecurity ModelOpen SourceRust Node CoreGetting Started (Developer)Benchmarks
Docs/Developer/Security Model
Developer

Security Model

Comprehensive security architecture. Cryptographic primitives, 8 defense layers, threat model, rate limiting escalation, and MPC treasury protection.

#Security Model

Built on defense in depth. Multiple independent security layers make sure no single failure can compromise the system.

#Cryptographic Primitives

PrimitiveLibraryUsage
Ed25519TweetNaClEvent signatures, quote signing, release verification, node identity, reveal challenges
secp256k1@noble/secp256k1Bitcoin/Ethereum transaction signing, MPC key shares
SHA-256@noble/hashesContent hashing, witness seed derivation, challenge derivation, event IDs
HMAC-SHA256@noble/hashesWitness selection seeding, deterministic node assignment
AES-256-GCMNode.js cryptoPSBT encryption (authenticated encryption with associated data)
Shamir's Secret SharingCustom GF(256)PSBT key shard distribution (3-of-4 threshold)

Every cryptographic operation uses audited, well-tested libraries. No custom cryptography. Ed25519 via TweetNaCl (the original djb implementation) and hashing via @noble/hashes (audited, zero-dependency).

#MPC Threshold Signatures

The protocol treasury uses multi-party computation (MPC) threshold signatures:

  • Key never reconstructed. The private key is split across ALL active nodes. No single node (or minority of nodes) ever holds the complete key.
  • 67% threshold (BFT standard). Signing requires 2/3 of key share holders to participate. This matches the Byzantine fault tolerance threshold used throughout the protocol.
  • No hot wallet. There is no server, vault, or HSM holding the treasury key. The key exists only as distributed shares.
  • Weekly epoch batching. Treasury operations (reward distributions, fee payouts) are batched into weekly epochs to minimize signing ceremonies.
  • Auto-reshare on membership changes. When nodes join or leave, key shares are redistributed without reconstructing the original key. Uses proactive secret sharing protocols.
  • Emergency health-based reshare. If the network detects that too many share-holders are unhealthy (offline, slow, or failing PoA), an emergency reshare triggers with a 5-minute grace period.

#Threat Model

What we protect against:

  • Single node compromise. No single node can forge transactions, steal assets, or manipulate governance.
  • Minority collusion. Up to 1/3 of witnesses can be compromised without affecting consensus.
  • Sybil attacks. Bonding requirements and PoA challenges prevent fake nodes.
  • Front-running. Unpredictable witness selection (HMAC-SHA256 with blockchain beacon seeds) prevents advance positioning.
  • Replay attacks. Nonces, salts, and per-order reveal tokens prevent reuse across orders and chains.
  • Man-in-the-middle. Ed25519 signatures on all protocol events. Nodes verify signatures before processing.
  • Key compromise. MPC treasury means there's no single key to steal. PSBT shards mean no single node holds a complete encrypted transaction.
  • Rogue contracts. TX-plan quorum verification and contract allowlisting prevent interaction with malicious smart contracts.

What we rely on:

  • Blockchain security. The underlying chains (BTC, ETH, SOL) provide settlement finality.
  • Cryptographic hardness. Standard assumptions (discrete log problem, hash collision resistance).
  • Honest supermajority. At least 2/3 of witnesses must be honest for correct attestation.

#8 Defense Layers

Layer 1: Protocol Determinism. Every node computes the same truth independently from the same inputs. No coordinator to compromise, no leader to bribe, no authority to coerce. The protocol package has zero external dependencies and produces identical outputs on every node.

Layer 2: Threshold Attestation. Transactions require 2/3 supermajority witness agreement (TX_ATTESTATION events). Compromising a minority of witnesses achieves nothing. The attestation threshold matches the BFT standard used in the MPC treasury.

Layer 3: Proof of Access. Witnesses must prove real-time blockchain RPC access via chain-specific challenges (5 for BTC, 3 for ETH, 3 for SOL). Challenges query unpredictable historical state. Can't fake attestations by copying other nodes' responses.

Layer 4: Pooled Network Fees. The network share of every fee is paid to the chain's reward pool wallet, which is set by governance (rewardPool.recipients) and not by the node handling the sale. If no pool wallet is configured for a chain, the sale is refused. Each epoch the pool is settled by a deterministic calculation over recorded work that any node can recompute. The lottery seed uses a beacon that is only known after the epoch closes, so nobody can choose it.

Layer 5: MPC Treasury. Treasury funds require 67% threshold multi-party signing. No hot wallet to hack, no single key to steal, no admin override. Weekly epoch batching reduces the signing ceremony attack surface.

Layer 6: Release Verification. Client-side hash verification ensures authentic code delivery. The verification path doesn't trust any single server. Manifest hashes are signed with the foundation's Ed25519 key and verifiable by any node.

Layer 7: Rate Limiting with Gossip Propagation. Multi-tier rate limiting with escalating cooldowns and network-wide ban propagation:

Violation LevelCooldownScope
First offense5 minutesLocal to the receiving node
Second offense15 minutesLocal to the receiving node
Third offense60 minutesLocal to the receiving node
Fourth offense24 hours + gossip banPropagated to ALL nodes in the mesh

At tier 4, the offending client's identifier is gossiped as a ban event. Every node in the network blocks the client without requiring independent detection.

Layer 8: Governance Safeguards. Parameter changes require node consensus through the governance system. During the beta period, the foundation master node (Node-1) retains veto power to prevent premature or malicious parameter changes. All governance actions are signed protocol events visible in the explorer.

#Non-Custodial Design

The protocol never takes custody of user assets:

  • Bitcoin. Seller holds private key. PSBT shards hold the encrypted transaction template, not the key. Reconstruction requires buyer action.
  • Ethereum. Smart contract is the only escrow point. Release triggered by valid EIP-712 signature. No admin key on the contract.
  • Solana. Program-verified transfers. No intermediate custody account.

#Incident Response

All security-relevant events follow the transparency protocol:

  • Signed by the originating node's Ed25519 key.
  • Gossiped to all nodes via the push/pull protocol.
  • Stored in the immutable event log.
  • Visible in the protocol explorer.
  • Subject to governance review if they involve parameter changes or strikes.

#Foundation Transparency

All foundation actions (veto, parameter changes, manual interventions) must be signed protocol events gossiped to all nodes and visible in the explorer. The foundation cannot act in secret. Every action is cryptographically attributable and permanently recorded.

PreviousSmart ContractsNext Open Source

On this page

  • Security Model
  • Cryptographic Primitives
  • MPC Threshold Signatures
  • Threat Model
  • 8 Defense Layers
  • Non-Custodial Design
  • Incident Response
  • Foundation Transparency