The architecture also includes a safety override. ZK proofs override TEE proofs if the two systems produce conflicting results. Any contradiction automatically triggers a soundness alert that disables the associated prover, ensuring the chain can detect and handle proof system bugs onchain without relying on a privileged security council . This onchain fault-detection capability is a core technical requirement for Stage 2 decentralization.
Azul consolidates Base onto a single execution client—base-reth-node—paired with a single consensus client, base-consensus. Nodes running legacy OP Stack clients such as op-geth, op-reth, nethermind, or kona no longer support the network and required migration before activation . This unified approach simplifies node operations and improves performance.
Performance gains were visible even before mainnet activation. Over the two months leading up to launch, the Base network reduced the number of empty blocks by approximately 99%, from an average of roughly 200 per day to about two per day . During the same period, the network sustained multiple bursts of 5,000 transactions per second
.
The upgrade also aligns Base with Ethereum's latest execution-layer specification, Osaka, including EIP-7825, which introduces a per-transaction gas cap of approximately 17 million gas . This keeps Base compatible with Ethereum's evolving standards while it continues to operate as an independent Layer 2.
The Azul upgrade is more than a performance improvement. By activating multiproofs and adopting a fully independent client stack, Base has taken its biggest single step toward Stage 2 decentralization. The ability to detect proof-system faults onchain without a security council intervention, combined with faster withdrawal finality and a simplified node architecture, positions Base to compete more aggressively in the Layer 2 landscape.
Comments
0 comments