All Core Devs - Execution (ACDE) #211, May 8

All Core Devs - Execution (ACDE) 211

Agenda

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

GitHub Issue

1 Like

Summary

[Main action items by @timbeiko copied from Eth R&D Discord]

  1. We agreed to SFI EIP-7935, with the implication that other EIPs related to increasing the gas limit will be added to Fusaka
  2. In that vein, we agreed to CFI EIP-7934
  3. On Monday’s call, we’ll agree to the scope for fusaka-devnet-1 . Client teams, please review the SFI list and prepare your “sorted preferences” for CFI → SFI by the call: EIP-7607: Hardfork Meta - Fusaka

The testing team will also review the CFI list and share their thoughts on the testing burden for each EIP before then.

Recordings

https://www.youtube.com/live/Y7j8FdRkSrA?t=170s
https://x.com/EthCatHerders/status/1920482268117680461

Writeups

Additional info

ACDE #211 Summary

Action Items

  1. We agreed to SFI EIP-7935, implying that other gas-limit-related EIPs will be added to Fusaka.
  2. In line with the above, we agreed to CFI EIP-7934.
  3. On Monday’s call, we’ll finalize the scope for fusaka-devnet-1. Client teams are encouraged to review the current CFI list and prepare their sorted preferences for EIPs they’d like to promote from CFI → SFI.

Summary

Pectra Mainnet Wrap-Up

  • Pectra activated smoothly on mainnet on May 7, 2025, with no significant issues reported. Client teams and users are encouraged to closely monitor network behavior post-upgrade.
  • This fork introduced several significant changes, notably EIP-7702 (EOA account code setting), EIP-7251 (MAX_EB), and the EIP-2537 BLS precompile. Client teams highlighted improved testing processes and encouraged ongoing feedback.

Fusaka Planning

  • Fusaka implementation discussions will shift exclusively to the weekly ACDT call moving forward.
  • The immediate next step is finalizing fusaka-devnet-1 scope on next Monday’s ACDT call, after client teams provide their prioritized preferences for EIPs moving from CFI → SFI.
  • As of this call, we’ve SFI’d EIP-7935 (default gas limit adjustment) and previously EIP-7594 (PeerDAS). Additionally, we’ve CFI’d EIP-7934 (RLP execution block size limit) and several repricing EIPs (notably EIP-7823 and EIP-7883 related to MODEXP). However, these repricing EIPs remain pending full consensus and test coverage before they can move to SFI.

Gas Limit and State Growth Discussion

The discussion around raising the gas limit (EIP-7935) dominated the call, highlighting clear areas of alignment and remaining uncertainties:

  • Agreed upon :
    • SFI EIP-7935, setting a default gas limit (likely around 150M), to provide a concrete baseline for testing and performance validation. This agreement explicitly implies that related repricing EIPs, notably EIP-7934 (10 MB RLP execution block size limit), will need to accompany this change to manage resource usage effectively.
  • Open discussions and considerations :
    • Extensive debate about resource implications of higher gas limits. Specific bottlenecks highlighted include increased disk requirements, state-sync performance degradation, and elevated RAM usage (potentially necessitating 32+ GB nodes).
    • Teams highlighted that EIP-7938 (exponential auto-increase mechanism) remains ambitious. Several participants emphasized the necessity of robust empirical validation before pursuing automated gas limit increases.
    • Broad acknowledgment that repricing EIPs (EIP-7823 and EIP-7883, potentially EIP-7918) should precede substantial gas limit increases. Current statuses of these repricing EIPs are still CFI, with client teams expected to confirm their readiness and testing status by Monday.
    • Further, there’s general alignment that gas-limit scaling must be carefully coordinated with progress on history expiry and better pricing of state IO operations, though these discussions remain ongoing.

Given the complexity and depth of technical trade-offs, stakeholders and implementers are strongly encouraged to review the call recording and chat transcript for full context.

AllCoreDevs Process Improvement

  • Due to time constraints and extensive discussion around the gas limit topic, we did not cover previously planned conversations on ACD process improvements or the proposed ACD platform during this call. Interested parties should continue participating asynchronously via the Ethereum Magicians threads:

EVM & Additional Topics

  • A brief discussion around removing dynamic jumps occurred, concluding that substantial changes to EVM functionality (e.g., static vs. dynamic jumps) should likely be addressed through a longer-term EVM roadmap rather than immediate inclusion in Fusaka. Participants expressed interest in structuring this conversation more explicitly in future calls.

Closing Shout-Outs

  • Contributors to the recent Pectra upgrade are invited to submit feedback and experiences for the Pectra Pages.
  • The second Protocol Research Call is scheduled for next Wednesday, focusing on short-term EL scaling strategies targeting Glamsterdam and future forks.

Next Steps

  • Client teams encouraged to carefully review the current CFI EIPs list, preparing their ranked preferences and testing statuses for Monday’s call, where the final scope for Fusaka’s next devnet will be determined.
1 Like