Skip to content

docs(networks): add versions and releases section #23319

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
AztecBot wants to merge 1 commit into
base: next
Choose a base branch
from
+64 −25
Draft

docs(networks): add versions and releases section #23319

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/docs-words.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -281,6 +281,7 @@ rustc
sendl
SENDL
serde
serializability
Shamir
sharedsecret
shcedule
Expand Down Expand Up @@ -438,3 +439,4 @@ reentrancy
variadic
Wonderland
indistinguishability
nightlies
87 changes: 62 additions & 25 deletions docs/docs/networks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,20 +2,16 @@
title: Networks
keywords: [Aztec, Networks, Alpha, Testnet, Mainnet]
id: networks
description: "Connect to Aztec Networks: Alpha (Mainnet) and Testnet — choose the right network for your use case."
description: "Connect to Aztec Networks: Alpha (Mainnet) and Testnet, choose the right network for your use case, and find the version each network is running."
---

# Aztec Networks Overview
# 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.
The Aztec Protocol operates across multiple networks, each serving specific purposes and audiences. This page gives builders and node operators the technical details to connect to each network: live version, RPC and bootnode endpoints, contract addresses, and governance parameters.

Not sure which network to use? Jump to our [Network Selection Guide](#network-selection-guide).
Not sure which network or version to pin against? Jump to the [Network selection guide](#network-selection-guide). For release channels and what is coming next, see [Versions and releases](#versions-and-releases).

:::note Developer SDK vs Node Versions
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
## Network technical information

| Parameter | Alpha (Mainnet) | Testnet |
|-----------|-------------------|---------|
Expand All @@ -27,13 +23,45 @@ The developer SDK/aztec-nr version (used for writing and compiling contracts) ma
| **Block Explorer** | [Aztecscan](https://aztecscan.xyz), [Aztecexplorer](https://aztecexplorer.xyz/?network=mainnet) | [Aztecscan](https://testnet.aztecscan.xyz), [Aztecexplorer](https://aztecexplorer.xyz/?network=testnet) |
| **Getting Started** | [Run a sequencer →](/operate/operators/setup/sequencer_management) | [Run a node →](/operate/operators/setup/running_a_node) |

:::tip Network Roles (Post-Alpha)
**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.
:::tip Network roles (post-Alpha)
**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
## Versions and releases

Aztec is a monorepo. Each release publishes a single version that covers the node, [Aztec.nr](https://aztec.network/aztecnr), and [aztec.js](https://aztec.network/aztecjs) together, so a network on `4.2.0` runs the `4.2.0` node, contracts compiled with the `4.2.0` Aztec.nr, and clients built against the `4.2.0` aztec.js. The **Version** row in the table above is the build a given network is currently running.

### Release channels

Aztec publishes three kinds of builds, each with a different stability promise.

| Channel | Example | What it is | Recommended audience |
|---------|---------|------------|----------------------|
| **Stable** | `4.2.0`, `4.3.0` | The validated, final version for a release cycle. | Builders shipping to users. Operators running Alpha or Testnet. |
| **Release candidate (RC)** | `4.3.0-rc.1`, `4.3.0-rc.2` | Pre-release of an upcoming stable, used for internal validation and Testnet rehearsals. Additional RCs ship if issues are found. | Operators participating in pre-release rehearsals. Builders verifying compatibility ahead of a stable cut. |
| **Nightly** | `4.3.0-nightly.<date>` | Latest in-progress work from the development branch. Experimental, less tested. | Builders previewing upcoming features. Not recommended for production. |

An RC is not newer than its matching stable: `4.3.0-rc.1` is a checkpoint on the way to `4.3.0`, and `4.3.0` supersedes every `4.3.0-rc.*`.

Release notes for each version are generated from the commit range since the previous release and published on the [GitHub releases page](https://github.com/AztecProtocol/aztec-packages/releases). The Git history is the source of truth for what changed between two versions.

### Cadence

### L1 Contract Addresses
Stable releases target roughly one per month, typically mid-month. Dates are not strictly fixed; the cadence is intended to be regular rather than ad hoc.

### Coming next: `v4.3.0-rc.1`

[`v4.3.0-rc.1`](https://github.com/AztecProtocol/aztec-packages/releases/tag/v4.3.0-rc.1) is the first release candidate for the v4.3 line. Focus areas:

- **PXE / wallet:** new opt-in SQLite-on-WASM kv-store backend (on track to become the default in v5), execution hooks for cross-contract utility-call authorization, and a series of sync-performance refactors.
- **Aztec.nr / TXE:** TXE oracle versioning and basic gas settings, a handshake registry contract for offchain message delivery, `call_self` utility stubs, and serializability assertions on contract function signatures.
- **CLI:** `aztec init` / `aztec new` scaffold a 2-crate workspace using a counter template by default; contract artifacts are stamped with the `aztec` version they were compiled against; `aztec profile gates` supports `--json`.

Two breaking changes ship in this RC: the new `aztec init` / `aztec new` scaffold, and shared protocol-circuit utilities consumed by the `aztec-nr` history module. Review the [release notes](https://github.com/AztecProtocol/aztec-packages/releases/tag/v4.3.0-rc.1) and [migration notes](https://github.com/AztecProtocol/aztec-packages/blob/next/docs/docs-developers/docs/resources/migration_notes.md) before upgrading.

## Contract addresses

### L1 contract addresses

| Contract Name | Alpha (Mainnet) | Testnet |
|---------------|-------------------|---------|
Expand All @@ -59,7 +87,7 @@ The developer SDK/aztec-nr version (used for writing and compiling contracts) ma
| **Register New Rollup Version Payload** | N/A | [`0x11f7Ab2324CA94af929A388477a7959E0108C3d6`](https://sepolia.etherscan.io/address/0x11f7Ab2324CA94af929A388477a7959E0108C3d6) |
| **Slash Payload Cloneable** | [`0xAA43220b7eb7c8Ffe75bc9C483f3C07b0a55B445`](https://etherscan.io/address/0xAA43220b7eb7c8Ffe75bc9C483f3C07b0a55B445) | [`0xe66d9eeBfF5490E6bfA263cF08028dE7d265321F`](https://sepolia.etherscan.io/address/0xe66d9eeBfF5490E6bfA263cF08028dE7d265321F) |

### L2 Contract Addresses
### L2 contract addresses

| Contract Name | Alpha (Mainnet) | Testnet |
|---------------|-------------------|---------|
Expand All @@ -69,7 +97,7 @@ The developer SDK/aztec-nr version (used for writing and compiling contracts) ma
| **Fee Juice** | `0x0000000000000000000000000000000000000000000000000000000000000005` | `0x0000000000000000000000000000000000000000000000000000000000000005` |
| **SponsoredFPC** | Not deployed | `0x254082b62f9108d044b8998f212bb145619d91bfcd049461d74babb840181257` |

## Governance Parameters
## Governance parameters

| Parameter | Alpha (Mainnet) | Testnet |
|-----------|-------------------|---------|
Expand All @@ -82,23 +110,23 @@ The developer SDK/aztec-nr version (used for writing and compiling contracts) ma

---

## Network Selection Guide
## 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](/participate/alpha)** page.
Alpha is the Aztec **mainnet** in its initial operational phase, with governance, networking, and transaction processing fully active. Alpha is live but early, so bugs (including critical ones) are expected. For a full explanation of what this means, see the **[Alpha Network](/participate/alpha)** 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:**
**Target users:**
- Validators who want to contribute to the decentralized Aztec Network
- Governance participants
- Developers deploying production applications
- Infrastructure operators

**Key Features:**
**Key features:**
- Governance system fully operational
- Staking required for sequencer participation
- Connected to Ethereum Mainnet
Expand All @@ -114,23 +142,32 @@ Testnet is the production path for Aztec. It operates as a fully decentralized n

Testnet is ideal for testing node configurations, governance proposals, and understanding network dynamics without real financial risk.

**Target Users:**
**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:**
**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
### Choosing a version

Once you have picked a network, choose a release channel that matches your role:

- **Building on Aztec.** Pin Aztec.nr and aztec.js to the stable version that matches the network you are targeting (see the **Version** row in the [Network technical information](#network-technical-information) table). Validate on Testnet before deploying to Alpha. Use nightlies only when you need an unreleased feature, and expect breakage.
- **Running a node or sequencer.** Run the stable version listed for your network. Switch to an RC only when an upcoming-release rehearsal is announced on Testnet.
- **Tracking what is coming.** Watch [Releases](https://github.com/AztecProtocol/aztec-packages/releases) for the current stable, any RCs in flight, and nightly tags. A public release calendar is on the roadmap; until then, the releases page is the authoritative timeline.

## Next steps

Based on your use case:

- **Building an application?** Start with [Getting Started](/developers/getting_started_on_local_network)
- **Running infrastructure?** Review [Network Operator Guide](/operate/operators)
- **Joining as validator?** See [Sequencer Management](/operate/operators/setup/sequencer_management)
- **Building an application?** Start with [Getting started](/developers/getting_started_on_local_network).
- **Running infrastructure?** Review the [Network operator guide](/operate/operators).
- **Joining as a validator?** See [Sequencer management](/operate/operators/setup/sequencer_management).
- **Tracking releases?** See [Versions and releases](#versions-and-releases) above and the [GitHub releases page](https://github.com/AztecProtocol/aztec-packages/releases).
Loading