For the complete documentation index, see llms.txt.
Skip to main content

Run a Node

Aztec is a permissionless network. Anyone can sync a node, propose blocks, or generate proofs. Pick the role that fits what you want to do, and the docs will walk you through it.

No stake

Full node

Sync the chain. Read state. Submit txs. Foundation for every other role.

Stake
None
Hardware
8 core / 8 GB / 1 TB
Reliability
24/7 uptime, stable connection
Earns
No rewards
Slashing
No
  • Trustless local source of network data
  • Useful for app developers, indexers, and explorers
  • No on-chain registration required
Read setup guide →
Own stake only

Solo sequencer

Run a sequencer with your own stake. Earn rewards, attest blocks, signal governance.

Stake
200,000 AZTEC
Hardware
8 core / 8 GB / 1 TB
Reliability
24/7 uptime, stable connection
Earns
Block rewards
Slashing
Yes (own stake)
  • Self-custodied stake
  • Guided playbook walks you from blank server to attesting
  • Personalised commands: paste keys / RPCs once, every step auto-fills
Start guided setup →
For pros

Staking provider

Run sequencers on behalf of delegators. Manage keys, commission, reward distribution.

Stake
From delegators
Hardware
8 core / 8 GB / 1 TB per node
Reliability
24/7 uptime, stable connection
Earns
Commission
Slashing
Yes (delegator stake)
  • Accept delegated stake from token holders
  • Earn a commission percentage on rewards you produce
  • Adds key-management and commission-tooling complexity
Start guided setup →
Heavy compute

Prover

Generate cryptographic proofs for L2 epochs. Different hardware profile and economics from sequencers.

Stake
None
Hardware
32+ core / 128+ GB
Reliability
Available during proving
Earns
Proof rewards
Slashing
No
  • Generates the epoch-level proofs the rollup posts to L1
  • CPU + RAM heavy
  • Earnings depend on epoch activity, gas, and prover-pool competition
Read setup guide →

Identity model

Which keys earn rewards, which are slashable, which can be rotated

Read more →

L1 RPC requirements

Supernode flags, hosted vs self-hosted, polling tuning

Read more →

Hardware spec

Per-role minimums plus the operator-community gotchas

Read more →

Claiming rewards

Where rewards live, when they show up, the multi-rollup case

Read more →

Slashing

What gets you slashed, thresholds, the veto council, recovery

Read more →

Monitoring and metrics

The five metrics that matter and what to alert on

Read more →

What comes after picking a role​

  • The guided setup is opinionated and personalized: paste your RPC URLs and keys once, every command on every page auto-fills with your values.
  • The advanced operations section in the sidebar covers everything the playbook doesn't: high-availability topologies, deep keystore management, monitoring stack, governance signalling, provider tooling.
  • The reference section is for when you know what you're looking for: CLI flags, env vars, JSON-RPC, the Ethereum-RPC requirements.