I propose reconfiguring AllCoreDevs such that ACDE & ACDC focus on scoping the next hard fork,

rather than implementing the current one. In addition to welcoming existing attendees,

these calls could more explicitly solicit input from a broader range of community stakeholders.

To complement this, the existing testing/interop call would formally become “ACDT(esting)”,

focused on the current fork’s implementation details, rather than setting its scope, ensuring that resolving technical issues doesn’t compete with high-level feature prioritization.

With Pectra about to go live, and the Fusaka fork scope scheduled to finalize soon,

Glamsterdam presents a good opportunity to test this process. Before then,

 I propose having a review and feedback period, aiming for a go/no-go decision shortly after Pectra mainnet releases are out.



Context
Early in Ethereum’s history, AllCoreDevs was the only formal governance venue and had a relatively small number of participants.

 Over the years, it has grown and seen many offshoots emerge, such as ACDC, breakout rooms, 

community calls, and more. Since The Merge, we’ve gotten better at working on multiple forks in parallel: 

Dencun was live on devnets as we shipped Shapella, and Fusaka is in a similar situation as we approach Pectra’s mainnet deployment.

To complement this, the existing testing/interop call would formally become “ACDT(esting)”, 