Beryl Upgrade Overview
Beryl is the next Base hardfork after Azul. It folds together three unrelated changes: a chain-native token standard called B20, a shorter wait before withdrawals finalize, and the Reth V2 node release that trims disk usage and accelerates state-root work.
What Beryl ships
Section titled “What Beryl ships”- B20 — a native token standard built for issuers of stablecoins, real-world assets (RWAs), and long-tail tokens.
- Faster withdrawals — a single-proof proposal now finalizes after 5 days instead of the previous 7, returning bridge liquidity sooner.
- Reth V2 — as much as 50% less disk and a rebuilt state-root pipeline worth roughly +33% throughput.
Activation timestamps
Section titled “Activation timestamps”| Network | Timestamp | Date |
|---|---|---|
mainnet | 1782410400 | 2026-06-25 18:00:00 UTC |
sepolia | 1781805600 | 2026-06-18 18:00:00 UTC |
Required software
Section titled “Required software”Builds for both networks are now published — the Mainnet versions have been confirmed ahead of its activation date.
| Layer | Software | Mainnet | Sepolia |
|---|---|---|---|
| Execution (EL) | base-reth-node | v1.1.1+ | v1.1.0+ |
| Consensus (CL) | base-consensus | v1.1.1+ | v1.1.0+ |
| - | base/node | v1.1.1+ | v1.1.0+ |
B20: native token standard
Section titled “B20: native token standard”B20 is Base’s own token standard: tokens that keep ERC-20 compatibility but run as Rust precompiles instead of EVM contracts, aimed at stablecoin, RWA, and long-tail issuers. The full surface is documented in B20 Native Token Standard, covering the roles model, policy integration, the factory, the policy registry, mint and burn, and the asset/stablecoin variants.
Withdrawals
Section titled “Withdrawals”Beryl shortens how long a single-proof proposal sits in its dispute game before finalizing — that wait drops to 5 days, down from 7. The TEE + ZK dual-proof path that Azul introduced is untouched and still resolves in a single day.
Returning capital to fast-bridge liquidity providers sooner is the point: shorter lockups mean lower fees and steadier third-party bridging for the people using it.
Reth V2
Section titled “Reth V2”Reth V2 ships as a node-software update alongside Beryl — it needs no separate network upgrade. It targets the two ceilings on a high-throughput chain, disk footprint and state-root speed, through Storage V2 and a rewritten state-root computation path. Full details are in Reth V2.
Native Account Abstraction (EIP-8130)
Section titled “Native Account Abstraction (EIP-8130)”Account abstraction moves into the protocol itself, but it is not part of Beryl. It was slated for Cobalt, the hardfork that comes next, until the node source moved it onto a separate activation gate in September 2026 — one that no public network sets. Nothing has been scheduled in its place. Each account records — onchain — who is allowed to act for it and how its signatures are checked, so smart-account behavior no longer depends on bundlers, relays, or a separate mempool. That hands applications portable smart accounts out of the box, along with scoped, revocable session keys, atomic call batching, and gas sponsorship paid natively by the protocol. EIP-8130 is still experimental and, for now, runs only on the vibenet devnet. The full mechanics — the account/actor/policy/authenticator model and a working vibenet example — are in Native Account Abstraction.