Complete guide for node operators. System requirements, chain infrastructure, staking economics, environment configuration, capabilities, full-node mode, Docker deployment, and dev commands.
Every node in the network is a full marketplace operator. You earn fees by processing transactions, validating protocol truth, and participating in governance.
| Resource | Minimum | Recommended |
|---|---|---|
| CPU | 4 cores | 8 cores |
| RAM | 8 GB | 16 GB |
| Storage | 100 GB SSD | 500 GB NVMe |
| Network | 100 Mbps | 1 Gbps |
| Node.js | 20+ | Latest LTS |
| Rust toolchain | stable | Latest stable |
| PostgreSQL | 16+ | 16+ |
| Redis | 7+ | 7+ |
You need RPC access to the chains you want to support. The Proof-of-Access challenge system continuously verifies that your access is real and responsive:
Bitcoin:
bitcoind full node (pruned is acceptable for basic operations, full is recommended)ord indexer (required for ordinal support -- this is mandatory for BTC capability)Ethereum / EVM:
Solana:
Key environment variables for node operation:
# Node identity
NODE_ID=1 # Unique integer node identifier
AGENT_SECRET_KEY_B64=<base64> # Ed25519 secret key for signing all events
# Database and cache
DATABASE_URL=postgres://user:pass@localhost:5432/agorix
REDIS_URL=redis://localhost:6379
# Rust node-core
RUST_NODE_CORE_URL=http://localhost:9100 # The Rust microservice endpoint
# Network
GATEWAY_DISCOVERY_URL=https://gateway.example.com
# Bitcoin
BTC_NETWORK=mainnet # or testnet, signet, regtest
BTC_RPC_URL=http://localhost:8332
ORD_RPC_URL=http://localhost:8080
# Ethereum / EVM
EVM_RPC_URL=https://eth-mainnet.g.alchemy.com/v2/<key>
BASE_RPC_URL=https://base-mainnet.g.alchemy.com/v2/<key>
ARB_RPC_URL=https://arb-mainnet.g.alchemy.com/v2/<key>
OP_RPC_URL=https://opt-mainnet.g.alchemy.com/v2/<key>
# Solana
SOL_RPC_URL=https://mainnet.helius-rpc.com/?api-key=<key>
# Full-node mode (optional)
FULL_NODE_CHAT=0 # Set to 1 to store all chat threads
FULL_NODE_MEDIA=0 # Set to 1 to cache all media entriesWhen you start a node, the following components run:
To join the network, you must bond a stake. The minimum stake follows a dynamic curve that increases as the network grows:
minimumStake = minStakeUsd + (increment * nodeCount^0.75)This sub-linear curve means the cost of joining grows more slowly than the network itself. Early operators get in cheaply; later operators pay more but join a more valuable network.
| Parameter | Value |
|---|---|
| Admission fee | 5% of stake (non-refundable, burned) |
| Cooldown period | 24 to 168 hours (governance-configurable) |
| Slashing | Bond at risk for provable misbehavior |
| Delegation | Delegates forfeit fees, accrue escalating cooldowns |
Delegates who exercise votes on behalf of delegators forfeit their own fee earnings and accumulate longer unstake cooldowns. This ensures delegation is a public service, not a profit center.
Each node advertises its capabilities via /.well-known/agent. The protocol uses these to determine which nodes are eligible for specific roles:
| Capability | Description |
|---|---|
btc_mempool_watch | Monitors Bitcoin mempool for relevant transactions |
btc_block_watch | Watches new Bitcoin blocks for confirmations |
ord_index_read | Reads ordinal inscription and transfer data from ord |
btc_psbt_share_store | Stores encrypted Shamir PSBT shards |
btc_psbt_share_reveal | Reveals PSBT shards during settlement |
protocol_validate | Runs validateSaleTx() and other protocol checks |
protocol_attest | Signs witness attestations for transactions |
gossip_relay | Relays protocol events to mesh peers |
ui_quote_service | Serves real-time price quotes to frontend clients |
public_server | No longer used. Servers are picked for each visitor from the measured route map; there is no public list to be on |
A node that lacks ord_index_read will never be selected as a witness for Bitcoin ordinal transactions. Capabilities are verified through PoA challenges -- you cannot fake them.
By default, nodes only store data they are responsible for via the shard ring. You can opt into storing everything:
FULL_NODE_CHAT=1 -- Store all chat threads instead of only your assigned shardsFULL_NODE_MEDIA=1 -- Cache all media entries instead of only your assigned shardsFull-node mode does NOT affect PSBT shard distribution. PSBT shards are always distributed via the Shamir 3-of-4 scheme to specific shard-holder nodes regardless of full-node settings.
Full-node mode increases storage requirements significantly but improves data availability and query performance for your node's users.
The repository includes Docker Compose profiles for different deployment scenarios:
| Profile | What it starts |
|---|---|
infra | PostgreSQL + Redis only (for local development against existing code) |
full | PostgreSQL + Redis + Node app + Rust node-core (complete node) |
gateway | Front-door-gateway (stateless edge proxy, depends on cache only) |
For local development and testing:
# Start the full development environment
pnpm dev
# Start a local multi-node cluster (simulates network locally)
pnpm dev:cluster
# Chain-specific development modes
pnpm dev:btc # Bitcoin-focused development with regtest
pnpm dev:evm # EVM-focused development with local Hardhat/Anvil
pnpm dev:sol # Solana-focused development with local validatorNODE_ANNOUNCE protocol event (Ed25519 signed)The node software is fully open source. You can inspect every line of code, verify every protocol rule, and propose improvements through governance. There is nothing proprietary. The entire marketplace runs on transparent, auditable code. All foundation actions are signed protocol events gossiped to every node and visible in the explorer.