Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Berlin Hardfork Planning #736

Closed
4 of 6 tasks
holgerd77 opened this issue May 1, 2020 · 2 comments
Closed
4 of 6 tasks

Berlin Hardfork Planning #736

holgerd77 opened this issue May 1, 2020 · 2 comments

Comments

@holgerd77
Copy link
Member

holgerd77 commented May 1, 2020

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.

Entry Points

Tasks

General

EIPs

Testing

Following Istanbul HF Planning: #501

@holgerd77
Copy link
Member Author

Taking over from a chat comment from @jochem-brouwer:

https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%20101.md#1d-final-gono-go-for-berlin-eips

EIPs which seem to be confirmed for Berlin are 2565, 2315, 2929, 2930, and 2718

We'd need 2565, 2930, 2718

Comment would need to be integrated in the issue TODO list

@holgerd77
Copy link
Member Author

Closed by #1151

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant