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

Action Items

Fusaka

Glamsterdam

  • Continue headliner discussions on next ACDE calls (July 31 & August 14)
  • Finalize headliners by August 21

Summary

Fusaka Devnet Updates

  • Devnet-2 running stable with minor issues mainly from Consensus Layer clients:
    • Lighthouse: Incorrect suggested value, payload leak.
    • Lodestar: Excessive polling leading to peer bans.
    • Nimbus: Node overloaded and crashing due to requests.
    • Prysm: Missing metadata field, incorrect block schedule (PR fix available).
  • Client teams comfortable proceeding to devnet-3 by July 23.

EIP-7907

  • Decision: Removed from Fusaka due to significant unresolved complexity and timeline risks.
  • Simplified alternatives (like EIP-7903) discussed but rejected to avoid additional delays.
  • General agreement to defer significant contract size changes to Glamsterdam or future forks.

Fusaka Timeline and Audit Concerns

  • Current proposed timeline is tight if targeting delivery before Devconnect (~Nov 5-12 Mainnet).
  • Uncertainty remains around achieving sufficient testnet stability and allowing enough time for audit competition and bug bounty.
  • Holesky upgrade could provide early indicator of readiness without extensive user disruption.

Glamsterdam Headliner Selection

  • Execution Layer (EL) leaning strongly toward Block-Level Access Lists, paired with significant gas repricing to achieve meaningful scaling improvements.
  • Consensus Layer (CL) strongly favors EPBS, with wide but not unanimous support.
  • FOCIL is popular but seen as potentially conflicting with EPBS in terms of implementation complexity and scope. Consensus to evaluate further on upcoming calls.

Timeline for other Glamsterdam EIPs

  • Deadline for regular (non-headliner) EIPs will be set after headliners are finalized (Aug 21 tentative).
  • Clients prefer focusing on Fusaka for now, delaying broader EIP considerations slightly.

Next Steps

  • Clearly define priorities between FOCIL and EPBS in upcoming Consensus Layer discussions.
  • Determine community stakeholders needed for headliner feedback.
  • Further clarify testing requirements and audit timelines for Fusaka.
1 Like