“`html
\n<\/p>\n
<\/p>\n
<\/p>\n
Earlier this week, the transition of the Ropsten testnet to proof-of-stake was revealed<\/a>. Due to the variability in hash rate on proof-of-work testnets, client releases supporting the upgrade were set up using an artificially elevated Terminal Total Difficulty (TTD)<\/span>. This was to guarantee that The Merge could not be initiated until the Ropsten Beacon Chain was prepared.<\/p>\n <\/p>\n Yesterday, at slot 24000<\/span>, the Bellatrix upgrade was activated on the Ropsten Beacon Chain, setting the stage for the network to execute The Merge. A new TTD<\/span> value of 50000000000000000<\/span><\/strong> has been established to initiate the transition.<\/p>\n <\/p>\n Node operators & stakers are required to manually adjust this TTD<\/span> value on both their execution and consensus layer clients before the network attains this total difficulty.<\/strong> The present network total difficulty is included in the block header and can be retrieved by querying your node or utilizing a block explorer.<\/p>\n <\/p>\n Assuming no unexpected alterations in network hash rate, we foresee this total difficulty value being reached, and TTD<\/span> to be surpassed, around June 8-9, 2022.<\/p>\n <\/p>\n <\/p>\n In order to implement the Terminal Total Difficulty modification, node operators and stakers must operate the following client versions or newer editions. Note that both the consensus and execution layer clients have to be completely synced ahead of The Merge, and that execution layer clients might require several hours to days for this process.<\/p>\n <\/p>\n <\/p>\n To activate The Merge at the correct moment, node operators and stakers must override both<\/strong> their execution and consensus layer clients’ Terminal Total Difficulty (TTD)<\/span> value to 50000000000000000<\/span><\/strong>.<\/p>\n <\/p>\n Here are instructions for accomplishing this with each client:<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n As noted in the Ropsten Merge Announcement<\/a>, node operators & stakers on Ropsten are required to upgrade their execution and consensus layer clients to the versions specified above or newer versions.<\/p>\n <\/p>\n After that, node operators & stakers are obliged to manually set the Ropsten Terminal Total Difficulty (TTD)<\/span> value on both their execution and consensus layer client<\/strong> utilizing the commands provided earlier.<\/p>\n <\/p>\n Finally, ensure that both your execution and consensus layer clients are fully synchronized prior to The Merge. This synchronizing process may take several days for execution layer clients.<\/p>\n <\/p>\n <\/p>\n With The Merge now active on Ropsten, it’s crucial to verify that your product operates correctly through the proof-of-stake transition and in a post-merge scenario. As detailed in a past article<\/a>, The Merge will minimally affect a limited number of contracts deployed on Ethereum, with none expected to malfunction. Furthermore, the majority of user API endpoints will remain stable (unless you are using proof-of-work specific methods such as eth_getWork<\/span>).<\/p>\n <\/p>\n That being said, most applications on Ethereum comprise much more than just on-chain contracts. Now is the moment to confirm that your front-end code, tooling, deployment pipeline, and other off-chain elements function as intended. We strongly advise developers to conduct a full testing & deployment cycle on Ropsten (or Kiln<\/a>) and report any issues with tools or dependencies to the maintainers of those projects. If you are uncertain where to raise an issue, please utilize this repository<\/a>.<\/p>\n <\/p>\n <\/p>\n No. The Ethereum mainnet is unaffected by this testnet. Future announcements will be made on this blog prior to the mainnet’s transition.<\/p>\n <\/p>\n <\/p>\n No. If you are mining on the Ethereum mainnet or Ropsten, it is important to note that both networks will function entirely under proof-of-stake after The Merge. Consequently, mining will no longer be viable on the network.<\/p>\n <\/p>\n This transition is anticipated around June 8-9, 2022 on Ropsten and later in the year for the Ethereum mainnet.<\/p>\n <\/p>\n <\/p>\n At the time of publishing this article, the date for the Ethereum mainnet’s proof-of-stake transition has not<\/strong> yet been determined. Any source claiming otherwise is likely a scam. Updates will be shared on this blog. Please stay vigilant!<\/p>\n <\/p>\n Assuming no problems are encountered with Ropsten, once client testing is completed, Ethereum’s other testnets will proceed with The Merge. After Goerli and Sepolia have successfully transitioned and stabilized, a slot height will be selected for the Bellatrix upgrade on the Beacon Chain and a terminal total difficulty value<\/a> will be established for the mainnet transition. Following this, clients will release updates that enable The Merge on the mainnet. These announcements will be made on this blog and in other community publications. The image below depicts this procedure:<\/p>\n <\/p>\n \n <\/p>\n Note that this assumes every step proceeds as planned. If any issues arise at any point during the process or if test coverage is deemed insufficient, they will be addressed before continuing with the deployment process.<\/p>\n <\/p>\n Only then will it be feasible to estimate the precise date for The Merge.<\/p>\n <\/p>\n In other words, \ud83d\udd1c.<\/p>\n<\/div>\nRopsten Merge Client Versions<\/h2>\n
Consensus Layer<\/h3>\n
\n<\/p>\nExecution Layer<\/h3>\n
\n<\/p>\nTerminal Total Difficulty Override<\/h2>\n
Execution Layer<\/h3>\n
Besu<\/h4>\n
\n
\noverride-genesis-config=[“terminalTotalDifficulty=50000000000000000”]<\/span><\/li>\n
\n–override-genesis-config=”terminalTotalDifficulty=50000000000000000″<\/span><\/li>\n<\/ul>\nErigon<\/h4>\n
\n
Go-Ethereum (geth)<\/h4>\n
\n
Nethermind<\/h4>\n
\n
Consensus Layer<\/h3>\n
Lighthouse<\/h4>\n
\n
Lodestar<\/h4>\n
\n
Nimbus<\/h4>\n
\n
Prysm<\/h4>\n
\n
Teku<\/h4>\n
\n
FAQ<\/h2>\n
As a node operator or staker, what should be my actions?<\/h3>\n
As an application or tooling developer, what should my course of action be?<\/h3>\n
As an Ethereum user or Ether holder, is there any action required from me?<\/h3>\n
As a miner, is there any course of action I need to take?<\/h3>\n
wen merge?<\/h3>\n