TL;DR
- Berlin is ready to be deployed!
- We are moving fast: Ropsten, the first testnet to be upgraded, is scheduled to be upgraded on March 10th. Mainnet is scheduled for April 15th.
- If you are running an Ethereum node, you should upgrade to the Berlin-compatible version as soon as possible for testnet and before April 7 for mainnet.
- See below for a list of Berlin-compatible client versions and details about the EIPs included in the upgrade.
- Besu client Reported a bug From the previous Berlin release. Besu users should upgrade to version 21.1.2.
berlin timing
After months of planning, Berlin is finally here! The resulting upgrade is Istanbul and muir glacier The upgrade is scheduled to take place on Ethereum mainnet block 12 244 000. This is expected to occur around Wednesday April 15, 2021, but the exact date may change due to block time fluctuations.
Before being deployed to mainnet, the upgrade will be applied to the Ropsten, Goerli and Rinkeby testnets. The full release schedule is as follows:
| network | block number | due date |
|---|---|---|
| Robston | 9 812 189 | March 10, 2021 |
| Görli | 4 460 644 | March 17, 2021 |
| Rinkebi | 8 290 928 | March 24, 2021 |
| mainnet | 12244000 | April 15, 2021 |
Ethereum node operators must upgrade their nodes before a fork block occurs on the network they wish to participate in. Due to block time fluctuations, we recommend updating a few days before the expected date. See the section below for the appropriate client version to upgrade to.
client version
To be compatible with the Berlin upgrade, node operators must upgrade the client version they run. The versions listed below for each client support Berlin as a whole. every The Ethereum network, including both testnet and mainnet.
FYI, the Besu team reported a bug in the 21.1.1 release related to Berlin (link). Besu users must upgrade to release 21.1.2 to maintain compatibility with Berlin. Additionally, TurboGeth is not preparing a client release for the first testnet, but plans to release one before mainnet. We will update this post once the release is available. Trinity is now deprecated and does not support the Berlin upgrade.
Berlin EIP
The Berlin Upgrade introduces the following EIPs to the Ethereum network:
To learn more about each EIP, see Ethereum Cat Herder’s. Berlin overview post.
frequently asked questions
Why “Berlin”?
After Istanbul, there was a lack of names for planned network upgrades. It was suggested to use Devcon city names for the upgrade., and we stuck with it! where is berlin Devcon 0 The next upgrade will be called London where Devcon 1 took place.
Is there anything I need to do as an Ethereum user or Ethereum holder?
If you use an exchange (Coinbase, Kraken, Binance, etc.), a web wallet service (Metamask, MyCrypto, MyEtherWallet, etc.), a mobile wallet service (Coinbase Wallet, Status.im, Trust Wallet, etc.), or a hardware wallet (e.g. Ledger, Trezor, etc.) If you use KeepKey, you don’t need to take any action unless you are instructed to do so by your exchange or wallet service.
What do I do as a node operator or miner?
Download the latest version of the Ethereum client as listed in the table above.
What happens if I’m a miner or node operator and don’t participate in the upgrade?
If you are using an Ethereum client that has not been updated to the latest version (listed above), your client will be in sync with the prefork blockchain when the upgrade occurs. Depending on the existing rules, you will be stuck on an incompatible chain and will not be able to send Ether or operate on the Ethereum network after the upgrade.
What is Ethereum Land’s network upgrade?
Network upgrades are changes to the underlying Ethereum protocol to create new rules to improve the system. The decentralized nature of blockchain systems makes network upgrades more difficult. To ensure a smooth network upgrade of the blockchain, collaboration and communication are required with the community as well as various Ethereum client developers.
What happens during a network upgrade?
After the community reaches a consensus on what changes should be included in the upgrade, protocol changes are recorded in various Ethereum clients such as geth, Open Ethereum, Besu, and Nethermind. Protocol changes are activated at specific block numbers. Any nodes that are not upgraded to the new rule set will be discarded from the old chain where the old rules still exist.
thank you!
A huge thank you to all Ethereum developers from all clients and platforms who came together to provide their opinions, thoughts and contributions to the Ethereum community and Berlin 😁🇩🇪
Now to London 🇬🇧!
disclaimer
This is an emerging, evolving, highly technological space. If you decide to implement the recommendations in this post and remain engaged, you need to understand how this affects you. You should understand that this involves risks, including but not limited to risks such as unexpected bugs. If you choose to implement these recommendations, you solely assume the risk of the results. This post and recommendations are not a sale of any kind, nor do they create any endorsement of any kind, including but not limited to anything related to the Ethereum network or the Ethereum clients mentioned herein.