You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are now the first EIPs being accepted for the Berlin HF, so we can (and should) relatively imminently start working on the integration, since planned timeline is relatively dense (June: Testnets, End of June (personal estimate: won't happen, but anyhow 😄): mainnet).
This is a meta issue to help on overall planning and coordination.
Suggested Procedure
I would suggest to directly work towards master and release implemented features early on as experimental to get things out early and allow people to play around. First EIP-PR (or alternatively a separate preparatory PR) needs to update the common library and in a first round add some boilerplate for berlin to have the HF keyword ready and allow for a clean HF switch in the other libraries.
There are now the first EIPs being accepted for the Berlin HF, so we can (and should) relatively imminently start working on the integration, since planned timeline is relatively dense (June: Testnets, End of June (personal estimate: won't happen, but anyhow 😄): mainnet).
This is a meta issue to help on overall planning and coordination.
Suggested Procedure
I would suggest to directly work towards
master
and release implemented features early on asexperimental
to get things out early and allow people to play around. First EIP-PR (or alternatively a separate preparatory PR) needs to update the common library and in a first round add some boilerplate forberlin
to have the HF keyword ready and allow for a clean HF switch in the other libraries.Entry Points
Tasks
General
berlin
boilerplate update on the common library similar to Draft Istanbul Support ethereumjs-common#51 to allow for clean HF switchEIPs
Testing
berlin
tests get mergedFollowing
Istanbul
HF Planning: #501The text was updated successfully, but these errors were encountered: