{"id":6385,"date":"2024-12-21T12:47:12","date_gmt":"2024-12-21T11:47:12","guid":{"rendered":"https:\/\/wsj-crypto.com\/?p=6385"},"modified":"2024-12-21T12:47:12","modified_gmt":"2024-12-21T11:47:12","slug":"ropsten-merge-a-new-era-for-ethereum-unfolds","status":"publish","type":"post","link":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/","title":{"rendered":"Ropsten Merge: A New Era for Ethereum Unfolds"},"content":{"rendered":"\n<div id=\"\">\n<ul role=\"list\" class=\"css-1onhfjo\">\n<li class=\"css-cvpopp\">Ropsten will be the initial enduring testnet to undergo The Merge<!-- --><\/li>\n<li class=\"css-cvpopp\">A fresh Ropsten Beacon Chain was initiated on May 30, 2022, to offer consensus for the network<!-- --><\/li>\n<li class=\"css-cvpopp\">The Ropsten Beacon Chain will enhance to merge-compatible protocol guidelines (Bellatrix) at slot <!-- --><strong><span class=\"chakra-text css-ons8vw\">24000<\/span><\/strong>, anticipated on June 2, 2022<!-- --><\/li>\n<li class=\"css-cvpopp\">Subsequently, a <!-- --><span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty (TTD)<\/span> will be established to trigger The Merge on the proof-of-work chain. Node Operators will be required to manually configure this value on their clients.<!-- --><\/li>\n<li class=\"css-cvpopp\"><strong>June 3 update:<!-- --><\/strong> the definitive Terminal Total Difficulty for the Ropsten Merge is <!-- --><strong><span class=\"chakra-text css-ons8vw\">50000000000000000<\/span><\/strong>. A <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2022\/06\/03\/ropsten-merge-ttd\">following announcement<!-- --><\/a> clarifies how node operators and stakers can ensure their clients are prepared for the upgrade. Kindly update your client\u2019s TTD before June 7, 2022. <!-- --><\/li>\n<\/ul>\n<p><!-- --><\/p>\n<h2 class=\"chakra-heading css-1w54o5f\" id=\"background\">Background<!-- --><\/h2>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">After extensive effort to implement proof-of-stake on Ethereum, we are now entering the concluding testing phase: testnet rollouts!<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Following trials of client versions on <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2021\/12\/20\/kintsugi-merge-testnet\">Kintsugi \ud83c\udf75<!-- --><\/a>, <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2022\/03\/14\/kiln-merge-testnet\">Kiln \ud83d\udd25\ud83e\uddf1<!-- --><\/a> and numerous <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/tim.mirror.xyz\/PWFVaHY3Mrx7srarMmuBWya0J5kioR1l2xaH3p5APDk\">shadow forks<!-- --><\/a>, client teams are now prepared to execute Ropsten &#8212; the oldest proof-of-work testnet &#8212; during The Merge. To facilitate this, a Ropsten Beacon Chain has been initiated to deliver consensus to the network.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Post the Ropsten transition, two additional testnets (Goerli and Sepolia) will be transitioned to proof-of-stake prior to shifting focus to the mainnet. Other testnets, such as Rinkeby and Kovan, may be preserved and upgraded independently by the community but will no longer be overseen by client developers.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">The Merge differs from earlier Ethereum upgrades in two significant ways. Firstly, node operators must update both their consensus and execution layer clients simultaneously, as opposed to just one. Secondly, the upgrade triggers in two stages: the first at a specific slot height on the Beacon Chain and the second when a <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-3675#terminal-total-difficulty-vs-block-number\"><span class=\"chakra-text css-ons8vw\">Total Difficulty<\/span><\/a> level is reached on the execution layer.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Considering these factors, the Ropsten network, intended to be retired post The Merge, will go through the upgrade earlier in the development timeline than previous network upgrades. This will allow the community additional time to acclimatize to the upgrade procedure.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Note<!-- --><\/strong>: Client releases listed below will <!-- --><strong>not<!-- --><\/strong> be appropriate for the Ethereum mainnet&#8217;s transition to proof-of-stake.<!-- --><\/p>\n<p><!-- --><\/p>\n<h2 class=\"chakra-heading css-1w54o5f\" id=\"upgrade-information\">Upgrade Information<!-- --><\/h2>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"timing\">Timing<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><em class=\"chakra-text css-0\">The Merge<!-- --><\/em> involves a two-step procedure. It commences with a network upgrade on the consensus layer, initiated by a slot height. This is succeeded by the execution layer&#8217;s shift from proof-of-work to proof-of-stake, triggered by a designated <!-- --><span class=\"chakra-text css-ons8vw\">Total Difficulty<\/span> limit, known as the <!-- --><span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty<\/span> (<!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span>).<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">On <!-- --><strong>June 2, 2022<!-- --><\/strong>, at slot <!-- --><strong><span class=\"chakra-text css-ons8vw\">24000<\/span><\/strong>, the <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/consensus-specs\/tree\/dev\/specs\/bellatrix\">Bellatrix<!-- --><\/a> upgrade will ready the Ropsten Beacon Chain for The Merge. At that moment, CL clients will begin monitoring for a <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span> threshold to be attained on the proof-of-work chain.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Due to the highly fluctuating hash rate of proof-of-work testnets, the <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span> will initially be set at a remarkably high figure, <!-- --><span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span>. With Ropsten&#8217;s current hash rate, it would require approximately 250 years to reach that.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Once the Bellatrix upgrade has been executed on the Beacon Chain, a new <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span> figure, which is anticipated to be achieved within a few days thereafter, will be established and publicized. <!-- --><strong>Users will then need to adjust their node with this updated value. Guidance for doing this with each client is available <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2022\/06\/03\/ropsten-merge-ttd\">here<!-- --><\/a>.<!-- --><\/strong><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">When this new <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span> is reached or surpassed on Ropsten, the execution layer aspect of the transition, codenamed <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/execution-specs\/blob\/master\/network-upgrades\/mainnet-upgrades\/paris.md\">Paris<!-- --><\/a>, will commence. Again, note that the hash rate on Ropsten is notoriously inconsistent, so the actual timing of the <!-- --><span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty<\/span> event may vary.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Once the execution layer has surpassed the <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span>, the subsequent block will be produced solely by a Beacon Chain validator. We regard The Merge as completed once the Beacon Chain has finalized this block. Given typical network circumstances, this should occur 2 epochs, or roughly 13 minutes, after the inaugural post-TTD block is achieved!<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">A new JSON-RPC block tag, <!-- --><span class=\"chakra-text css-ons8vw\">finalized<\/span>, provides the latest finalized block or an error if no such block exists post-merge. This tag can assist applications in verifying if The Merge has been actualized. Similarly, smart contracts can <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-4399#using-264-threshold-to-determine-pos-blocks\">check the <!-- --><span class=\"chakra-text css-ons8vw\">DIFFICULTY<\/span> opcode (<!-- --><span class=\"chakra-text css-ons8vw\">0x44<\/span>)<!-- --><\/a>, rebranded to <!-- --><span class=\"chakra-text css-ons8vw\">PREVRANDAO<\/span> post-merge, to ascertain if The Merge has occurred. We recommend that infrastructure providers track overall network stability in addition to finalization.status.<!-- --><\/p>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"client-releases\">Client Releases<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">The subsequent client releases facilitate The Merge on the Ropsten test network. Node operators are required to operate <!-- --><strong>both<!-- --><\/strong> an execution and consensus layer client to stay connected to the network during and after The Merge.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">As stated earlier, the upcoming releases have a fixed <!-- --><span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty<\/span> value of <!-- --><span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span>, which will need to be manually modified after the Bellatrix upgrade becomes active on the Beacon Chain.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">When selecting which client to operate, validators should particularly consider the hazards of running a majority client on both the EL and CL. An explanation of these hazards and their repercussions can be found <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/dankradfeist.de\/ethereum\/2022\/03\/24\/run-the-majority-client-at-your-own-peril.html\">here<!-- --><\/a>. An approximation of the current EL and CL client distribution and resources for transitioning from one client to another are located <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/clientdiversity.org\/\">here<!-- --><\/a>.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Note<!-- --><\/strong>: if you had earlier acquired a client release with a Ropsten TTD of <!-- --><span class=\"chakra-text css-ons8vw\">43531756765713534<\/span>, you are required to either update your release or manually override the TTD to <!-- --><span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span> as indicated <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2022\/06\/03\/ropsten-merge-ttd\">here<!-- --><\/a>.<!-- --><\/p>\n<p><!-- --><\/p>\n<h4 class=\"chakra-heading css-1u9mv6z\" id=\"consensus-layer\">Consensus Layer<!-- --><\/h4>\n<p><!-- --><\/p>\n<div class=\"css-ylxp7t\">\n<table role=\"table\" class=\"chakra-table css-nz8z8i\">\n<thead node=\"[object Object]\" class=\"css-0\">\n<tr role=\"row\" class=\"css-0\">\n<th class=\"css-aqvfe2\">Name<!-- --><\/th>\n<th class=\"css-aqvfe2\">Version<!-- --><\/th>\n<th class=\"css-aqvfe2\">Link<!-- --><\/th>\n<\/tr>\n<\/thead>\n<tbody node=\"[object Object]\" class=\"css-i54j9x\">\n<tr role=\"row\" class=\"css-0\">\n<td role=\"gridcell\" class=\"css-19nu0k5\">Lighthouse<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">Baby Wizard (2.3.0)<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/sigp\/lighthouse\/releases\/tag\/v2.3.0\">Download<!-- --><\/a><\/td>\n<\/tr>\n<tr role=\"row\" class=\"css-0\">\n<td role=\"gridcell\" class=\"css-19nu0k5\">Lodestar<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">Refer to &#8220;Lodestar Note&#8221; below<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">Refer to &#8220;Lodestar Note&#8221; below<!-- --><\/td>\n<\/tr>\n<tr role=\"row\" class=\"css-0\">\n<td role=\"gridcell\" class=\"css-19nu0k5\">Prysm<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">v2.1.3-rc.2<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/prysmaticlabs\/prysm\/releases\/tag\/v2.1.3-rc.2\">Download<!-- --><\/a><\/td>\n<\/tr>\n<tr role=\"row\" class=\"css-0\">\n<td role=\"gridcell\" class=\"css-19nu0k5\">Nimbus<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">v22.5.2<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/status-im\/nimbus-eth2\/releases\/tag\/v22.5.2\">Download<!-- --><\/a><\/td>\n<\/tr>\n<tr role=\"row\" class=\"css-0\">\n<td role=\"gridcell\" class=\"css-19nu0k5\">Teku<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">v22.5.2<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ConsenSys\/teku\/releases\/tag\/22.5.2\">Download<!-- --><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Lodestar Note:<!-- --><\/strong> the recent Lodestar release, <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ChainSafe\/lodestar\/releases\/tag\/v0.37.0\">v0.37.0<!-- --><\/a>, possesses an outdated Ropsten TTD value of <!-- --><span class=\"chakra-text css-ons8vw\">43531756765713534<\/span>. To ensure compatibility with the Ropsten Merge, which currently employs a TTD of <!-- --><span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span>, Lodestar users must manually set this value. Guidelines on how to do this are available on the team&#8217;s <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.chainsafe.io\/lodestar-v0-37-0-bopsten-ready-release-231d185e3e1e\">release announcement page<!-- --><\/a>.<!-- --><\/p>\n<p><!-- --><\/p>\n<h4 class=\"chakra-heading css-1u9mv6z\" id=\"execution-layer\">Execution Layer<!-- --><\/h4>\n<p><!-- --><\/p>\n<div class=\"css-ylxp7t\">\n<table role=\"table\" class=\"chakra-table css-nz8z8i\">\n<thead node=\"[object Object]\" class=\"css-0\">\n<tr role=\"row\" class=\"css-0\">\n<th class=\"css-aqvfe2\">Name<!-- --><\/th>\n<th class=\"css-aqvfe2\">Version<!-- --><\/th>\n<th class=\"css-aqvfe2\">Link<!-- --><\/th>\n<\/tr>\n<\/thead>\n<tbody node=\"[object Object]\" class=\"css-i54j9x\">\n<tr role=\"row\" class=\"css-0\">\n<td role=\"gridcell\" class=\"css-19nu0k5\">Besu<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">v22.4.2<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/hyperledger\/besu\/releases\/tag\/22.4.2\">Download<!-- --><\/a><\/td>\n<\/tr>\n<tr role=\"row\" class=\"css-0\">\n<td role=\"gridcell\" class=\"css-19nu0k5\">Erigon<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">v2022.06.01-alpha<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ledgerwatch\/erigon\/releases\/tag\/v2022.06.01\">Download<!-- --><\/a><\/td>\n<\/tr>\n<tr role=\"row\" class=\"css-0\">\n<td role=\"gridcell\" class=\"css-19nu0k5\">go-ethereum (geth)<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">Refer to &#8220;Geth Note&#8221; below<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">Refer to &#8220;Geth Note&#8221; below<!-- --><\/td>\n<\/tr>\n<tr role=\"row\" class=\"css-0\">\n<td role=\"gridcell\" class=\"css-19nu0k5\">Nethermind<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">v1.13.1<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/NethermindEth\/nethermind\/releases\/tag\/1.13.1\">Download<!-- --><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Geth Note:<!-- --><\/strong> the most recent go-ethereum (geth) release, <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/go-ethereum\/releases\/tag\/v1.10.18\">Sharblu (v1.10.18)<!-- --><\/a>, has an outdated Ropsten TTD value of <!-- --><span class=\"chakra-text css-ons8vw\">43531756765713534<\/span>. To achieve compatibility with the Ropsten Merge, which now utilizes a TTD of <!-- --><span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span>, geth users need to either:<!-- --><\/p>\n<p><!-- --><\/p>\n<ul role=\"list\" class=\"css-1onhfjo\">\n<li class=\"css-cvpopp\">Compile from source on the latest <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/go-ethereum\/tree\/master\"><span class=\"chakra-text css-ons8vw\">master<\/span> branch<!-- --><\/a><\/li>\n<li class=\"css-cvpopp\">Utilize the latest <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/cloud.docker.com\/u\/ethereum\/repository\/docker\/ethereum\/client-go\">Docker image<!-- --><\/a><\/li>\n<li class=\"css-cvpopp\">Manually override the TTD, via running the following command when initiating the&#8220;`html<br \/>\n<!-- --><span class=\"chakra-text css-ons8vw\">&#8211;override.terminaltotaldifficulty 100000000000000000000000.<\/span><\/li>\n<\/ul>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"upgrade-specifications\">Upgrade Specifications<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Crucial consensus alterations for The Merge are outlined in two locations:<!-- --><\/p>\n<p><!-- --><\/p>\n<ul role=\"list\" class=\"css-1onhfjo\">\n<li class=\"css-cvpopp\">The consensus layer alterations, located under the <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/consensus-specs\/tree\/dev\/specs\/bellatrix\"><span class=\"chakra-text css-ons8vw\">bellatrix<\/span> directory<!-- --><\/a> of the consensus-specs repository<!-- --><\/li>\n<li class=\"css-cvpopp\">The execution layer alterations, found under the <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/execution-specs\/blob\/master\/network-upgrades\/mainnet-upgrades\/paris.md\"><span class=\"chakra-text css-ons8vw\">Paris<\/span> spec<!-- --><\/a> in the execution-specs repository<!-- --><\/li>\n<\/ul>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Besides these, two additional specifications address how the consensus and execution layer clients engage:<!-- --><\/p>\n<p><!-- --><\/p>\n<ul role=\"list\" class=\"css-1onhfjo\">\n<li class=\"css-cvpopp\">The Engine API, defined in the <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/execution-apis\/tree\/main\/src\/engine\">execution-apis repository<!-- --><\/a>, facilitates communication between the consensus and execution layers<!-- --><\/li>\n<li class=\"css-cvpopp\">Optimistic Sync, detailed in the <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/consensus-specs\/blob\/dev\/sync\/optimistic.md\"><span class=\"chakra-text css-ons8vw\">sync<\/span><\/a> folder of the consensus-specs repository, is utilized by the consensus layer to incorporate blocks while the execution layer client is syncing and to provide a partial perspective of the head of the chain from the former to the latter<!-- --><\/li>\n<\/ul>\n<p><!-- --><\/p>\n<h2 class=\"chakra-heading css-1w54o5f\" id=\"faq\">FAQ<!-- --><\/h2>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"as-a-node-operator-what-should-i-do\">As a node operator, what actions should I take?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Following the merge, an Ethereum full node will integrate a consensus layer client, responsible for operating the proof-of-stake Beacon Chain, along with an execution layer client that oversees the user state and processes the computations linked to transactions. These layers communicate through an authenticated port using a new array of JSON RPC methods labeled the <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/execution-apis\/tree\/main\/src\/engine\">Engine API<!-- --><\/a>. The EL and CL clients authenticate one another using a JWT secret. <!-- --><strong>Node operators should consult their clients&#8217; documentation for guidelines on generating and configuring these.<!-- --><\/strong><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">In simpler terms, if you were previously operating a node on the Beacon Chain, you must now also run an execution layer client. Likewise, if you operated a node on the current proof-of-work network, you will need to deploy a consensus layer client. For secure communication, a JWT token needs to be transferred to each client.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">It is critical to note that while both are incorporated into consensus layer client releases, operating a Beacon Node is separate from managing a Validator Client. Stakers must operate both, but node operators need only the former. <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/docs.ethhub.io\/ethereum-roadmap\/ethereum-2.0\/eth-2.0-client-architecture\/\">This post<!-- --><\/a> clarifies the distinction between both components further.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Also, be aware that each layer will sustain a distinct set of peers and present its own APIs. The <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/beacon-apis\">Beacon<!-- --><\/a> and <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/execution-apis\">JSON RPC<!-- --><\/a> APIs will continue functioning as anticipated.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Finally, remember to return on June 3rd for a notification on this blog regarding the final Ropsten TTD value.<!-- --><\/strong><\/p>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"as-a-staker-what-do-i-need-to-do\">As a staker, what actions do I need to perform?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">As previously mentioned, <!-- --><strong>validators on the Beacon Chain must run an execution layer client subsequent to The Merge, in addition to their consensus layer clients.<!-- --><\/strong> Before the merge, while this was highly suggested, validators could have delegated these functions to external providers. This was feasible because the execution layer only required data updates to the deposit contract.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Post-merge, validators must ensure that transactions in blocks they produce and endorse are accurate. To accomplish this, every beacon node has to be paired with an execution layer client. Remember, multiple validators can still associate with a single beacon node &amp; execution layer client combination. While this expands the validators&#8217; duties, it further entitles a validator proposing a block to receive the associated transaction priority fees (currently awarded to miners).<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">While validator rewards accumulate on the Beacon Chain and will necessitate a subsequent network upgrade for withdrawal, transaction fees will persist in being paid, burned, and allocated on the execution layer. Validators can designate any Ethereum address as a recipient for transaction fees.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>After updating your consensus client, ensure to configure the <!-- --><span class=\"chakra-text css-ons8vw\">fee recipient<\/span> within your validator client settings, to guarantee transaction fees are directed to an address under your control.<!-- --><\/strong><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">If you have staked through a third-party provider, it is the responsibility of your chosen provider to clarify how these fees are distributed.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Testnet upgrades are the last opportunity for validators to verify their configurations operate as intended and to rectify any issues. Information regarding running a validator on the Ropsten Beacon Chain in preparation for The Merge can be accessed on the <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/ropsten.launchpad.ethereum.org\/en\/\">Ropsten staking launchpad<!-- --><\/a>.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">We strongly encourage mainnet validators to practice through The Merge on Ropsten and other testnets before the Ethereum mainnet transitions to proof-of-stake.<!-- --><\/p>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"as-an-application-or-tooling-developer-what-should-i-do\">As an application or tooling developer, what actions should I take?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">With The Merge being implemented on Ropsten, it&#8217;s vital to ensure that your product functions as anticipated throughout the proof-of-stake transition and in a post-merge environment. As described in a <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2021\/11\/29\/how-the-merge-impacts-app-layer\">prior post<!-- --><\/a>, The Merge will have a minimal influence on a segment of contracts deployed on Ethereum, none of which should encounter disruptions. Moreover, the majority of user API endpoints<br \/>\n&#8220;`remain consistent (unless you utilize proof-of-work specific techniques such as <!-- --><span class=\"chakra-text css-ons8vw\">eth_getWork<\/span>).<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">That being said, the majority of applications on Ethereum encompass significantly more than solely on-chain contracts. <!-- --><strong>Now is the moment<!-- --><\/strong> to verify that your front-end code, tools, deployment pipeline, and other off-chain elements function as expected. We highly suggest that developers conduct a comprehensive testing &amp; deployment cycle on Ropsten (or <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2022\/03\/14\/kiln-merge-testnet\">Kiln<!-- --><\/a>) and report any concerns regarding tools or dependencies to the maintainers of those projects. If you are uncertain about where to report an issue, please utilize <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/eth-clients\/merge-testnets\/\">this repository<!-- --><\/a>.<!-- --><\/p>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"as-an-ethereum-user-or-ether-holder-is-there-anything-i-need-to-do\">As an Ethereum user or Ether holder, is there anything I should do?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">No. The Ethereum mainnet remains unaffected by this testnet. Future announcements will be made on this blog prior to the mainnet&#8217;s transition.<!-- --><\/p>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"as-a-miner-is-there-anything-i-need-to-do\">As a miner, is there any action I must take?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">No. If you are mining on the Ethereum mainnet or Ropsten, you should be aware that each network will function entirely on proof-of-stake following The Merge. At that point, mining will no longer be feasible on the network.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">This is anticipated around June 8, 2022 on Ropsten and later in the year for the Ethereum mainnet.<!-- --><\/p>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"as-a-validator-can-i-withdraw-my-stake\">As a validator, can I withdraw my stake?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">No. The Merge is the most intricate upgrade to Ethereum to date. To reduce the risks of network interruptions, a minimalistic approach has been adopted which excludes any non-transition alterations from this upgrade.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Withdrawals from the Beacon Chain are expected to be introduced in the first upgrade following The Merge. Specifications for both the <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/consensus-specs\/issues\/2758\">consensus<!-- --><\/a> and <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-4895\">execution<!-- --><\/a> layers are currently ongoing.<!-- --><\/p>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"i-have-more-questions-where-can-i-ask-them\">I have additional questions; where can I inquire?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">A <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/pm\/issues\/532\">Merge Community Call<!-- --><\/a> is planned for June 3, 14:00 UTC. Client developers and researchers will be present to address inquiries from node operators, stakers, infrastructure &amp; tooling providers, and community members.<!-- --><\/p>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"wen-merge\">When is the merge?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">At the time of this post&#8217;s publication, the date for the Ethereum mainnet proof-of-stake transition has <!-- --><strong>not<!-- --><\/strong> been established. Any sources claiming otherwise are likely deceptive. Updates will be shared on this blog. Please remain cautious!<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Assuming no issues arise with Ropsten, once client testing concludes, Ethereum&#8217;s other testnets will proceed with The Merge. Once Goerli and Sepolia have successfully transitioned and stabilized, a specific slot height will be determined for the Bellatrix upgrade on the Beacon Chain, and a <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-3675#terminal-total-difficulty-vs-block-number\">difficulty value<!-- --><\/a> will be established for the mainnet transition. Clients will then release updates that enable The Merge on mainnet. These announcements will occur on this blog and in various community publications.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">This scenario assumes no issues are discovered. Nevertheless, if problems are identified at any stage of the process or if testing coverage is deemed inadequate, these matters will be resolved before advancing with the deployment procedures.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Only then will it be feasible to approximate the precise date for The Merge.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">In other terms, \ud83d\udd1c.<!-- --><\/p>\n<\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/blog.ethereum.org\/en\/2022\/05\/30\/ropsten-merge-announcement\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ropsten will be the initial enduring testnet to undergo The Merge A fresh Ropsten Beacon Chain was initiated on May 30, 2022, to offer consensus for the network The Ropsten Beacon Chain will enhance to merge-compatible protocol guidelines (Bellatrix) at slot 24000, anticipated on June 2, 2022 Subsequently, a Terminal Total Difficulty (TTD) will be<\/p>\n","protected":false},"author":3,"featured_media":6386,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23],"tags":[521],"class_list":{"0":"post-6385","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ethereum","8":"tag-return-a-list-of-comma-separated-tags-from-this-title-ropsten-merge-announcement-ethereum-foundation-blog"},"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.3 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Ropsten Merge: A New Era for Ethereum Unfolds - WSJ-Crypto<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/\" \/>\n<meta property=\"og:locale\" content=\"it_IT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Ropsten Merge: A New Era for Ethereum Unfolds - WSJ-Crypto\" \/>\n<meta property=\"og:description\" content=\"Ropsten will be the initial enduring testnet to undergo The Merge A fresh Ropsten Beacon Chain was initiated on May 30, 2022, to offer consensus for the network The Ropsten Beacon Chain will enhance to merge-compatible protocol guidelines (Bellatrix) at slot 24000, anticipated on June 2, 2022 Subsequently, a Terminal Total Difficulty (TTD) will be\" \/>\n<meta property=\"og:url\" content=\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/\" \/>\n<meta property=\"og:site_name\" content=\"WSJ-Crypto\" \/>\n<meta property=\"article:published_time\" content=\"2024-12-21T11:47:12+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_7edef98ba154912a7bb4f57c2dd74bc8.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2100\" \/>\n\t<meta property=\"og:image:height\" content=\"900\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"wsjcrypto\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Scritto da\" \/>\n\t<meta name=\"twitter:data1\" content=\"wsjcrypto\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tempo di lettura stimato\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minuti\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/\",\"url\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/\",\"name\":\"Ropsten Merge: A New Era for Ethereum Unfolds - WSJ-Crypto\",\"isPartOf\":{\"@id\":\"https:\/\/wsj-crypto.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_7edef98ba154912a7bb4f57c2dd74bc8.jpg\",\"datePublished\":\"2024-12-21T11:47:12+00:00\",\"author\":{\"@id\":\"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7\"},\"breadcrumb\":{\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#breadcrumb\"},\"inLanguage\":\"it-IT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#primaryimage\",\"url\":\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_7edef98ba154912a7bb4f57c2dd74bc8.jpg\",\"contentUrl\":\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_7edef98ba154912a7bb4f57c2dd74bc8.jpg\",\"width\":2100,\"height\":900},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/wsj-crypto.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Ropsten Merge: A New Era for Ethereum Unfolds\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/wsj-crypto.com\/#website\",\"url\":\"https:\/\/wsj-crypto.com\/\",\"name\":\"WSJ-Crypto\",\"description\":\"Just Another Crypto News Website\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/wsj-crypto.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"it-IT\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7\",\"name\":\"wsjcrypto\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/wsj-crypto.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/86fe8af82ea089646d6639ca2f87e0243d8688d957bd8e3ec22ec3c457cc16d4?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/86fe8af82ea089646d6639ca2f87e0243d8688d957bd8e3ec22ec3c457cc16d4?s=96&d=mm&r=g\",\"caption\":\"wsjcrypto\"},\"url\":\"https:\/\/wsj-crypto.com\/index.php\/author\/wsjcrypto\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Ropsten Merge: A New Era for Ethereum Unfolds - WSJ-Crypto","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/","og_locale":"it_IT","og_type":"article","og_title":"Ropsten Merge: A New Era for Ethereum Unfolds - WSJ-Crypto","og_description":"Ropsten will be the initial enduring testnet to undergo The Merge A fresh Ropsten Beacon Chain was initiated on May 30, 2022, to offer consensus for the network The Ropsten Beacon Chain will enhance to merge-compatible protocol guidelines (Bellatrix) at slot 24000, anticipated on June 2, 2022 Subsequently, a Terminal Total Difficulty (TTD) will be","og_url":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/","og_site_name":"WSJ-Crypto","article_published_time":"2024-12-21T11:47:12+00:00","og_image":[{"width":2100,"height":900,"url":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_7edef98ba154912a7bb4f57c2dd74bc8.jpg","type":"image\/jpeg"}],"author":"wsjcrypto","twitter_card":"summary_large_image","twitter_misc":{"Scritto da":"wsjcrypto","Tempo di lettura stimato":"11 minuti"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/","url":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/","name":"Ropsten Merge: A New Era for Ethereum Unfolds - WSJ-Crypto","isPartOf":{"@id":"https:\/\/wsj-crypto.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#primaryimage"},"image":{"@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#primaryimage"},"thumbnailUrl":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_7edef98ba154912a7bb4f57c2dd74bc8.jpg","datePublished":"2024-12-21T11:47:12+00:00","author":{"@id":"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7"},"breadcrumb":{"@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#breadcrumb"},"inLanguage":"it-IT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/"]}]},{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#primaryimage","url":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_7edef98ba154912a7bb4f57c2dd74bc8.jpg","contentUrl":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_7edef98ba154912a7bb4f57c2dd74bc8.jpg","width":2100,"height":900},{"@type":"BreadcrumbList","@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/21\/ropsten-merge-a-new-era-for-ethereum-unfolds\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/wsj-crypto.com\/"},{"@type":"ListItem","position":2,"name":"Ropsten Merge: A New Era for Ethereum Unfolds"}]},{"@type":"WebSite","@id":"https:\/\/wsj-crypto.com\/#website","url":"https:\/\/wsj-crypto.com\/","name":"WSJ-Crypto","description":"Just Another Crypto News Website","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/wsj-crypto.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"it-IT"},{"@type":"Person","@id":"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7","name":"wsjcrypto","image":{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/wsj-crypto.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/86fe8af82ea089646d6639ca2f87e0243d8688d957bd8e3ec22ec3c457cc16d4?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/86fe8af82ea089646d6639ca2f87e0243d8688d957bd8e3ec22ec3c457cc16d4?s=96&d=mm&r=g","caption":"wsjcrypto"},"url":"https:\/\/wsj-crypto.com\/index.php\/author\/wsjcrypto\/"}]}},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts\/6385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/comments?post=6385"}],"version-history":[{"count":2,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts\/6385\/revisions"}],"predecessor-version":[{"id":6388,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts\/6385\/revisions\/6388"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/media\/6386"}],"wp:attachment":[{"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/media?parent=6385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/categories?post=6385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/tags?post=6385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}