yangkun pfp
yangkun
@yangkun
I propose reconfiguring AllCoreDevs such that ACDE & ACDC focus on scoping the next hard fork,
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
rather than implementing the current one. In addition to welcoming existing attendees,
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
these calls could more explicitly solicit input from a broader range of community stakeholders.
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
To complement this, the existing testing/interop call would formally become “ACDT(esting)”,
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
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.
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
With Pectra about to go live, and the Fusaka fork scope scheduled to finalize soon,
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
Glamsterdam presents a good opportunity to test this process. Before then,
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
I propose having a review and feedback period, aiming for a go/no-go decision shortly after Pectra mainnet releases are out.
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
Context Early in Ethereum’s history, AllCoreDevs was the only formal governance venue and had a relatively small number of participants.
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
Over the years, it has grown and seen many offshoots emerge, such as ACDC, breakout rooms,
1 reply
0 recast
0 reaction
yangkun pfp
yangkun
@yangkun
community calls, and more. Since The Merge, we’ve gotten better at working on multiple forks in parallel:
1 reply
0 recast
0 reaction