Base has activated Azul on mainnet, marking the network’s first independent upgrade since it began moving toward its own client stack and bringing meaningful changes to how the Coinbase-backed Ethereum layer 2 handles proofs, withdrawals, and node infrastructure. The mainnet activation took place on May 28, 2026, at 18:00 UTC, and introduces a multiproof system combining trusted execution environment proofs and zero-knowledge proofs that Base says can reduce withdrawal finality to as little as one day.
The Base Azul upgrade represents more than a performance improvement. It is a structural step toward the kind of decentralized, independently operated layer 2 that the broader Ethereum ecosystem has been working toward, and it signals that Base is moving past its early dependence on shared OP Stack infrastructure into a more self-determined technical path.
What the Base Azul Upgrade Actually Changes
The centerpiece of the Azul upgrade is its multiproof system. Previously, Base relied on a single proof path to finalize transactions and validate state transitions between Base and Ethereum mainnet. The Azul upgrade introduces two parallel proof mechanisms: trusted execution environment proofs and zero-knowledge proofs. Either proof can finalize a proposal independently, but the system is designed so that when both agree, withdrawals between Base and Ethereum can complete in as little as one day.
That one-day withdrawal target is a significant improvement over the seven-day challenge period that has historically been a feature of optimistic rollup designs. The longer window exists because optimistic rollups assume transactions are valid unless challenged, and challengers need time to detect and dispute fraudulent state transitions. A multiproof system that can achieve rapid finality through cryptographic verification rather than a waiting period changes the user experience meaningfully for anyone moving assets between Base and Ethereum.
The upgrade also includes a conflict resolution mechanism that favors cryptographic security. If a zero-knowledge proof conflicts with a permissioned TEE proof, the ZK proof can override it. That design choice reflects Base’s stated direction toward a final architecture grounded in stronger zero-knowledge proving, with the TEE system serving as a practical intermediate step while ZK infrastructure matures.
The Path Toward Stage 2 Decentralization
The multiproof design is also directly relevant to Base’s decentralization roadmap. Layer 2 networks are typically categorized by their degree of decentralization, with Stage 2 representing a level where the network operates without reliance on a privileged operator for security. Reaching Stage 2 requires, among other things, a proof system that does not depend on a single trusted party to validate state transitions.
By introducing a ZK proof that can override a permissioned TEE proof in cases of conflict, Base is building the technical foundation for reduced operator dependence. The full effect will depend on how the system performs under live network conditions and how Base continues to develop its ZK proving infrastructure in subsequent upgrades. But the Azul upgrade moves the network closer to the decentralization threshold in a concrete and measurable way.
Base has been transparent that this is an intermediate step rather than a final destination. The network has more upgrades planned, and the direction of travel is toward a design based more heavily on zero-knowledge proofs and less on trusted execution environments. Azul establishes the multiproof framework; future upgrades are expected to shift the balance within that framework toward stronger cryptographic guarantees.
Ethereum Osaka Changes and Application Impact
Beyond the proof system, the Base Azul upgrade incorporates Ethereum Osaka execution-layer changes, including the CLZ opcode and associated repricing updates. These changes align Base with the broader Ethereum protocol roadmap and ensure that the network remains compatible with Ethereum tooling and standards as both ecosystems evolve.
Base said most application developers should not need to make significant code changes to accommodate the Azul upgrade. That is an important practical consideration for the ecosystem of developers building on Base, which has grown substantially since the network launched. Minimizing disruption to existing applications while introducing significant infrastructure changes is a difficult balance, and Base’s assessment that most developers are unaffected suggests the upgrade was designed with backward compatibility as a priority.
Node Operators Face Required Migration
While application developers may see minimal disruption, the situation for node operators is more demanding. The Base Azul upgrade moves Base to base-reth-node as its execution client and introduces base-consensus as its consensus client. Critically, several previously supported clients — op-node, op-geth, op-reth, nethermind, and kona — no longer support the Azul upgrade. Node operators running any of these clients must migrate to the Base-native clients to remain in sync with the network.
The migration path varies depending on current infrastructure. Operators already running OP Reth through the Base node package can update without a full re-sync, which reduces the operational burden significantly. Others may need to start fresh with base-reth-node, which is a more involved process. Base documentation covers the migration requirements in detail, and operators who have not yet begun the transition need to act promptly to avoid falling out of sync.
The shift to Base-native clients is itself significant beyond the immediate migration requirement. It represents Base establishing independent infrastructure rather than relying on shared OP Stack components maintained by other teams. That independence gives Base more control over its own development roadmap and reduces its dependency on the broader OP Stack ecosystem for core node software.
Performance Improvements: 5,000 TPS and 99% Fewer Empty Blocks
Base has reported notable performance improvements following the client stack changes that preceded and accompanied the Azul upgrade. The network said the new stack reduced empty blocks by approximately 99 percent, with the count falling from nearly 200 per day to around two. Empty blocks represent wasted network capacity and a poor user experience, so a reduction of that magnitude is a meaningful quality-of-life improvement for both users and developers.
Base also reported several bursts of 5,000 transactions per second. These figures are internal network claims based on observed performance, and should be understood as reported results rather than guaranteed sustained throughput. Peak burst performance can differ significantly from average throughput under typical load conditions. That said, 5,000 TPS bursts indicate meaningful headroom above typical usage levels, which matters for applications that need confidence the network can handle demand spikes without degrading.
What Comes After Azul
The Azul launch is not the endpoint of Base’s upgrade roadmap. The network has additional releases planned, with the next upgrades expected to focus on performance improvements and user experience enhancements. Native account abstraction is also on the roadmap, a change that would make wallet creation and transaction management significantly simpler for end users by removing some of the friction currently associated with managing Ethereum accounts.
The broader direction Base is signaling through the Azul upgrade is consistent: a Coinbase-backed Ethereum layer 2 that is progressively becoming faster, more decentralized, and less dependent on any single proof system or infrastructure provider. One-day withdrawals, a multiproof architecture, Base-native clients, and a path toward Stage 2 decentralization are the components of that vision becoming operational rather than aspirational.
For users, the near-term benefit is faster and more secure movement of assets between Base and Ethereum. For developers, it is a more performant and stable network with minimal disruption to existing applications. For node operators, it is a required migration with a defined path and clear documentation. For the Ethereum layer 2 ecosystem more broadly, Base Azul is a signal that Coinbase’s network is maturing into a serious independent infrastructure project rather than a consumer-friendly wrapper around shared rollup components.
