- Berlin is ready to start deployment!
- We are moving fast: The first testnet to be upgraded, Ropsten, is scheduled to be upgraded on March 10. Mainnet is scheduled to be released on April 15.
- If you are running an Ethereum node, you should upgrade to the Berlin-compatible version ASAP for the testnet, and upgrade to this version before April 7th for the mainnet.
- Please refer to the list of Berlin compatible client versions below and the details of the EIP included in the upgrade.
- Besu customers have Reported an error In their previous Berlin release. Besu users should upgrade to version 21.1.2.
After months of planning, Berlin is finally here! After the upgrade, Istanbul with Muir Glacier The upgrade is planned to be launched on the 12 244 000 block of the Ethereum mainnet. We expect this to happen around April 15, 2021 (Wednesday), but due to the variability of block time, the exact date may change.
Before being deployed on the mainnet, the upgrade will be carried out on the Ropsten, Goerli and Rinkeby testnets. The entire release schedule is as follows:
|The internet||Block number||Due date|
|Roppsten||9812189||March 10, 2021|
|Gerry||4460644||March 17, 2021|
|Linkby||8290928||March 24, 2021|
|Mainnet||12244 000||April 15, 2021|
Ethereum node operators should upgrade their nodes before the derivative blocks on the network they want to join. Due to the variability of block time, it is recommended to update a few days before the expected date. Please refer to the following section for the corresponding client version to upgrade to.
In order to be compatible with the Berlin upgrade, node operators will need to upgrade the client version they are running.The version listed below for each customer supports all parts of Berlin All Ethereum network, including testnet and mainnet.
|client||version number||Download link|
|Ethereum (fka parity)||3.2.0||download|
|Ethereum Virtual Machine||v5.2.0||download|
Please note that the Besu team reported a Berlin-related bug in its version 21.1.1 (Associate). Besu users should upgrade to version 21.1.2 to maintain compatibility with Berlin. In addition, TurboGeth is not yet able to prepare a client version for the first testnet, but will release a version before the mainnet. As their release becomes available, we will update this post. Trinity is now deprecated and will not support the Berlin upgrade.
The Berlin upgrade introduced the following EIPs to the Ethereum network:
To learn more about each EIP, see Ethereum Cat Herder’s Berlin overview.
After Istanbul, our name has been used up and the planned network upgrade is not possible. It is recommended to use the Devcon city name to upgrade, Let’s keep going!Where is berlin Devcon 0 Happened, the next upgrade will be called London, and Devcon 1 will take place in London.
As an Ethereum user or Ethereum holder, what do I need to do?
If you use an exchange (such as Coinbase, Kraken or Binance), web wallet services (such as Metamask, MyCrypto or MyEtherWallet), mobile wallet services (such as Coinbase Wallet, Status.im or Trust Wallet), or hardware wallets (such as Ledger, Trezor) Or KeepKey), unless the exchange or wallet service tells you to take other steps, you don’t need to take any action.
As a node operator or miner, what do I need to do?
As shown in the table above, download the latest version of the Ethereum client.
What if I am a miner or node operator but do not participate in the upgrade?
If you are using the Ethereum client that has not been updated to the latest version (listed above), after the upgrade occurs, your client will be synchronized to the pre-fork blockchain. Following the old rules, you will be stuck on an incompatible chain and will not be able to send Ether or operate on the upgraded Ethereum network.
What is the network upgrade in the Ethereum area?
The network upgrade is a change to the underlying Ethereum protocol, which creates new rules to improve the system. The decentralized nature of the blockchain system makes network upgrades more difficult. The network upgrade in the blockchain requires cooperation and communication with the community and various Ethereum client developers to make the transition smooth.
What will happen during the network upgrade?
After the community has reached an agreement on what changes should be included in the upgrade, the changes to the agreement will be written to various Ethereum clients, such as geth, Open Ethereum, Besu, and Nethermind. The protocol change is activated at a specific block number. All nodes that have not been upgraded to the new rule set will be discarded on the old chain, and the previous rules will continue to exist.
Thank you very much to the Ethereum community and all the Ethereum developers who take the customer as the platform for their opinions, ideas and contributions to Berlin 😁🇩🇪
Now, to London🇬🇧!
This is a new and evolving high-tech field. If you choose to implement the recommendations in this article and continue to participate, you should make sure you understand how it affects you. You should understand that the risks involved include, but are not limited to, risks such as accidental errors. By choosing to implement these recommendations, you alone risk the consequences. This article and advice is not a sale of any kind, nor does it provide any form of guarantee, including but not limited to anything related to the Ethereum network or the Ethereum customers mentioned here.