Skip to main content

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.

Network Technical Information

ParameterIgnition (Mainnet)TestnetDevnet
Version2.1.113.0.34.0.0-devnet.2-patch.0
L1 Chain ID1 (Mainnet)11155111 (Sepolia)11155111 (Sepolia)
Rollup Version02500495677615022430
RPC EndpointN/Ahttps://rpc.testnet.aztec-labs.comhttps://v4-devnet-2.aztec-labs.com/
Bootnodeshttp://static.aztec.network/mainnet/bootnodes.jsonhttp://static.aztec.network/testnet/bootnodes.jsonN/A
Block ExplorerAztecscan, AztecexplorerAztecscan, AztecexplorerAztecscan, Aztecexplorer
Getting StartedRun a sequencer →Run a node →Build on Devnet →

Contract Addresses

L1 Contract Addresses

Contract NameIgnition (Mainnet)TestnetDevnet
Registry0x35b22e09ee0390539439e24f06da43d83f90e2980xa0bfb1b494fb49041e5c6e8c2c1be09cd171c6ba0x52945c29d2788ccb076e910509c0449bfcbe29e6
Rollup0x603bb2c05d474794ea97805e8de69bccfb3bca120x66a41cb55f9a1e38a45a2ac8685f12a61fbfab770xcd1a7be18501092f3ba8d80ce5629501ba178de0
L1 → L2 Inbox0x15c718c05b8c0dbec4d648b6711d6ce8793969ee0x59f588603d55a45dd3e57d50403c7c359a39bfc90xef5730d1e07b306aecbe01400630d61e3ccb68af
L2 → L1 Outbox0xf006c41097861afeb18b05e586b921c081411ee90x5fe98f5a4de64f7b5920b038cd32937ca30bab320x34fc558b6f97e50149bcc140060bbe3f7d04bc59
Fee Juice0xa27ec0006e59f245217ff08cd52a7e8b169e62d20x762c132040fda6183066fa3b14d985ee55aa3c180x35d0186d1fd53b72996475d965c5ed171d52b986
Staking Asset0xa27ec0006e59f245217ff08cd52a7e8b169e62d20x5595cb9ed193cac2c0bc5393313bc6115817954b0x4263376b0d7d0ac46d38b76af4cf8bf93844bc14
Fee Juice Portal0xe05dc9d5969272831757181fff1532b066254bf10x4fc4ec3f09b77b20ea5d995261c4bef45a2c4d6d0x516e3f74fd1c19b24da0706d28b5a30578f054ab
Fee Asset HandlerN/A0x5602c39a6e9c5ace589f64f754927bcda4f4bfc90xed9c5557d2e0abcc7c7fca958ee4292199413494
Coin Issuer0x02fadf157d551aa6d761b2a2237d03af68e41ca60xe05d0a62045b4237556c1ec423e59eea9a24eaee0xc0dcff65de33fe19a95f67ed1b7b9e7bd0a23f5f
Reward Distributor0x3d6a1b00c830c5f278fc5dfb3f6ff0b74db6dfe00x030d2780e70f085c31d490268d3900d4cea166060x51f13e2131d28c44f9df33a8d0ff0a897eb52eda
Reward Booster0x7101a6703491a4d808aeabe9f62bc1dc6a20bdf40x5b6337eddb91e7c1a05de0de26b087ece35b8dc8
Governance Proposer0x06ef1dcf87e419c48b94a331b252819fadbd63ef0x01c7d4ca153748d2377968fef22894cb162e94800x17f54a1448387de40120f8a2f9949a68a9185c8b
Governance0x1102471eb3378fee427121c9efcea452e4b6b75e0xcaf7447721447b22cd0076ac7c63877c3afd329f0xfaa29a00987bb2d2ec703edac5ebb24f1ee9de97
Governance Staking Escrow0xa92ecfd0e70c9cd5e5cd76c50af0f7da93567a4f0xb6a38a51a6c1de9012f9d8ea9745ef957212eaac0x5f966c3cbbc12569690ca4250b37bf17fc1b3013
Staking Registry0x042dF8f42790d6943F41C25C2132400fd727f4520xC6EcC1832c8BF6a41c927BEb4E9ec610FBeDd1C2
Slash FactoryN/A0xaa34b2929dbf3f0a9f1df015cd26798d5fc557640xd4248cbb1fa7228f49b9d314237cde7b2d0f3470
Slasher0x91a3745c685c220595b997e53311ebf6601448890x89684502e6a5fd3f1e4b3c610429f6e2c181c6ba
Tally Slashing Proposer0x7a318c3daa9f21f8fc8238c65755eb0394fbf1890xca49e32bc2926c3f2ef67e1647fa14a8ebf34065

