Title: EIP_7607__Fusaka_Meta_EIP
Category: EIPs

Author: timbeiko
Date: 2024-01-31T23:00:00.000Z

Fusaka Planning Timeline

March 24: deadline for EIPs to be Proposed for Inclusion in Fusaka
March 31: deadline for client teams to share their preferences about scope, including which EIPs they think should be Declined for Inclusion.
April 10: Fusaka scope frozen

Author: abcoathup
Date: 2025-02-20T22:19:53.929Z

Fusaka scope preferences
Consensus Layer client teams
Grandine
Lighthouse


Sigma Prime – 2 Apr 25



Lighthouse Team on Fulu
The Lighthouse team's outlook on Fulu EIP inclusion





Lodestar



ChainSafe – 28 Mar 25



Lodestar's Fusaka Inclusion Perspective
In response to the Fusaka deadline outlined in the All Core Developers March Checkpoint, this blog post summarizes the collective thoughts of Lodestar's perspective on the Fusaka hard fork.


Keep Fusaka Small and Focused

Taking into account some...





Prysm



HackMD



Prysm Recommendation for Fusaka - HackMD
We believe that the aggressive pace called for by the community, including core devs, will require more frequent and smaller forks. Scope and time are coupled in software engineering—if we want a concrete timeline, the scope needs to stay flexible:...





Nimbus
Teku



HackMD



What do we want to see in Fusaka? - HackMD





Execution Layer client teams
Besu



HackMD



Besu Fusaka Position Paper - HackMD
The Besu team is thinking about Ethereum's next upgrade in 4 different ways:





Erigon



erigon.tech



A Lean Approach to Fusaka: Our Stance on a Minimal Fork – Erigon.tech





Geth
Nethermind
https://x.com/m25marek/status/1896911082628727213
Reth



Paradigm – 19 Feb 25



What comes after Ethereum’s Pectra hard fork?
The Reth team’s view on what should happen in Fusaka, Ethereum’s next hard fork after Pectra.





Layer 2s
Base


blog.base.dev



blob/acc: Achieving more blob space in 2025
To support a global onchain economy and ensure Ethereum's success, Base believes it's crucial to ship the Fusaka hard fork Q3 of 2025, here's the plan..





Languages
Solidity



Solidity Programming Language



The Case for EOF | Solidity Programming Language
Posted by Kamil Śliwak on March 27, 2025





Vyper


github.com/ethereum/pm








All Core Devs - Execution (ACDE) #209



        opened 05:04PM - 27 Mar 25 UTC




          timbeiko
        




          ACD
        

          Execution
        




# All Core Devs - Execution (ACDE) #209

