Ethereum’s Berlin Upgrade is Here: Key Details Released

Summary

• Berlin is set to launch!
• We’re progressing quickly: the initial testnet to upgrade, Ropsten, is set for March 10th. The mainnet upgrade is anticipated on April 15th.
• If you’re operating an Ethereum node, please upgrade to a Berlin-compatible version immediately for testnets and before April 7th for mainnet.
• Refer below for a list of Berlin-compatible client versions and details on the included EIPs in the upgrade.
• The Besu client has identified a bug in their prior Berlin release. Users of Besu should update to version 21.1.2.

Berlin Timeline

After extensive planning, Berlin is here! This upgrade, following the Istanbul and Muir Glacier upgrades, is projected to be activated on the Ethereum mainnet at block 12,244,000. We estimate this to occur around April 15, 2021, but the exact date may vary due to block time inconsistencies.

Before the mainnet deployment, the upgrade will first launch on the Ropsten, Goerli, and Rinkeby testnets. Below is the full release schedule:

Ethereum node operators must update their nodes prior to the fork block on the networks in which they wish to engage. Due to block time unpredictability, it’s advisable to update several days before the expected date. Check the section below for the suitable client versions to upgrade to.

Compatible Client Versions

To ensure compatibility with the Berlin upgrade, node operators need to upgrade the client version they are using. The versions listed below for each client are compatible with Berlin across all Ethereum networks, including testnets and mainnet.

Please note, the Besu team has acknowledged a bug in their 21.1.1 release related to Berlin (link). Besu users are advised to upgrade to version 21.1.2 to ensure compatibility with Berlin. Additionally, TurboGeth will not have a release ready for the initial testnets but is expected to provide an update before the mainnet launch. We will revise this post as their release becomes available. Trinity is no longer supported and will not be participating in the Berlin upgrade.

Berlin EIPs

The Berlin upgrade brings the following EIPs to the Ethereum network:

For further details on each EIP, check out the Ethereum Cat Herders’ Berlin Overview article.

Frequently Asked Questions

Why name it “Berlin”?

After Istanbul, we ran out of names for scheduled network upgrades. Using city names from Devcon was suggested for upgrades, and we embraced this idea! Berlin is where Devcon 0 was held, and the succeeding upgrade will be named London, the site of Devcon 1.

As an Ethereum user or Ether holder, do I need to take any action?

If you utilize an exchange (like 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 (like Ledger, Trezor, or KeepKey), you do not need to take any action unless specifically instructed by your exchange or wallet service.

As a node operator or miner, what steps should I take?

Make sure to download the latest version of your Ethereum client as outlined in the table above.

What will happen if I am a miner or node operator and do not participate in the upgrade?

If you’re using a client version that isn’t updated to the latest (as listed above), your client will only sync to the pre-fork blockchain after the upgrade. You will find yourself on an incompatible chain adhering to the older protocols, making it impossible to send Ether or operate on the upgraded Ethereum network.

What does a network upgrade mean in Ethereum?

A network upgrade signifies an adjustment to the Ethereum protocol, establishing new rules to enhance the system. The decentralized aspect of blockchain technology complicates network upgrades. Effective network upgrades necessitate collaboration and communication with both the community and developers of various Ethereum clients to ensure a smooth transition.

What occurs during a network upgrade?

Once a consensus is reached within the community regarding the changes to incorporate into the upgrade, those protocol adjustments are programmed into the different Ethereum clients such as geth, Open Ethereum, Besu, and Nethermind. The protocol modifications are activated at a designated block number. Any nodes that haven’t upgraded to the new rule set will be left on the old chain, where previous rules persist.

We Appreciate You!

A heartfelt thanks to the Ethereum community and all Ethereum developers across all platforms who collaborated to provide insights, feedback, and contributions for Berlin

Next up, it’s London !

Disclaimer

This field is rapidly evolving and highly technical. If you opt to follow the suggestions in this post and continue your involvement, please ensure you comprehend how they affect you. Be mindful that there are risks involved, including but not limited to the potential for unexpected bugs. By choosing to implement these recommendations, you independently assume the risks associated. This post and its recommendations do not constitute a sale of any sort, nor do they create any warranties, including but not limited to those related to the Ethereum network or the Ethereum clients mentioned herein.