For the complete documentation index, see llms.txt.
Skip to main content
Version: Testnet (v6.0.0-rc.1)

Changelog

Overview​

This changelog documents all configuration changes, new features, and breaking changes across Aztec node versions. Each version has a dedicated page with detailed migration instructions.

Version history​

v6.0.0​

Hard fork: a complete new deployment from genesis. Every artifact location moved, and the executor configuration was renamed with no fallback.

Key changes:

  • New locations for everything: azteclabs/aztec on DockerHub, @aztec-labs/* and @aztec-foundation/* on npm, aztec-labs-eng/aztec-node for source
  • ACVM_* configuration renamed to NOIR_EXECUTE_*, with no fallback. A real-proving node fails to start on the old names; one without real proofs starts anyway on slow WASM simulation, so a clean startup does not prove the config migrated
  • Attester-initiated sequencer exits, including batched exits for operators running many delegations. Live on the rollup now; the CLI wrappers arrive in v6.0.0 stable, so for rc.1 call the contract directly
  • New RPC methods: aztec_getTxEffectMembershipWitness, aztec_getValidatorStatsBatch
  • v6.0.0-rc.1 is Testnet only; Mainnet's first v6 release will be v6.0.0 stable

Migration difficulty: High

View full changelog →

v5.2.0​

Node-operator hardening release: peerless nodes stop acting, slashing votes against your own validators are surfaced, and the RPC server gains timeout and CORS configuration.

Key changes:

  • A node whose p2p service fails to start now exits instead of running peerless
  • A peerless node warns periodically, skips proposing, and rejects incoming transactions
  • Logs and metrics when the network votes to slash your own validators
  • L1 event watching moved from server-side filters to bounded eth_getLogs polling
  • New settings: SEQ_MIN_PEERS_TO_PROPOSE, P2P_HEALTH_MIN_PEERS, GOVERNANCE_PROPOSER_FORCE_PAYLOAD_VOTE, RPC_HTTP_KEEP_ALIVE_TIMEOUT_MS, RPC_HTTP_HEADERS_TIMEOUT_MS, RPC_CORS_ALLOWED_HEADERS, RPC_CORS_ALLOWED_ORIGINS, RPC_CORS_ALLOW_ANY_ORIGIN (all defaults preserve previous behaviour)

Migration difficulty: Low

View full changelog →

v4.3.x​

Bundled binaries renamed under an aztec- prefix on PATH. v4.3.1 is a bug-fix release.

Key changes:

  • aztec-up no longer places bare-named binaries (forge, cast, nargo, bb, pxe, txe, validator-client, blob-client, ...) on PATH; use the aztec- prefixed names instead
  • v4.3.1: fixes a block-stream error loop after finalization, prover proof-submission ordering, and released contract artifact version stamping

Migration difficulty: Low

View full changelog →

v4.2.0​

New features and configuration options for node operators.

Key changes:

  • Blob retrieval improvements with unified retry loop

Migration difficulty: Low

View full changelog →

v4.x (Upgrade from Ignition)​

Major upgrade from Ignition (v2.x) to Alpha (v4.x) with significant architectural changes.

Key changes:

  • Checkpoint-based block architecture (multiple L2 blocks per slot)
  • Blob-only data publication (EIP-4844), calldata fallback removed
  • Double signing slashing infrastructure
  • HA signing with PostgreSQL for redundant sequencer nodes
  • Admin API key authentication
  • Sequencer environment variable renames
  • Withdrawal delay increase (7 to 30 days)

Migration difficulty: High

View full changelog →

v2.0.2 (from v1.2.1)​

Major release with significant configuration simplification, keystore integration, and feature updates.

Key changes:

  • Simplified L1 contract address configuration (registry-only)
  • Integrated keystore system for key management
  • Removed component-specific settings in favor of global configuration
  • Enhanced P2P transaction collection capabilities
  • New invalidation controls for sequencers

Migration difficulty: Moderate to High

View full changelog →

Migration guides​

When upgrading between versions:

  1. Review the version-specific changelog for breaking changes
  2. Follow the migration checklist for your node type
  3. Test in a non-production environment first
  4. Check the troubleshooting section for common upgrade issues
  5. Join Aztec Discord for upgrade support