I propose reconfiguring AllCoreDevs such that ACDE & ACDC focus on scoping the 1

 welcoming existing attendees, these calls could more explicitly solicit input from a3

 broader range of community stakeholders.
4


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

focused on the current fork’s implementation details, rather than setting its scope, 6

ensuring that resolving technical issues doesn’t compete with high-level feature prioritization.

x7

ensuring that resolving technical issues doesn’t compete with high-level feature prioritization.
8


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

Glamsterdam presents a good opportunity to test this process. Before then, I propose having a review and feedback period, aiming for a go10

next hard fork, rather than implementing the current one. In addition to/no-go decision shortly after Pectra mainnet releases are out.2