DocsValidator guide

Validator guide

How to operate a W3AI compute node, stake collateral, and earn from served intents.

Requirements

CPU8 vCPU minimum (16+ recommended for parallel capsules).
RAM32 GB minimum.
GPUOptional — required only for scopes declaring on-host inference.
Network1 Gbps symmetric; p50 latency to Solana RPC < 100 ms.
Storage200 GB NVMe for capsule snapshots and receipt logs.
StakeMinimum 25,000 W3AI per capability tier.

Install

bash
curl -fsSL https://get.w3ai.run | bash
w3ai-node init --keypair ./operator.json
w3ai-node config set rpc https://api.mainnet-beta.solana.com

Stake & registration

  1. 1
    Fund the operator key
    Send the minimum stake in W3AI plus a small SOL balance for fees.
  2. 2
    Stake collateral
    Run w3ai-node stake --amount <n>. Funds are locked in the Staking program.
  3. 3
    Register capabilities
    Declare the scopes you serve. Each tier requires a stake floor.
  4. 4
    Start the node
    w3ai-node start. The Registry begins routing intents within ~1 epoch.

Declaring capabilities

toml
# capabilities.toml
[net]
hosts = ["jupiter.ag", "orca.so", "api.pyth.network"]

[wallet]
sign = true             # operator may request user signatures

[chain]
write = true            # operator may broadcast signed txs

[llm]
provider = "local"      # use on-host inference for llm:call
Capability tiers
Higher-impact scopes (chain:write, wallet:sign) require larger stake floors and are subject to harsher slashing.

Operating the node

HealthGET /health — returns uptime, p50/p95 latency, and active capsule count.
MetricsPrometheus endpoint on :9090.
LogsStructured JSON to stdout; rotate via your supervisor of choice.
Upgradesw3ai-node upgrade — staged rollout aligned to protocol epochs.

Monitoring checklist

Slashing alertsWebhook on any sim-mismatch or scope-violation event.
Stake marginAlert when collateral approaches the floor of any declared scope.
RPC latencyAlert on p95 > 250 ms — affects routing rank.
DiskAlert at 80% — snapshot pruning runs at 90%.

Earnings

Operators earn 60% of every settled fee. Delegators of the operator earn an additional 20% share. Treasury and burn take the remaining 20%. Earnings are paid in W3AI and routed by the Settlement program at the moment of settlement — no claim transaction required.

Slashing conditions

Simulation mismatch10% slash; receipt voided.
Forged receipt100% slash; operator deregistered.
Scope violation25% slash; capability tag revoked.
Sustained liveness failureSoft slash + reputation decay; eventual deregistration.