TL;DR
- Berlin is set for deployment!
- We’re progressing quickly: the initial testnet to upgrade, Ropsten, is slated to refresh on March 10th. Mainnet is planned for April 15th.
- If you’re operating an Ethereum node, you ought to update it to a Berlin-compatible version ASAP for testnets and prior to April 7th for mainnet.
- Refer below for the compilation of Berlin-compatible client versions and information regarding the EIPs incorporated in the upgrade.
- The Besu client has identified a bug in their earlier Berlin release. Besu users should upgrade to version 21.1.2.
Berlin Timing
Following extensive preparations, Berlin has finally arrived! The upgrade, which succeeds the Istanbul and Muir Glacier upgrades, is set to activate on the Ethereum mainnet at block 12,244,000. We anticipate this will occur around Wednesday, April 15, 2021, but due to fluctuating block times, the precise date may vary.
Before launching on mainnet, the upgrade will be initiated on the Ropsten, Goerli, and Rinkeby testnets. The comprehensive release timeline is as follows:
| Network | Block Number | Anticipated Date |
|---|---|---|
| Ropsten | 9,812,189 | 10 Mar 2021 |
| Goerli | 4,460,644 | 17 Mar 2021 |
| Rinkeby | 8,290,928 | 24 Mar 2021 |
| Mainnet | 12,244,000 | 15 Apr 2021 |
Ethereum node operators must update their nodes before the fork block on the networks they wish to partake in. Due to fluctuations in block time, it is advisable to upgrade several days ahead of the anticipated date. Refer to the section below for the recommended client versions to upgrade to.
Client Versions
To ensure compatibility with the Berlin upgrade, node operators must update the client version they are using. The versions listed below for each client, support Berlin across all Ethereum networks, including both testnets and mainnet.
Note that the Besu team has reported a bug in their 21.1.1 release pertaining to Berlin (link). Besu users are urged to upgrade to the 21.1.2 release to stay compliant with Berlin. Moreover, TurboGeth will not present a client release ready for the initial testnets, but will have one before mainnet. We will revise this post as their release is made available. Trinity is now obsolete and will not be participating in the Berlin upgrade.
Berlin EIPs
The Berlin upgrade brings the following EIPs to the Ethereum ecosystem:
For further information on each EIP, check out the Ethereum Cat Herder’s Berlin Overview post.
FAQ
Why “Berlin”?
Following Istanbul, we exhausted our choices of names for our planned network upgrades. It was proposed to utilize Devcon city names for these upgrades, and we embraced this idea! Berlin is the location of Devcon 0, and the subsequent upgrade will be named London, where Devcon 1 was held.
As an Ethereum user or Ether holder, is there anything I need to do?
If you utilize an exchange (such as Coinbase, Kraken, or Binance), a web wallet service (such as Metamask, MyCrypto, or MyEtherWallet), a mobile wallet service (such as Coinbase Wallet, Status.im, or Trust Wallet), or a hardware wallet (such as Ledger, Trezor, or KeepKey), there is nothing you need to do unless instructed to take additional measures by your exchange or wallet provider.
As a node operator or miner, what actions should I take?
Download the most recent version of your Ethereum client, as specified in the table above.
What transpires if I am a miner or node operator and fail to participate in the upgrade?
If you are running an Ethereum client that is not updated to the latest version (as listed above), your client will synchronize to the pre-fork blockchain once the upgrade takes place. You will be relegated to an incompatible chain adhering to the previous rules, and you will be unable to send Ether or function on the upgraded Ethereum network.
What constitutes a network upgrade in Ethereum-land?
A network upgrade refers to a modification in the underlying Ethereum protocol, instating new rules to enhance the system. The decentralized characteristic of blockchain systems complicates a network upgrade. Successful network upgrades in a blockchain necessitate collaboration and communication with the community, as well as the developers of various Ethereum clients to ensure a smooth transition.
What occurs during a network upgrade?
Once the community reaches a consensus regarding which modifications should be included in the upgrade, changes to the protocol are documented in the multiple Ethereum clients, such as geth, Open Ethereum, Besu, and Nethermind. The protocol changes are activated at a designated block number. Any nodes that have not been upgraded to the new ruleset will be left behind on the old chain, where the previous rules still apply.
Thank You!
A heartfelt thanks to the Ethereum community and all Ethereum developers across all clients and platforms for collaborating to provide insights, ideas, and contributions towards Berlin 😁🇩🇪
Now, let’s move on to London 🇬🇧!
Disclaimer
This is a rapidly evolving and highly technical domain. If you opt to implement the suggestions in this post and continue to engage, ensure you comprehend how it affects you. You should recognize that risks are involved, including but not limited to unanticipated bugs. By choosing to follow these recommendations, you solely accept the risks associated with the outcomes. This post and its suggestions are not a sale of any sort and do not establish any warranties of any kind, including but not limited to anything associated with the Ethereum network or the Ethereum clients mentioned herein.
