simple-taiko-node v2.4.0

This release prepares Taiko Mainnet nodes for the Unzen upgrade, makes alethia-reth the default execution engine, and upgrades the Go driver and taiko-geth images.

Unzen Mainnet activation

Unzen activates on Taiko Mainnet at:

• Unix timestamp: 1786021200
• UTC: 2026-08-06 13:00:00

Mainnet operators must upgrade before the activation time.

Component upgrades

• Default execution engine: alethia-reth:v1.3.0
• Optional Geth execution engine: taiko-geth:v2.6.0
• Driver: taiko-alethia-client-v2.6.0

Operator-visible changes

• New configurations default to COMPOSE_PROFILES=reth_execution_engine.
• To continue using taiko-geth, set COMPOSE_PROFILES=geth_execution_engine.
• The former l2_execution_engine profile is no longer available. Existing .env files using it must be updated before restart.
• TAIKO_INBOX_ADDRESS changes to the Unzen inbox: 0x6f21C543a4aF5189eBdb0723827577e1EF57ef1f. Run script/util/update-env.sh or update the value manually.
• Add L2_RETH_DATA_DIR for using a local alethia-reth snapshot or data directory, and expose discv5 discovery on PORT_L2_EXECUTION_ENGINE_DISCOVERY (default 9200).
• Align driver startup with Unzen by using --inbox, removing the legacy fork-time and preconfirmation-whitelist settings, and sharing the execution-engine JWT with preconfirmations.

Upgrade notes

1. Pull the v2.4.0 configuration.
2. Update the existing .env, especially COMPOSE_PROFILES and TAIKO_INBOX_ADDRESS.
3. If switching from taiko-geth to alethia-reth, start from an alethia-reth snapshot or allow the new execution engine to sync before the Unzen activation time.

Full changelog: v2.3.2...v2.4.0