ACDE #214: Call Minutes

The call where developers finalized the scope of Fusaka (again)

Jun 20, 2025

Good evening,

Today, Ethereum developers revisited the decisions they made on the last All Core Developers Execution Call (ACDE) call, ACDE #213. They agreed to keep the finalized scope of the Fusaka upgrade relatively unchanged, with the inclusion of just one additional Ethereum Improvement Proposal (EIP), EIP 7939.

Below is my full call summary for the ACDE #214.

Yours truly,

Christine D. Kim

Key Decisions & Announcements

(For background on the ACD process and jargon used on these calls, refer to the Ethereum Governance 101 document in the ACD Toolkit.)

Fusaka:

Developers agreed to include the following 12 EIPs in the Fusaka upgrade:
- 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-7892: Blob Parameter Only Hardforks
- EIP-7917: Deterministic proposer lookahead
- EIP-7918: Blob base fee bounded by execution cost
- EIP-7935: Set default gas limit to XX0M (Informational)
- EIP-7951: Precompile for secp256r1 Curve Support
- EIP-7907: Meter Contract Code Size And Increase Limit
- EIP-7934: RLP Execution Block Size Limit
- [NEW] EIP-7939: New Opcode for Counting Leading Zeros
They also agreed to the following changes in the implementation details of certain Fusaka EIPs:
- Repricing for the EIP 7951 precompile: Developers stated that more testing and benchmarking analysis are needed to determine the cost of this new operation.
- Reduction of the contract code size limit in EIP 7907 from 256 KB to 48 KB: Developers stated that they will start with a lower increase to the contract code size due to a lack of testing and benchmarking for the higher 256 KB limit.
- Reduction of the blob base cost parameter in EIP 7918 from 2^14 to 2^13: Developers were divided on the base cost for blobs. While some advocated for keeping the base cost parameter elevated at 2^14, others argued that it should start lower, as low as 2^11. They compromised and agreed to a blob base cost parameter of 2^13.
- Remove the maximum blob count per transaction parameter from EIP 7892 and add it instead to EIP 7594: Because developers do not anticipate this parameter as needing to be updated regularly through blob parameter only hard forks, they agreed to specify this parameter in the PeerDAS EIP and make it only updateable through regular Ethereum hard forks.
Developers aim to launch Fusaka Devnet 2 on Monday, June 23, provided there are a minimum of three consensus layer (CL) and three execution layer (EL) client teams ready with updated releases. If not, they will launch the developer-focused test network (devnet) as soon as a sufficient number of client teams are ready.
Berlinterop Devnet 2 will be deprecated shortly after the launch of Fusaka Devnet 2.

Glamsterdam:

Two new proposals for Glamsterdam were presented on ACDE #214:
- EIP 7745: Trustless Log Index by Geth developer Zsolt Felfoldi.
- [HEADLINER PROPOSAL] EIP 7919: Pureth by Nimbus developer Etan Kissling

Notable Discussion

(Quotes featured in this section may be edited slightly for grammar and clarity. For more information on the people quoted in this section, refer to the ACD Call Directory in the ACD Toolkit.)

Fusaka Scope Freeze

Developers spent most of today’s call determining the scope of testing for the next Fusaka devnet.

Ethereum Foundation (EF) Researcher Ansgar Dietrichs, who chaired the call in place of EF Protocol Team Lead Tim Beiko, was strongly in favor of freezing Fusaka specifications on the call and making Fusaka Devnet 2 the last devnet for developer-focused testing.

Dietrichs said:

“Ideally, we can today make final decisions about inclusion. … Whatever is not selected for Devnet 2, at least as of today, would then be intended to also just not go into the hard fork and then within the already [scheduled for inclusion] EIPs, there are some small last parameters that also need to be decided and again, ideally we would make that decision today as well.”

However, not all decisions could be made on today’s call.

Regarding the repricing of EIP 7951, EF Developer Operations Engineer Barnabas Busa said:

“It makes no sense to change the price right now. No rush. We should actually evaluate what the [real] pricing will be, and then we can do all the repricing in Devnet 3.”

