Skip to main content
Version: Testnet (v3.0.3)

v4.0.0 (from v3.0.0)

Overview​

Migration difficulty: TODO

Breaking changes​

Node.js upgraded to v24​

Node.js minimum version changed from v22 to v24.12.0.

Bot fee padding configuration renamed​

The bot configuration for fee padding has been renamed from "base fee" to "min fee".

v3.x:

--bot.baseFeePadding <value>          ($BOT_BASE_FEE_PADDING)

v4.0.0:

--bot.minFeePadding <value>           ($BOT_MIN_FEE_PADDING)

Migration: Update your configuration to use the new flag name and environment variable.

L2Tips API restructured with checkpoint information​

The getL2Tips() RPC endpoint now returns a restructured response with additional checkpoint tracking.

v3.x response:

{
  "latest": { "number": 100, "hash": "0x..." },
  "proven": { "number": 98, "hash": "0x..." },
  "finalized": { "number": 95, "hash": "0x..." }
}

v4.0.0 response:

{
  "proposed": { "number": 100, "hash": "0x..." },
  "checkpointed": {
    "block": { "number": 99, "hash": "0x..." },
    "checkpoint": { "number": 10, "hash": "0x..." }
  },
  "proven": {
    "block": { "number": 98, "hash": "0x..." },
    "checkpoint": { "number": 9, "hash": "0x..." }
  },
  "finalized": {
    "block": { "number": 95, "hash": "0x..." },
    "checkpoint": { "number": 8, "hash": "0x..." }
  }
}

Migration:

  • Replace tips.latest with tips.proposed
  • For checkpointed, proven, and finalized tips, access block info via .block (e.g., tips.proven.block.number)

Removed features​

New features​

Initial ETH per fee asset configuration​

A new environment variable AZTEC_INITIAL_ETH_PER_FEE_ASSET has been added to configure the initial exchange rate between ETH and the fee asset (AZTEC) at contract deployment. This value uses 1e12 precision.

Default: 10000000 (0.00001 ETH per AZTEC)

Configuration:

--initialEthPerFeeAsset <value>       ($AZTEC_INITIAL_ETH_PER_FEE_ASSET)

This replaces the previous hardcoded default and allows network operators to set the starting price point for the fee asset.

Changed defaults​

Troubleshooting​

Next steps​