Ethereum's Ropsten proof-of-stake 'test merge' goes live

Quick Take

  • Developers merged Ropsten’s proof-of-work chain with its proof-of-stake beacon chain on Wednesday afternoon.
  • The goal of the testnet merge was to prepare for Ethereum’s mainnet merge, set to take place sometime later this year.

In preparation for the Ethereum merge happening later this year, developers have activated the merge on the Ropsten test network.

The merge took place on Wednesday afternoon after the move was first announced on June 3.

Ropsten’s proof-of-work chain was merged with its proof-of-stake beacon chain by combining their codes into one. Today’s merge is critical to check if client software using Ethereum nodes performs without any glitches. Client software teams participated in the merge including Lighthouse, Lodestar, Prysm, Teku, Besu, Erigon, go-ethereum (geth) and Nethermind.

The same process is set to happen later this year with the Ethereum mainnet merge, for which a date has not yet been set. In effect, today's event was intended to serve as a major practice session for the mainnet merge, which will see Ethereum transition from proof-of-work consensus to proof-of-stake.

"I mean of course, the merge working well for 6 hours isn’t evidence of complete success," said Vitalik Buterin, co-founder of Ethereum, in the livestream earlier today. "There are all of these kind of longer term issues around MEV and staking centralization and protection against DOS attacks and things that could potentially bite us 3 weeks after the merge instead of 2 minutes during the process."

Previous tests included 10 shadow forks on the main network in April and another merge on Kiln, another testnet. 

Today's test is measured by a metric called terminal total difficulty. The merge is considered activated once this level of block difficulty is reached on the proof of work version. The proof-of-work version of Ropsten crossed a pre-set 50 quadrillion measure to protect the merge from any malicious activity by artificially acquiring the hashrate.

Before the activation of the merge, node operators had to manually configure their clients to override the Ropsten Terminal Total Difficulty for both the proof-of-stake version and proof-of-stake clients, as explained by The Block’s Vishal Chawla in an explainer published Tuesday.


© 2024 The Block. All Rights Reserved. This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.

About Author

Anushree covers how U.S. businesses and corporations are moving into crypto. She has written about business and tech for Bloomberg, Newsweek, Insider, and others. Reach out on Twitter @anu__dave