Further, certain changes to EIPs that developers agreed to on today’s call were not changes that client teams felt confident they could implement in time for the Devnet 2 launch on Monday.

Geth developer Matt Garnett, also known by the screen name “Lightclient,” advocated for changes to EIP 7907, which developers supported due to a lack of adequate testing, to be included in Devnet 3, instead of Devnet 2. He said:

“We agreed on what Devnet 2 was supposed to be two weeks ago. So it feels a little weird to constantly change everything.”

Other changes developers agreed should be included in Fusaka Devnet 3, rather than Fusaka Devnet 2, included the parameter changes in EIP 7918 and EIP 7892 (listed above).

Dietrichs said these decisions confirm that developers will need to extend the Fusaka testing timeline by a few weeks and that they can re-evaluate the scope for testing on Devnet 3 after Devnet 2 has launched.

EIP 7939 Inclusion

As part of the discussion on Fusaka, developers agreed to schedule for inclusion (SFI) a new EIP, EIP 7939, in the upgrade. As background, EIP 7939 is a proposal for adding a new operation or opcode to the Ethereum Virtual Machine (EVM) to enhance the efficiency of smart contract code execution.

Notably, this EIP was already implemented and tested by client teams on Berlinterop Devnet 2, which is why most developers were in favor of including it in Fusaka. Dietrichs noted that the implementation of the EIP was “out of process” because it had not been formally proposed for Fusaka.

Reth developer Roman Krasiuk said the EIP had been proposed but was “ignored in the process.” Garnett said the EIP was proposed, but not by the deadline set by developers for Fusaka EIP proposals.

In any case, all client teams were in favor of including the EIP regardless of the break in process. Dietrichs said:

“These things are never ideal. So, I think in general, we should try to stick to the process in these things, but again, in this case, my understanding is that all the clients would want this. … I will just make the call to overrule process here. We will add and then immediately move to SFI, this EIP, and that means it will then also be part of [Fusaka] Devnet 2.”

🌻That’s all for my summary on ACDE #214. You are now officially caught up on the state of Ethereum protocol development and governance. Stay tuned for my insights on ACDE #214 coming out tomorrow.

🌻New to the ACD calls and need help understanding what’s going on? Check out the ACD Toolkit. It contains evergreen resources and materials that teach you the fundamentals of tracking the evolution of Ethereum like a pro:

ACD Toolkit

🌻I also offer professional consultations on Ethereum protocol development and governance. If you’d like to book a meeting with me to get tailored insights into the evolution of Ethereum for your business or portfolio, please use my Calendly scheduling page:

Book a meeting

Below are links for further reading on the topics discussed on ACDE #214.

Berlinterop Devnet 2 Real-time Activity (Block explorer)
Considerations for the BLOB_BASE_COST in EIP-7918 (Research post)
Considerations for the maximum blob count per transaction parameter (Github pull request)
EIP 7919 Presentation Slides by Etan Kissling (Discord message)

Here’s what’s coming up next week on the Ethereum Protocol Call Calendar:

Monday June 23

12:00 UTC/8:00 ET, Eth Simulate Implementors Meeting #54 (Meeting link shared on Telegram)
14:00 UTC/10:00 ET, All Core Developers Testing Call #41 (Meeting link shared on Discord)
15:00 UTC/11:00 ET, RPC Standards Call #7 (Meeting link shared on Discord)
~~15:30 UTC/11:30 ET, Portal Implementors Call~~ (Call series cancelled)

Tuesday June 24

16:00 UTC/12:00 ET, EIP Editing Office Hour (Meeting link shared on Discord)

Wednesday June 25

14:00 UTC/10:00 ET, Protocol Research Call #3

Thursday June 26

14:00 UTC/10:00 ET, All Core Developers Consensus Call #159 (Meeting link shared on Discord)

Friday June 27

No calls scheduled on this day.

📅 Call days and times may be subject to change so please utilize the links shared above to reconfirm meeting details day of. 📅

Thank you for subscribing to ACD After Hours! If you like what you read, consider sharing it with a friend who might also enjoy the content.

If today’s post sparked any thoughts, opinions, or questions, I’d love to hear them. Please share your feedback on today’s newsletter by leaving a quick comment. I read every response!