EIP-7607 Hard fork meta: Fusaka (Hardfork Meta - Fusaka)
Final · Other · EIP status Final · created 2024-02-01
A meta EIP that compiles the list of EIPs included in the Fusaka (Fulu/Osaka) network upgrade and the activation schedule for each network. It is the upgrade following Pectra.
Why it is needed
Ethereum bundles multiple improvement proposals together and applies them as a hard fork, an upgrade where the entire network changes its rules at the same time. Without an official single place recording which EIPs are included in a given upgrade and when and on which network they are turned on, client teams, node operators, and app developers end up preparing based on different information. This document serves as the official list that shows, at a glance, all EIPs included in the Fusaka upgrade and provides links to the full specifications. It also records the schedule for the Blob Parameter Only (BPO) forks planned alongside Fusaka, covering the plan to raise blob capacity without further protocol changes.
What changes
Today
- The network is in the state after the Pectra (EIP-7600) upgrade has been applied
- The official list of which EIPs are included in Fusaka had not been finalized
- Raising blob capacity required separate coordination
After EIP-7607
- 9 core EIPs and 4 other EIPs are finalized for Fusaka and compiled into one document
- After going through the Holešky, Sepolia, and Hoodi testnets, mainnet activates on 2025-12-03
- BPO 1 and BPO 2 forks are scheduled after Fusaka to raise blob capacity without further protocol changes
Who is affected
- Client teams: Every EIP in the list must be implemented, and in particular eth/69 (EIP-7642) and eth_config (EIP-7910) must be supported by Fusaka activation.
- Node operators and validators: Clients must be updated to match each network's activation epoch and fork ID.
- App and wallet developers: You can prepare your response based on the included changes such as the transaction gas limit cap (EIP-7825) and the secp256r1 precompile (EIP-7951).
- L2: You can check the blob capacity plan expanding through PeerDAS (EIP-7594) and the BPO forks in this document's schedule.
In depth
The role of a Meta EIP
This document is not an EIP that directly changes the protocol, but a Meta-type EIP that collects the EIPs included in the Fulu (consensus layer) / Osaka (execution layer) upgrade to provide a global view of all changes and links to each specification. It follows EIP-7600, which documented the preceding upgrade, Pectra. Its status is Final, and all 14 included EIPs are listed in its requires.
9 core EIPs
The included core EIPs are EIP-7594 (PeerDAS, peer data availability sampling), EIP-7823 (set upper bounds for MODEXP), EIP-7825 (transaction gas limit cap), EIP-7883 (ModExp gas cost increase), EIP-7917 (deterministic proposer lookahead), EIP-7918 (set a blob base fee floor based on execution costs), EIP-7934 (RLP execution block size limit), EIP-7939 (count leading zeros CLZ instruction), and EIP-7951 (precompile for secp256r1 curve support).
4 other EIPs and client obligations
Beyond the core set, EIP-7892 (blob-parameter-only hard forks), EIP-7642 (eth/69, removal of pre-merge fields), EIP-7910 (eth_config JSON-RPC method), and EIP-7935 (set default gas limit to 60M) are included. Of these, EIP-7642 and EIP-7910 are explicitly stated as ones client teams MUST support by the time Fusaka activates.
Per-network activation schedule
Activation proceeds in the order Holešky epoch 165120 (2025-10-01 08:48:00 UTC, fork ID 0x783def52), Sepolia epoch 272640 (2025-10-14 07:36:00, 0xe2ae4999), Hoodi epoch 50688 (2025-10-28 18:53:12, 0xe7e0e7ff), and Mainnet epoch 411392 (2025-12-03 21:49:11, 0x5167e2a6). Activation timestamps are also specified for each network.
BPO fork 1 and 2 schedule
The blob-parameter-only (BPO) forks defined in EIP-7892 are scheduled alongside Fusaka to raise blob capacity without additional protocol changes. BPO 1 activates at mainnet epoch 412672 (2025-12-09 14:21:11 UTC, fork ID 0xcba2a1c0), and BPO 2 activates at mainnet epoch 419072 (2026-01-07 01:01:11 UTC, fork ID 0x07c9462e). For both BPOs, the Holešky, Sepolia, and Hoodi testnet schedules are set ahead of mainnet.
Security considerations and document status
Since this Meta EIP itself does not change protocol behavior, it states that there are no security considerations (None). Security analysis of individual changes follows the specification of each included EIP. The document status is Final, with the list of included EIPs and the activation schedule finalized.