Skip to content
BaseHub by wbnns Updated

Azul Upgrade Overview

Azul is the first Base-specific hardfork. It folds Osaka-era EVM changes onto the Base execution layer, trims the Flashblocks websocket payload, and turns on a multi-proof system that shortens withdrawal latency and lays the groundwork for stronger decentralization. It also drops support for non-Base clients.

What Azul ships

Section titled “What Azul ships”
  • Osaka EVM support on Base.
  • A simplified Flashblocks websocket message format.
  • A multi-proof system that unlocks faster withdrawals and a credible path toward decentralization.
  • Base-native clients (base-reth-node + base-consensus) as the only supported stack.

Activation timestamps

Section titled “Activation timestamps”
NetworkActivation timestamp
mainnet1779991200 (2026-05-28 18:00:00 UTC)
sepolia1776708000 (2026-04-20 18:00:00 UTC)

Both timestamps are now confirmed: Azul shipped to Sepolia first and activated on mainnet on 2026-05-28. Operators who have not yet moved to the Base-native stack should follow the Azul node upgrade guide to stay on the chain.

Required software

Section titled “Required software”
LayerSoftwareMainnetSepolia
Execution (EL)base-reth-nodev0.9.0+v0.7.0+
Consensus (CL)base-consensusv0.9.0+v0.7.0+
-base/nodev0.16.0+v0.15.0+

Execution layer changes

Section titled “Execution layer changes”

The Azul execution engine page covers each of these in full; the list below links straight to the relevant section:

Proof system

Section titled “Proof system”

Azul introduces the components that make multi-proof withdrawals possible. The Azul proof system page covers the design in full — the AggregateVerifier dispute game, the TEE and ZK proof paths, and the finality windows. The individual roles are documented separately: