{"id":42226,"date":"2022-06-08T17:48:26","date_gmt":"2022-06-08T17:48:26","guid":{"rendered":"https:\/\/harchi90.com\/ethereums-merge-upgrade-goes-live-today-on-ropsten-testnet\/"},"modified":"2022-06-08T17:48:26","modified_gmt":"2022-06-08T17:48:26","slug":"ethereums-merge-upgrade-goes-live-today-on-ropsten-testnet","status":"publish","type":"post","link":"https:\/\/harchi90.com\/ethereums-merge-upgrade-goes-live-today-on-ropsten-testnet\/","title":{"rendered":"Ethereum’s Merge Upgrade Goes Live Today on Ropsten Testnet"},"content":{"rendered":"
\n

Ethereum’s Merge \u2014 the blockchain’s much-anticipated transition from its current proof-of-work<\/span> (PoW) mechanism to a proof-of-stake<\/span> (PoS) consensus algorithm \u2014 will be one step closer today if the planned trial upgrade on the Ropsten public testnet goes as planned later today.<\/p>\n

First rolled out in 2016, Ropsten is Ethereum’s oldest testnet that allows for blockchain development testing before deployment on the mainnet. Similar to other testnets, it is identical to the mainnet, with the key difference that no \u201creal\u201d funds are at risk if any technical issues occur.<\/p>\n

The date for the upgrade was first announced on May 18 when Ethereum core developer Terence Tsao broke the news<\/a> that configuration for Ropsten’s Beacon Chain \u2014 a PoS network that runs alongside Ethereum’s mainnet \u2014 had been merged and client releases should be expected soon.<\/p>\n

<\/p>\n

Things moved quickly after that, with another Ethereum developer, Tim Beiko, announcing<\/a> the launch of a new beacon chain on May 30, and the Bellatrix upgrade \u2014 one of the two required conditions for the Ropsten testnet Merge\u2014activated<\/a> on June 2.<\/p>\n

The developers also had to decide on the so-called \u201cTerminal Total Difficulty\u201d (TTD) \u2014a pre-decided difficulty value at which the Ropsten Merge occurs, something they did the following day setting the value at 50 quadrillion.<\/p>\n

As explained<\/a> by Beiko, such a high value was chosen “because of the low PoW hash rate on testnets, and the risk of The Merge having happened before the network was ready with the Bellatrix update.”<\/p>\n

\n
\n

\ud83d\udce3 Ropsten Merge Update \ud83d\udce3<\/p>\n

As mentioned in the Ropsten Merge Announcement, the terminal total difficulty (TTD) at which The Merge happens on Ropsten must be overridden by node operators & stakers. <\/p>\n

The correct TTD value is 50000000000000000 \ud83d\udc40https: \/\/t.co\/aPAWNJfDYh<\/p>\n

– Tim Beiko | timbeiko.eth \ud83d\udc3c (@TimBeiko) June 3, 2022<\/a><\/p>\n<\/blockquote>\n<\/div>\n

Per the Ethereum Foundation’s blog post, client software teams participating in the Ropsten Merge include Lighthouse, Lodestar, Prysm, Nimbus, Teku, Besu, Erigon, go-ethereum (geth) and Nethermind.<\/p>\n

<\/p>\n

What’s next?<\/h2>\n

Today’s Ropsten Merge is a crucial step before Ethereum’s actual transition to the Consensus Layer (formerly known as ETH 2.0) slated for August this year.<\/p>\n

In essence, it gives developers the first taste of what things will look like in the future when Ethereum finally makes the move to a less energy-intensive PoS algorithm mechanism. And it’s quite clear that a successful Merge on the testnet would bode well for the Ethereum’s mainnet’s own transition.<\/p>\n

<\/p>\n

“Merging Ropsten is a huge testing milestone towards Ethereum’s mainnet Merge later this year,” Ethereum Core developer Preston van Loon wrote<\/a> last month.<\/p>\n

This process has been in the works for some years though, with multiple delays sending waves of frustration among the community and investors.<\/p>\n

The new PoS model is supposed to solve some of Ethereum’s biggest issues, such as high transaction costs and the network’s ability to scale, so the stakes are indeed high, with the biggest upgrade in Ethereum’s history \u2014 if successful\u2014 having a good chance to become the crypto industry’s event of the year.<\/p>\n

\n
\n

Want to be a crypto expert? Get the best of Decrypt straight to your inbox.<\/h3>\n
\n
\n