AllCoreDevs - Execution (ACDE) #216 (July 17, 2025)

[nixorokish]

AllCoreDevs - Execution (ACDE) #216 (July 17, 2025)

• Jul 17, 2025, 14:00 UTC
• Ethereum Protocol Calls Calendar subscription

Agenda

• Fusaka
  • devnet updates
  • Upgrade timelines
    • After Pectra, we agreed to have a 30 day window between client releases and both the first testnet fork and mainnet.
    • Assuming we followed this and wanted to deliver Fusaka before Devconnect, this implies:
      • Mainnet ~> Nov 5-12
      • Last testnet ~> Oct 6-10
      • First testnet ~> Sep 22 - Oct 3
      • Client testnet releases ~> Week of Aug 25
        - Is this realistic?
      • @ralexstokes counter-proposal
      • PeerDAS todos
      • Holesky fork?
    • EIP-7907
    • Update EIP-7825: Lower Tx Gas Limit Cap EIPs#9986
• Glamsterdam Planning
  • Next 2 ACDE focused on headliner discussions
    • Client team preferences
      • Geth
      • Reth
      • Erigon
      • Nethermind
      • Besu
      • Lighthouse
      • Prysm
      • Grandine
      • Lodestar
      • Teku
    • Most important open questions
    • Scheduling live discussions
    • Broader community input
  • EIP PFI deadline?
    • August 21 (end of headliner selection)?
    • Sep/Oct?
    • Fusaka shipping?

🤖 config

• Duration in minutes : 90
• Recurring meeting : true
• Call series : acde
• Occurrence rate : bi-weekly
• Already a Zoom meeting ID : true
• Already on Ethereum Calendar : true
• Need YouTube stream links : true
• Facilitator email: tim@ethereum.org
  Note: The zoom link will be sent to the facilitator via email

[github-actions]

Discourse Topic ID: 24770

• Action: Updated at 2025-07-17 14:01 UTC
• URL: https://ethereum-magicians.org/t/24770

Zoom Meeting: Reusing meeting 88269836469 for series 'acde'.

• Zoom link hidden (sent to facilitator email)

Existing YouTube Stream Links (Reused):

• Stream 1 (Jul 17, 2025): https://youtube.com/watch?v=dkIQxIHX56E

Calendar Event: Reusing existing event for series.

• Approximate Google Calendar Link
• Skipping email notification (already processed issue AllCoreDevs - Execution (ACDE) #216 (July 17, 2025) #1610 before).

Telegram Notification

• Updated message for this occurrence to Ethereum Protocol Updates channel

[SirSpudlington]

General question: How do EIP authors present potential EIPs? Is it like a full-blown presentation, or is it more of a "show up and talk" type situation?

[nixorokish]

General question: How do EIP authors present potential EIPs? Is it like a full-blown presentation, or is it more of a "show up and talk" type situation?

heya! Propose it as an agenda item on the issue for the relevant ACD (execution vs. consensus) and the moderator (execution: Tim, consensus: Alex) will add it to the agenda if appropriate. Having a 5-min (really 5 min!) presentation is good

It's also good to indicate whether you mean to present for general feedback from a specific group or proposing for a specific fork - Fusaka scope is frozen, Glamsterdam is still looking at only headliners at the moment, so if you mean it for a specific fork, you may have to wait until Glamsterdam is soliciting non-headliner EIPs
Timeline here: https://forkcast.org/upgrade/glamsterdam#glamsterdam-timeline

In general, the first step is making sure you have an Ethereum Magicians post for it first, which it looks like you already do (7932?)?

[nerolation]

I'd like to discuss lowering the tx gas limit cap in EIP-7825 as done in the PR here:
ethereum/EIPs#9986

Otherwise, I'd propose that we consider this EIP in glamsterdam:
ethereum/EIPs#9984

Carried out some analysis alongside:
https://github.com/nerolation/eth-16m-gas-cap-analysis/blob/main/eip_7983_comprehensive_analysis.ipynb

[SirSpudlington]

heya! Propose it as an agenda item on the issue for the relevant ACD (execution vs. consensus) and the moderator (execution: Tim, consensus: Alex) will add it to the agenda if appropriate. Having a 5-min (really 5 min!) presentation is good

It's also good to indicate whether you mean to present for general feedback from a specific group or proposing for a specific fork - Fusaka scope is frozen, Glamsterdam is still looking at only headliners at the moment, so if you mean it for a specific fork, you may have to wait until Glamsterdam is soliciting non-headliner EIPs Timeline here: https://forkcast.org/upgrade/glamsterdam#glamsterdam-timeline

In general, the first step is making sure you have an Ethereum Magicians post for it first, which it looks like you already do (7932?)?

Thank you for this info, I'll wait until Glamsterdam opens up to Non-Headliner proposals.

[fjl]

The Geth team supports EIP-7928 "Block-Level Access Lists" as the headliner proposal for the Glamsterdam fork. We would very much like to see the design include an improvement for the snap sync 'healing phase' alongside the support for parallel tx execution.

Assessment of all EL headliner proposals: https://notes.ethereum.org/@fjl/glamsterdam-headliner-el

[timbeiko]

@nerolation your PR was merged, anything else to discuss on ACDE?

[ralexstokes]

i'd like to toss another option for fusaka mainnet timing that leaves a little less room around testnets to give us a bit more time to harden implementations.

note: this is all assuming happy paths; if e.g. there is a significant failure on a testnet, we will have to revise the schedule.

1 Sep - RC client releases
15 or 22 Sep - Sepolia
< 2 or 3 weeks>
6 Oct - Hoodi
< 30 days>
5 Nov - mainnet

from today, this implies we have the rest of July to get any last minute spec things sorted and devnet-3 live and healthy, all of August can be devoted to hardening implementations, and then we move to the deployment pipeline in September

[nalepae]

As far as peerDAS is concerned on the CL side, before running any testnet, we should at least:

• Ensure all clients can sync in the "perfect peerDAS" configuration. (aka. perfect_peerdas_enabled: true on Kurtosis)
• Ensure all clients perform well without engine_getBlobsV2. (Using private blob txs in devnets can do the job.)

[terencechain]

Prysm team's preference on glamsterdam headliner

[sauliusgrigaitis]

Grandine team prefers eip-7732 as Glamsterdman headliner for CL. However, our opinion may change after we hear more community input on this and other EIPs. As I mentioned in the previous ACD, we should focus on community input.

[somnathb1]

Erigon team's preference on Glamsterdam headliners - It's indicative and not comprehensive or absolute, intended to help in making the final decision rather than dictating it.