Aztec Networks Overview
The Aztec Protocol operates across multiple networks, each serving specific purposes and audiences. This guide provides essential technical information for connecting to each network.
Not sure which network to use? Jump to our Network Selection Guide.
The developer SDK/aztec-nr version (used for writing and compiling contracts) may differ from the node version listed below. Use the version from the developer docs for contract development — use the version below for running nodes.
Network Technical Information
| Parameter | Alpha (Mainnet) | Testnet |
|---|---|---|
| Version | 4.3.0 | 4.3.0 |
| L1 Chain ID | 1 (Mainnet) | 11155111 (Sepolia) |
| Rollup Version | 2934756905 | 4127419662 |
| RPC Endpoint | https://aztec-mainnet.drpc.org | https://rpc.testnet.aztec-labs.com |
| Bootnodes | http://static.aztec.network/mainnet/bootnodes.json | http://static.aztec.network/testnet/bootnodes.json |
| Block Explorer | Aztecscan, Aztecexplorer | Aztecscan, Aztecexplorer |
| Getting Started | Run a sequencer → | Run a node → |
Testnet is your production path. It's decentralized, live, and stable — treat it as your staging environment for Alpha. If you want to deploy on Alpha, validate on Testnet first.
Contract Addresses
L1 Contract Addresses
L2 Contract Addresses
| Contract Name | Alpha (Mainnet) | Testnet |
|---|---|---|
| Instance Registry | 0x0000000000000000000000000000000000000000000000000000000000000002 | 0x0000000000000000000000000000000000000000000000000000000000000002 |
| Class Registry | 0x0000000000000000000000000000000000000000000000000000000000000003 | 0x0000000000000000000000000000000000000000000000000000000000000003 |
| MultiCall Entrypoint | 0x0000000000000000000000000000000000000000000000000000000000000004 | 0x0000000000000000000000000000000000000000000000000000000000000004 |
| Fee Juice | 0x0000000000000000000000000000000000000000000000000000000000000005 | 0x0000000000000000000000000000000000000000000000000000000000000005 |
| SponsoredFPC | Not deployed | 0x254082b62f9108d044b8998f212bb145619d91bfcd049461d74babb840181257 |
Governance Parameters
| Parameter | Alpha (Mainnet) | Testnet |
|---|---|---|
| Proposer Quorum | 600/1000 | 60/100 |
| Voting Delay | 3 days | 12 hours |
| Voting Duration | 7 days | 24 hours |
| Execution Delay | 30 days | 12 hours |
| Slashing Quorum | 65% | 33% |
| Slashing Round Size | 128 epochs | 64 epochs |
Network Selection Guide
Alpha (Mainnet)
Alpha is the Aztec mainnet in its initial operational phase, with governance, networking, and transaction processing fully active. Alpha is live but early — bugs, including critical ones, are expected. For a full explanation of what this means, see the Alpha Network page.
Overview
Alpha is connected to Ethereum mainnet and supports user transactions. Governance and staking infrastructure are fully operational. This network requires real stakes for sequencer participation.
Target Users:
- Validators who want to contribute to the decentralized Aztec Network
- Governance participants
- Developers deploying production applications
- Infrastructure operators
Key Features:
- Governance system fully operational
- Staking required for sequencer participation
- Connected to Ethereum Mainnet
- User transactions supported
Testnet
Testnet is the production path for Aztec. It operates as a fully decentralized network with multiple sequencers and closely mirrors Alpha conditions. If you plan to deploy on Alpha, Testnet is where you validate your application. Think of it as your staging environment for the real thing.
Overview
Testnet is ideal for testing node configurations, governance proposals, and understanding network dynamics without real financial risk.
Target Users:
- Future Alpha sequencer operators testing configurations
- Developers requiring production-like testing conditions
- Governance participants practicing proposal workflows
- Infrastructure operators validating monitoring setups
Key Features:
- Fully decentralized sequencer set
- Connected to Ethereum Sepolia
- Transactions are proven
- Sponsored FPC available for free transactions
- Good environment for testing node operations
Next Steps
Based on your use case:
- Building an application? Start with Getting Started
- Running infrastructure? Review Network Operator Guide
- Joining as validator? See Sequencer Management