BRIP-0010: Fusaka Hardfork Specification

Proposals BRIPs
,
1

Abstract

This BRIP defines the scope and specification for the Fusaka hardfork on Berachain. The upgrade bundles consensus layer improvements, execution layer EIP adoptions from Ethereum’s Fusaka fork, and parameter updates for the next iteration of Proof of Liquidity into a single coordinated network upgrade.

Specifically, the hardfork includes: EIP-6110 style deposit processing, EIP-7951 (P-256 precompile), a contract code size limit increase, EIP-7939 (CLZ opcode), EIP-7823/7883 (MODEXP repricing), EIP-7934/7825 (block and transaction size caps), the validator effective balance hysteresis update from BRIP-0008, and consensus layer parameter changes to support PoL vNext.

Motivation

Bundling these changes into a single hardfork minimizes the operational burden on validators (one upgrade cycle instead of many) while ensuring interdependent changes activate atomically. The included changes fall into five categories:

  1. Deposit processing reliability — Migrating to EIP-6110 style in-payload deposits eliminates the eth1 follow distance and delayed queue, reducing latency and complexity.

  2. EVM feature parity — Adopting select Fusaka and Glamsterdam EIPs keeps Berachain compatible with emerging Ethereum tooling, wallet standards (passkeys/WebAuthn), and security best practices.

  3. DoS hardening — MODEXP repricing, block size caps, and per-transaction gas caps close known underpricing vectors before they can be exploited.

  4. Validator economics — The current hysteresis configuration strands validator capital unnecessarily; updating these constants improves capital efficiency across the validator set (see BRIP-0008).

  5. PoL evolution — Consensus layer parameter changes are required to support the next iteration of Proof of Liquidity.

EIP Selection

EIPs were evaluated on three axes:

  • Security — MODEXP repricing and size caps close known DoS vectors.

  • Ecosystem compatibility — P-256 precompile and CLZ opcode keep Berachain aligned with Ethereum tooling and emerging wallet standards.

  • Berachain relevance — EIP-7918 (blob base fee) was excluded as Berachain does not use blob transactions.

Full specification: BRIPs/meta/BRIP-0010.md at main · berachain/BRIPs · GitHub