Berachain has set July 8, 2026 at 16:00 UTC as the activation timestamp for its Fusaka hardfork, per the bera-reth v1.4.1 release published June 23. Specified under BRIP-0010, the upgrade adopts Ethereum's Fulu and Osaka execution-layer EIPs in a single network event and ends support for bera-geth as a valid execution client under the companion BRIP-0009.
Node operators must migrate by July 8 at 16:00 UTC
Node operators still running bera-geth must migrate to bera-reth before July 8 at 16:00 UTC. The v1.4.1 release is labeled required for all mainnet participants, payload builders and non-payload builders alike. Any node on an older version will fork off the canonical chain.
What BRIP-0010 includes
The EIP bundle under BRIP-0010 covers five changes: EIP-6110 for in-payload deposit processing, EIP-7951 for a P-256 precompile, EIP-7939 for the CLZ opcode, EIP-7823/7883 repricing MODEXP, and EIP-7934/7825 capping block and transaction size. The hardfork also carries forward validator effective balance hysteresis changes and a contract code size increase from BRIP-0008, consolidated into one upgrade to cut validator overhead. The underlying Reth engine advances to v1.11.4.
Separate from PoL Next
Fusaka is a separate event from PoL Next, which activated on June 23. PoL Next modified Proof of Liquidity incentive mechanics, specifically how emissions route to gauges and reward vaults. Fusaka runs one layer lower: it retires the go-ethereum fork Berachain has used as its execution client and replaces it entirely with bera-reth, a Rust client. Moving off the patched Go fork means Berachain's execution layer now implements Ethereum EIPs at spec level rather than backporting them.
