> For the complete documentation index, see [llms.txt](/llms.txt) # Run a Node Aztec is a permissionless, decentralized network with no centralized sequencer. 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](/operate/operators/full-node/overview.md) ### [Full node](/operate/operators/full-node/overview.md) [Sync the chain. Read state. Submit txs. Foundation for every other role.](/operate/operators/full-node/overview.md) [* Stake None* Hardware 8 core / 8 GB / 1 TB* Reliability 24/7 uptime, stable connection* Earns No rewards* Slashing No](/operate/operators/full-node/overview.md) [- Trustless local source of network data- Useful for app developers, indexers, and explorers- No on-chain registration required](/operate/operators/full-node/overview.md) [Read setup guide](/operate/operators/full-node/overview.md) [ →](/operate/operators/full-node/overview.md) [Own stake only](/operate/operators/solo-sequencer.md) ### [Solo sequencer](/operate/operators/solo-sequencer.md) [Run a sequencer with your own stake. Earn rewards, attest blocks, signal governance.](/operate/operators/solo-sequencer.md) [* Stake 200,000 AZTEC* Hardware 8 core / 8 GB / 1 TB* Reliability 24/7 uptime, stable connection* Earns Block rewards* Slashing Yes (own stake)](/operate/operators/solo-sequencer.md) [- Self-custodied stake- Guided playbook walks you from blank server to attesting- Personalised commands: paste keys / RPCs once, every step auto-fills](/operate/operators/solo-sequencer.md) [Start guided setup](/operate/operators/solo-sequencer.md) [ →](/operate/operators/solo-sequencer.md) [For pros](/operate/operators/provider.md) ### [Staking provider](/operate/operators/provider.md) [Run sequencers on behalf of delegators. Manage keys, commission, reward distribution.](/operate/operators/provider.md) [* Stake From delegators* Hardware 8 core / 8 GB / 1 TB per node* Reliability 24/7 uptime, stable connection* Earns Commission* Slashing Yes (delegator stake)](/operate/operators/provider.md) [- Accept delegated stake from token holders- Earn a commission percentage on rewards you produce- Adds key-management and commission-tooling complexity](/operate/operators/provider.md) [Start guided setup](/operate/operators/provider.md) [ →](/operate/operators/provider.md) [Heavy compute](/operate/operators/prover/overview.md) ### [Prover](/operate/operators/prover/overview.md) [Generate cryptographic proofs for L2 epochs. Different hardware profile and economics from sequencers.](/operate/operators/prover/overview.md) [* Stake None* Hardware 32+ core / 128+ GB* Reliability Available during proving* Earns Proof rewards* Slashing No](/operate/operators/prover/overview.md) [- Generates the epoch-level proofs the rollup posts to L1- CPU + RAM heavy- Earnings depend on epoch activity, gas, and prover-pool competition](/operate/operators/prover/overview.md) [Read setup guide](/operate/operators/prover/overview.md) [ →](/operate/operators/prover/overview.md) ## Popular questions ### [Identity model](/operate/operators/concepts/identity-model.md) [Which keys earn rewards, which are slashable, which can be rotated](/operate/operators/concepts/identity-model.md) [Read more →](/operate/operators/concepts/identity-model.md) ### [L1 RPC requirements](/operate/operators/concepts/l1-rpc.md) [Supernode flags, hosted vs self-hosted, polling tuning](/operate/operators/concepts/l1-rpc.md) [Read more →](/operate/operators/concepts/l1-rpc.md) ### [Hardware spec](/operate/operators/concepts/hardware.md) [Per-role minimums plus the operator-community gotchas](/operate/operators/concepts/hardware.md) [Read more →](/operate/operators/concepts/hardware.md) ### [Claiming rewards](/operate/operators/concepts/claiming-rewards.md) [Where rewards live, when they show up, the multi-rollup case](/operate/operators/concepts/claiming-rewards.md) [Read more →](/operate/operators/concepts/claiming-rewards.md) ### [Slashing](/operate/operators/concepts/slashing.md) [What gets you slashed, thresholds, the veto council, recovery](/operate/operators/concepts/slashing.md) [Read more →](/operate/operators/concepts/slashing.md) ### [Monitoring and metrics](/operate/operators/concepts/monitoring.md) [The five metrics that matter and what to alert on](/operate/operators/concepts/monitoring.md) [Read more →](/operate/operators/concepts/monitoring.md) ## 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. ## Using these docs with an AI assistant These docs are published in a machine-readable form, so you can hand them to an AI assistant instead of copying pages by hand. * `llms.txt` at [docs.aztec.network/llms.txt](https://docs.aztec.network/llms.txt) is an index of every page. `llms-full.txt` is the whole site as a single file. * The **Copy page** button at the top of each page copies that page as markdown, ready to paste into a chat. * Append `.md` to any docs URL to fetch the markdown source of that page. * The [AI Tooling guide](/developers/ai_tooling.md) covers the Aztec MCP server and project instruction files for tools like Claude Code, Cursor, and Codex. Always verify commands, addresses, and version numbers against these docs before you run them on a live node. An assistant can read the docs, but it cannot see your setup.