- all Final Total Difficulty (TTD) ~ Of 50000000000000000 Selected for Ropsten Merge.
- Stakers and node operators manually TTD On both execution and consensus layer clients Before June 7, 2022.
- The proof-of-work testnet may have an unstable hash rate, and the exact timing of the merge in Ropsten is difficult to predict with precision. Assuming there are no unexpected hash rate fluctuations, we expect the merge to occur as follows: June 8-9, 2022.
- Synchronizing execution layer clients in Ropsten can take several hours to several days. essential Run The Merge.
background
Earlier this week, the Ropsten testnet switched to proof-of-stake. It was announced. Because the hash rate of the Proof-of-Work testnet is unstable, client releases supporting upgrades were configured using artificially high hash rates. Final Total Difficulty (TTD). This ensures that merges cannot run before the Ropsten beacon chain is ready.
in yesterday’s slot 24000, the Bellatrix upgrade has been activated on the Ropsten Beacon Chain, making the network ready to run through The Merge. new TTD value 50000000000000000 Selected to trigger a conversion.
Node operators and stakers must update this manually. TTD Before the network reaches this total difficulty, it places value on both execution and consensus layer clients. The current network total difficulty is part of the block header and can be obtained by querying the node or visiting the block explorer.
Assuming there are no unexpected changes in the network hash rate, we expect to reach this total difficulty value. TTD It is expected to be exceeded around June 8-9, 2022.
Ropsten merge client version
To perform the final total difficulty override, node operators and stakers must be running the following client version or a newer version: Consensus and execution layer clients must be fully synchronized before merging, which can take execution layer clients hours to days.
consensus layer
execution layer
Ignore final total difficulty
Activating The Merge in a timely manner requires overrides by node operators and stakers. both Execution and consensus layer clients Final Total Difficulty (TTD) give value 50000000000000000.
Instructions for each client are as follows:
execution layer
besut
- If you are using a TOML configuration file, add the following line:
override-genesis-config=(“terminalTotalDifficulty=50000000000000000”) - Alternatively, add the following flag when starting the node using the CLI:
–override-genesis-config=”terminalTotalDifficulty=50000000000000000″
Eragon
- Add the following flag when starting node using the CLI: –override.terminaltotaldifficulty=50000000000000000
Gothereum(geth)
- Add the following flag when starting node using the CLI: –override.terminaltotaldifficulty50000000000000000
nethermind
- Add the following flag when starting node using the CLI: –Merge.TerminalTotalDifficulty 50000000000000000
- This can also be set in the client’s settings. configuration file or environment variables, Terminal overall difficulty level give value 50000000000000000
consensus layer
Lighthouse
- Add the following flag when starting node using the CLI: –terminal-total-difficulty-override=50000000000000000
lodestar
- Add the following flag when starting node using the CLI: –terminal-total-difficulty-override 50000000000000000
- For more information, see: this blog post.
cloud
- Add the following flags when starting node using the CLI: –terminal-total-difficulty-override=50000000000000000
prism
- Add the following flag when starting node using the CLI: –terminal-total-difficulty-override 50000000000000000
- This also config.yaml by updating the file TOTAL_TERMINAL_DIFFICULTY Place the values in the configuration directory and restart the client.
ocean
- Add the following flag when starting node using the CLI: –Xnetwork-total-terminal-difficulty-override=50000000000000000
frequently asked questions
What do I do as a node operator or staker?
As mentioned in Ropsten Merge AnnouncementRopsten’s node operators and stakers must update their execution and consensus layer clients to the versions listed above or the latest version.
Once this is done, node operators and stakers will need to manually override Ropsten. Final Total Difficulty (TTD) value Both execution and consensus layer clients Use the commands listed above.
Finally, ensure that both execution and consensus layer clients are fully synchronized before merging. For execution tier clients, this may take up to several days.
What should I do as an application or tool developer?
With The Merge now live on Ropsten, it’s time to verify that the product is working as expected with Proof-of-Stake conversion and post-merge context. As explained in previous post, a merge has minimal impact on a subset of contracts deployed on Ethereum, none of which must be violated. Additionally, most of the user API endpoints remain stable (unless you use proof-of-work specific methods, such as: eth_getWork).
That said, most applications on Ethereum involve much more than on-chain contracts. Now is the time to ensure that your front-end code, tools, deployment pipelines, and other off-chain components are working as intended. We recommend that the developer Ropsten (or kiln) Report any issues related to tools or dependencies to the maintainer for that project. If you are not sure where to open the issue, use: this repository.
Is there anything I need to do as an Ethereum user or Ethereum holder?
no. The Ethereum mainnet is not affected by this testnet. Follow-up announcements will be made through this blog before the mainnet transition.
Is there anything I need to do as a miner?
no. If you mine on the Ethereum mainnet or Ropsten, you should know that each network will operate entirely on Proof-of-Stake after The Merge. At that point mining will no longer be possible on the network.
It is expected to launch on Ropsten around June 8-9, 2022, and on the Ethereum mainnet later this year.
Do you want to merge?
As of the time this post was published, the Ethereum mainnet Proof-of-Stake conversion date is as follows: ~ no It’s set. Any source that claims otherwise is likely a scam. Updates will be posted on this blog. Stay safe!
Assuming no issues are found in Ropsten, Ethereum’s other testnets will run through The Merge once client testing is complete. Once Goerli and Sepolia are successfully converted and stabilized, a slot height for the Bellatrix upgrade on the beacon chain is selected and Final total difficulty value Set up for mainnet transition. The client then makes a release that activates The Merge on the mainnet. These will be announced through this blog and other community publications. The image below shows this process.
This assumes that all steps proceed as expected. If issues are discovered at any point in the process or test coverage is determined to be insufficient, these issues are addressed before continuing with the deployment process.
Only then can we estimate the exact date of The Merge.
In other words 🔜.