L2 Contract Addresses

Contract NameIgnition (Mainnet)TestnetDevnet
Instance RegistryN/A0x00000000000000000000000000000000000000000000000000000000000000020x0000000000000000000000000000000000000000000000000000000000000002
Class RegistryN/A0x00000000000000000000000000000000000000000000000000000000000000030x0000000000000000000000000000000000000000000000000000000000000003
MultiCall EntrypointN/A0x00000000000000000000000000000000000000000000000000000000000000040x0000000000000000000000000000000000000000000000000000000000000004
Fee JuiceN/A0x00000000000000000000000000000000000000000000000000000000000000050x0000000000000000000000000000000000000000000000000000000000000005
SponsoredFPCN/A0x1586f476995be97f07ebd415340a14be48dc28c6c661cc6bdddb80ae790caa4e0x09a4df73aa47f82531a038d1d51abfc85b27665c4b7ca751e2d4fa9f19caffb2

Governance Parameters

ParameterIgnition (Mainnet)TestnetDevnet
Proposer Quorum600/100060/100N/A
Voting Delay3 days12 hoursN/A
Voting Duration7 days24 hoursN/A
Execution Delay7 days12 hoursN/A
Slashing Quorum65%33%N/A
Slashing Round Size128 epochs64 epochsN/A

Use Case Suitability

Use CaseIgnition (Mainnet)TestnetDevnet
App Development✅ Recommended
Sequencer Testing
Governance Testing

Network Selection Guide

Ignition (Mainnet - Phase 1)

Ignition is the Aztec mainnet in its first operational phase, focusing on establishing governance and network infrastructure.

Overview

Ignition is currently configured with a gas limit of 0, meaning no user transactions are being executed. However, governance and networking infrastructure are fully active and being tested. This network is connected to Ethereum mainnet and requires real stakes for participation.

Target Users:

  • Validators who want to contribute to the decentralized Aztec Network
  • Governance participants
  • Infrastructure operators preparing for full mainnet

Key Features:

  • Governance system fully operational
  • Staking required for sequencer participation
  • Connected to Ethereum Mainnet
  • No user transaction execution

Testnet

The Aztec Testnet provides a decentralized testing environment that closely mirrors production conditions.

Overview

Testnet operates as a fully decentralized network with multiple sequencers. This network is ideal for testing node configurations, governance proposals, and understanding network dynamics without real financial risk.

Target Users:

  • Future mainnet 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
  • Longer resolution times for features and bugs
  • Good environment for testing node operations
info

App developers can deploy on Testnet for production-like testing. For faster iteration cycles, consider using Devnet.


Devnet

Devnet provides the most developer-friendly environment for building applications on Aztec.

Overview

Devnet is a centralized network operated by Aztec Labs, designed for rapid development and testing. It offers the latest Aztec package versions and quick iteration cycles, making it ideal for application developers.

Target Users:

  • Application developers building on Aztec
  • Teams testing smart contracts and dApps
  • Developers learning Aztec development

Key Features:

  • Centralized sequencer
  • Latest package versions available first
  • Fast bug fixes and feature updates

Next Steps

Based on your use case: