For the complete documentation index, see llms.txt.
Skip to main content

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​

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