Berlin Hardfork Planning

[holgerd77]

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

• EIP-2070 Berlin HF Meta EIP (canonical source)
• eth.wiki Berlin Roadmap
• GitHub ethereum/pm "Berlin" search
• ACD 84, Decisions on EIP-2537, EIP-2315

Tasks

General

• [x] Preparatory berlin boilerplate update on the common library similar to https://github.com/ethereumjs/ethereumjs-common/pull/51 to allow for clean HF switch

EIPs

• [x] EIP-2315 Simple Subroutines for the EVM, Issue https://github.com/ethereumjs/ethereumjs-vm/issues/737
• [x] EIP-2537 BLS12-381 Curve Operation Precompiles, Issue https://github.com/ethereumjs/ethereumjs-vm/issues/738

Testing

• [x] Update ethereumjs-testing to a latest (currently still pre-Berlin) state of the official ethereum/tests and integrate on the VM, see https://github.com/ethereumjs/ethereumjs-testing/issues/44
• [ ] Further ethereumjs-testing upgrades and integration once berlin tests get merged
• [ ] Follow discussion on test improvements (see e.g. ACD 84 section, eventually join planned test call

Following Istanbul HF Planning: #501

[holgerd77]

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]

Closed by #1151