.jpg)
- The Sepolia testnet will undergo a post-merge execution layer (EL) upgrade at the cluster 1735371expected on August 17, 2022
- The upgrade will disconnect EL clients on the network from peers that have not moved to Proof of Stake. It does not add additional functionality after that.
- Sepolia node operators must upgrade their execution layer client before blocking 1735371.
- A similar upgrade is expected on Goerli and the Ethereum mainnet once these networks move to proof-of-stake
background
In order to maintain a healthy list of peers, nodes on the implementation layer in Ethereum will automatically disconnect peers that do not have the same upgrade sequence as them. On the Ethereum mainnet, this means checking if a peer has been upgraded to Melting boundaries At mass 200,000, then Homestead At block 1,150,000, and so on until the last upgrade, Gray glacierwhich occurred at block 15,050,000. EIP-2124 Specifies how to deal with this. In typical network upgrades, which are triggered by block height, this happens automatically as nodes use the block height of upcoming upgrades to filter out peers.
For the merge, this was not possible because the upgrade was run using a file Complete difficulty value instead of block number. The justification for this choice is explained in EIP-3675:
Using a predetermined block number for a hard fork is unsafe in this context since PoS fork selection takes priority during the transfer process.
An attacker may use a minority of hash power to create a malicious chain fork that meets block height requirements. The first Proof of Stake (PoS) block may then be maliciously proposed on top of the Proof of Work (PoW) block of this hostile fork, becoming the head and undermining the security of the transfer.
To protect the network from this attack scenario, the difficulty accumulated by the chain (total difficulty) is used to initiate the upgrade.
To minimize changes to the protocol during its most complex upgrade since launch, The Merge’s design excluded EIP-2124 compatibility. This means that an additional upgrade must now be made to add this. It is important to note that the only change introduced as part of this upgrade is the block number limitation that nodes can use to identify which peers have gone through the merge process. No other functionality is introduced or deprecated as part of this upgrade.
Upgrade information
timing
This upgrade will happen in Sepolia at the block 1735371expected on August 17, 2022.
Note that a similar upgrade will be announced for Goerli and the mainnet after these networks move to proof-of-stake.
Will Robsten no He is promoted because he is now considered deprecated, along with Rinkeby and Kiln. be seen This post For more details about their deprecation table.
Customer versions
Only implementation layer clients need to be updated for this upgrade. Node operators can continue to run their existing consensus layer client version on Sepolia during the transition.
Note that the client versions used for Gurley/Prater All support for this upgrade is integrated into Sepolia. In other words, if you have already downloaded a version to integrate Goerli/Prater, you can use the same version on Sepolia for this upgrade.
Implementation layer
Upgrade specifications
The specifications for this change are tracked as part of Paris Specifications, below Next upgrade fork to divide.
Instructions
As a node operator, what should I do?
You must upgrade your implementation layer client to one of the above versions before August 16, 2022. Your consensus layer client does not need to be upgraded.
As a stakeholder, what should I do?
Validator set to Sepolia is allowed. If you are part of existing Sepolia validators, you must update your implementation layer client to one of the above versions by August 16, 2022 at the latest.
If you are not part of the current Sepolia verification suite, you do not need to do anything at this time.
Validators on Goerli/Prater and the main network will need to follow the same steps when announcing this upgrade on those networks.
As an app or tool developer, what should I do?
Nothing, unless you are also running a node. If so, please upgrade your implementation layer client to one of the above versions before August 16, 2022.
As an Ethereum user or Ethereum holder, is there anything I should do?
No, the Ethereum mainnet is not affected by this upgrade. Even when this upgrade is applied to the main network, no action will be required.
Thank you Justin Crone For the original cover image and Tomo Saito for the edits.