* [April 10, 2025, 14:00-15:30 UTC](htt…ps://www.timeanddate.com/worldclock/converter.html?iso=20250410T140000&p1=1440&p2=37&p3=136&p4=237&p5=923&p6=204&p7=671&p8=16&p9=41&p10=107&p11=28)
* 90 minutes
* Stream: TBA

# Agenda 

- Pectra 
    - EIP-7702 receipts
      - https://github.com/ethereum/execution-apis/pull/640
      - https://ethereum-magicians.org/t/eip-7702-set-eoa-account-code/19923/382
- [Fusaka](https://eips.ethereum.org/EIPS/eip-7607)
    - Scope finalization
        - PFI vs. CFI vs. SFI 
        - Client Team preferences
            - [Besu](https://hackmd.io/@RoboCopsGoneMad/H1z1lky6Je)
            - [Reth](https://www.paradigm.xyz/2025/02/what-comes-after-ethereums-pectra-hard-fork)
            - [Erigon](https://x.com/GiulioRebuffo/status/1900854414174204182)
            - [Nethermind](https://x.com/M25Marek/status/1896911082628727213) 
        - Synchronous vs. async presentations
            -  EIP-7819 
            - [EIP-7918](https://ethereum-magicians.org/t/eip-7918-blob-base-fee-bounded-by-execution-cost/23271) 
- [Reconfiguring AllCoreDevs](https://ethereum-magicians.org/t/reconfiguring-allcoredevs/23370)

--- 

Facilitator email: tim@ethereum.org






Community




EIP-7607: Fusaka Meta EIP EIPs Meta


Personal scope preference

Whilst client team & EthPandaOps preferences are all important, the community should also take the opportunity to respond in a structured manner to upgrade scoping.
I summarized ACD calls async for 3.5 years (former editor of weekinethereumnews.com) and collected summaries/writeups in Protocol Calls & happenings - Fellowship of Ethereum Magicians.  The following is my two cents.

Roadmap focus

The Surge - L2 scaling 
EIPs should generally only be considered for inclus…

Author: timbeiko
Date: 2025-02-28T15:35:48.892Z

Base’s preferences for Fusaka: blob/acc: Achieving more blob space in 2025

Author: timbeiko
Date: 2025-03-13T17:21:14.219Z

Cross-linking a thread highlighting concerns about EOF: Ethereum is turning into a labyrinth of unnecessary complexity with EOF - Let's reconsider EOF

Author: TimDaub
Date: 2025-03-18T23:29:32.092Z

What‘s the current thinking around the blob target increase? The fee accrual to Ethereum stakers is now 10x less after blobs and the blob fee market has just kicked in a few months ago.
It was widely criticized that the too high blob fee target meant that Ethereum didn‘t capture any value for a long time as price discovery didn‘t happen. Today ETH is mechanically worth less because of that change. Sentiment is down and analysts dislike the project.
Why should we just pass out a free blobs voucher to Base et al when it would be much more beneficial to leave the target where it is right now so that more competition happens around DA?

Ethereum is poised for significant growth, with the potential to one day serve a vast global user base seeking a freer, more open economy. Right now, blob usage has been saturated for several months, resulting in higher fees for users and constrained ecosystem growth. Even though Pectra increase will offer some relief, the expected increase in blob count won’t be enough to handle explosive growth as more rollups come online.

This is a crazy claim. Where is the evidence for this? I actually had to go to Basescan myself because this seemed like such a crazy claim that I thought I was the crazy one. I picked a random transaction for an ERC20 transfer and voila: $0.000708

resulting in higher fees for users and constrained ecosystem growth.

It costs a fraction of a cent to transact on L2s like Base. No user is held back by transacting on Base for $0.000708 or even double or triple that. wat

Author: abcoathup
Date: 2025-03-24T23:00:04.511Z

Personal scope preference

Whilst client team & EthPandaOps preferences are all important, the community should also take the opportunity to respond in a structured manner to upgrade scoping.
I summarized ACD calls async for 3.5 years (former editor of weekinethereumnews.com) and collected summaries/writeups in Protocol Calls & happenings - Fellowship of Ethereum Magicians.  The following is my two cents.

Roadmap focus

The Surge - L2 scaling
EIPs should generally only be considered for inclusion if they significantly move the roadmap forward.

Scheduled for inclusion (SFI)

EIP-7594 PeerDAS: L2 scaling

Considered for inclusion (CFI)

EIP-7892 Blob Parameter Only Hardforks: L2 scaling
EIP-7839 Unified Network Configuration: reduce config complexity
EIP-7910 eth_config JSON-RPC Method: reduce config issues

Denied for inclusion (DFI)

EIP-7692 EOF:  Geth were against.  (Client teams with greater than one third market share & DevOps should have an informal veto.  Currently this would be Geth & Nethermind)

Author: abcoathup
Date: 2025-03-26T02:08:49.801Z

@potuz personal take
https://x.com/potuz_eth/status/1904138823606386985

Author: timbeiko
Date: 2025-03-26T20:03:44.056Z

Besu’s preferences: Besu Fusaka Position Paper - HackMD
Shared here: https://x.com/HyperledgerBesu/status/1904936507858710768

Author: abcoathup
Date: 2025-03-27T00:09:20.956Z

Erigon’s preferences: A Lean Approach to Fusaka: Our Stance on a Minimal Fork – Erigon.tech
Shared here: https://x.com/ErigonEth/status/1903769491072221365

Author: terence
Date: 2025-03-27T00:48:37.415Z

Prysm’s preference: Prysm Recommendation for Fusaka - HackMD

Author: matt
Date: 2025-04-10T13:21:48.301Z

The go-ethereum team’s opinion on Fusaka: https://notes.ethereum.org/@lightclient/osaka-prefs