All Core Devs - Consensus (ACDC) #157, May 15 2025

All Core Devs - Consensus (ACDC) #157, May 15, 2025

Agenda

Facilitator emails: stokes@ethereum.org

🤖 config
  • Duration in minutes : 90
  • Recurring meeting : true
  • Call series : ACDC
  • Occurrence rate : bi-weekly
  • Already a Zoom meeting ID : true
  • Already on Ethereum Calendar : true
  • Need YouTube stream links : true
  • display zoom link in invite : false # Set to true to add the Zoom link to the Google Calendar invite description

GitHub Issue

1 Like

Summary

Recordings

https://www.youtube.com/live/Bn4jGMnub9g
https://x.com/ethcatherders/status/1923010406353703098

Writeups

Additional info

Meeting Summary:

No summary available. Could not retrieve summary.

Recording Access:

YouTube Stream Links:

ACDC #157 Summary

Action items

  • Continue work towards fusaka-devnet-0
    • To be launched 26 May

Summary

Pectra

  • Pectra upgrade completed successfully :tada:
  • Trent published Pectra perspectives from various core contributors
  • Pari conducting analysis on blob increase following Pectra; report forthcoming

⠀Fusaka

  • peerdas-devnet-7 launched; currently stable
  • Client teams primarily working on implementing BPO support
  • fusaka-devnet-0 ; aim for 26 May launch
  • We touched on validator custody implementation and any potential spec complexity
    • Async followup on Discord

⠀ACD Restructuring Proposal

  • Tim proposed reorganizing All Core Devs meetings:
    • ACDT to focus on current fork N
    • ACDE/C to focus on future fork N+1
  • Key discussion points:
    • Need for broader community input earlier in process
    • Concern about splitting attention between current and future forks
    • Proposal to formalize working group reviews
  • Proposed Timeline Structure for ACDE/C
    • Initial month for high-level fork focus discussion
    • Agreement on main features by early July
    • Core feature development alongside Fusaka work
    • Integration of smaller EIPs later
  • Marchill raised the need for a new ACD forum to improve community involvement
    • Participants leaned towards improving Ethereum Magicians, but agreed for a better way to surface input, and track R&D process of an EIP from proposal to mainnet.
1 Like