{"id":17986,"date":"2026-03-06T03:40:42","date_gmt":"2026-03-06T03:40:42","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/03\/06\/ropsten-merge-announcement-ethereum-foundation-blog\/"},"modified":"2026-03-06T03:40:42","modified_gmt":"2026-03-06T03:40:42","slug":"ropsten-merge-announcement-ethereum-foundation-blog","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/03\/06\/ropsten-merge-announcement-ethereum-foundation-blog\/","title":{"rendered":"Ropsten Merge Announcement | Ethereum Foundation Blog"},"content":{"rendered":"<p> <br \/>\n<br \/><img decoding=\"async\" src=\"https:\/\/blog.ethereum.org\/images\/posts\/upload_7edef98ba154912a7bb4f57c2dd74bc8.jpg\" \/><\/p>\n<div id=\"\">\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">Ropsten will be the first longstanding testnet to run through The Merge<\/li>\n<li class=\"css-0\">A new Ropsten Beacon Chain was launched on May 30, 2022 to provide consensus to the network<\/li>\n<li class=\"css-0\">The Ropsten Beacon Chain will upgrade to merge-compatible protocol rules (Bellatrix) at slot <strong><span class=\"chakra-text css-ons8vw\">24000<\/span><\/strong>, expected on June 2, 2022<\/li>\n<li class=\"css-0\">After this, a <span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty (TTD)<\/span> will be chosen to activate The Merge on the proof-of-work chain. Node Operators will need to manually set this value on their clients.<\/li>\n<li class=\"css-0\"><strong>June 3 update:<\/strong> the exact Terminal Total Difficulty for the Ropsten Merge is <strong><span class=\"chakra-text css-ons8vw\">50000000000000000<\/span><\/strong>. A <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2022\/06\/03\/ropsten-merge-ttd\">subsequent announcement<\/a> explains how node operators and stakers can ensure their clients are ready for the upgrade. Please update your client\u2019s TTD before June 7, 2022. <\/li>\n<\/ul>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"background\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"background permalink\" href=\"#background\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Background<\/h2>\n<p class=\"chakra-text css-gi02ar\">After years of work to bring proof-of-stake to Ethereum, we are now entering the final testing stage: testnet deployments!<\/p>\n<p class=\"chakra-text css-gi02ar\">Having tested client implementations on <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2021\/12\/20\/kintsugi-merge-testnet\">Kintsugi \ud83c\udf75<\/a>, <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2022\/03\/14\/kiln-merge-testnet\">Kiln \ud83d\udd25\ud83e\uddf1<\/a> and many <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/tim.mirror.xyz\/PWFVaHY3Mrx7srarMmuBWya0J5kioR1l2xaH3p5APDk\">shadow forks<\/a>, client teams are now ready to run Ropsten &#8212; the oldest proof-of-work testnet &#8212; through The Merge. In preparation, a Ropsten Beacon Chain has been launched to provide consensus to the network.<\/p>\n<p class=\"chakra-text css-gi02ar\">After the Ropsten transition, two more testnets (Goerli and Sepolia) will be transitioned to proof-of-stake before focus shifts to mainnet. Other testnets, such as Rinkeby and Kovan, may be maintained and upgraded separately by the community but will no longer be monitored by client developers.<\/p>\n<p class=\"chakra-text css-gi02ar\">The Merge is different from previous Ethereum upgrades in two ways. First, node operators need to update both their consensus and execution layer clients in tandem, rather than just one of the two. Second, the upgrade activates in two phases: the first at a slot height on the Beacon Chain and the second upon hitting a <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-3675#terminal-total-difficulty-vs-block-number\"><span class=\"chakra-text css-ons8vw\">Total Difficulty<\/span><\/a> value on the execution layer.<\/p>\n<p class=\"chakra-text css-gi02ar\">Given these circumstances, the Ropsten network, which is intended to be deprecated after The Merge, will run through the upgrade earlier in the development process than previous network upgrades. This will give the community more time to become familiar with the upgrade process.<\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Note<\/strong>: Client releases listed below will <strong>not<\/strong> be suitable for the Ethereum mainnet&#8217;s transition to proof-of-stake.<\/p>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"upgrade-information\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"upgrade information permalink\" href=\"#upgrade-information\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Upgrade Information<\/h2>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"timing\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"timing permalink\" href=\"#timing\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Timing<\/h3>\n<p class=\"chakra-text css-gi02ar\"><em class=\"chakra-text css-0\">The Merge<\/em> is a two-step process. It starts with a network upgrade on the consensus layer, triggered by a slot height. This is followed by the execution layer&#8217;s transition from proof-of-work to proof-of-stake, triggered by a specific <span class=\"chakra-text css-ons8vw\">Total Difficulty<\/span> threshold, called the <span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty<\/span> (<span class=\"chakra-text css-ons8vw\">TTD<\/span>).<\/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-vezwxf\" href=\"https:\/\/github.com\/ethereum\/consensus-specs\/tree\/dev\/specs\/bellatrix\">Bellatrix<\/a> upgrade will prepare the Ropsten Beacon Chain for The Merge. At that point, CL clients will begin listening for a <span class=\"chakra-text css-ons8vw\">TTD<\/span> value to be hit on the proof-of-work chain.<\/p>\n<p class=\"chakra-text css-gi02ar\">Because the hash rate of proof-of-work testnets is very volatile, the <span class=\"chakra-text css-ons8vw\">TTD<\/span> value will first be set to an exceedingly high value, <span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span>. At Ropsten&#8217;s current hash rate, it would take ~250 years to reach it.<\/p>\n<p class=\"chakra-text css-gi02ar\">Once the Bellatrix upgrade has happened on the Beacon Chain, a new <span class=\"chakra-text css-ons8vw\">TTD<\/span> value, which is expected to be reached a few days later, will be chosen and announced. <strong>Users will then need to configure their node with this new value. Instructions for doing so with each client are available <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2022\/06\/03\/ropsten-merge-ttd\">here<\/a>.<\/strong><\/p>\n<p class=\"chakra-text css-gi02ar\">When this new <span class=\"chakra-text css-ons8vw\">TTD<\/span> is hit or exceeded on Ropsten, the execution layer part of the transition, codenamed <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/execution-specs\/blob\/master\/network-upgrades\/mainnet-upgrades\/paris.md\">Paris<\/a>, will start. Again, note that hash rate on Ropsten is notoriously variable, so the actual time at which the <span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty<\/span> takes place may fluctuate.<\/p>\n<p class=\"chakra-text css-gi02ar\">Once the execution layer has exceeded the <span class=\"chakra-text css-ons8vw\">TTD<\/span>, the next block will be solely produced by a Beacon Chain validator. We consider The Merge to have been completed once the Beacon Chain has finalized this block. Assuming normal network conditions, this should happen 2 epochs, or approximately 13 minutes, after the first post-TTD block is hit!<\/p>\n<p class=\"chakra-text css-gi02ar\">A new JSON-RPC block tag, <span class=\"chakra-text css-ons8vw\">finalized<\/span>, returns the latest finalized block or an error if no such post-merge block exists. This tag can be used for applications to check if The Merge has been completed. Similarly, smart contracts can <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-4399#using-264-threshold-to-determine-pos-blocks\">query the <span class=\"chakra-text css-ons8vw\">DIFFICULTY<\/span> opcode (<span class=\"chakra-text css-ons8vw\">0x44<\/span>)<\/a>, renamed to <span class=\"chakra-text css-ons8vw\">PREVRANDAO<\/span> post-merge, to determine if The Merge has happened. We recommend infrastructure providers monitor overall network stability in addition to finalization status.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"client-releases\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"client releases permalink\" href=\"#client-releases\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Client Releases<\/h3>\n<p class=\"chakra-text css-gi02ar\">The following client releases support The Merge on the Ropsten testnet. Node operators must run <strong>both<\/strong> an execution and consensus layer client to remain on the network during and after The Merge.<\/p>\n<p class=\"chakra-text css-gi02ar\">As mentioned above, the following releases have a hardcoded <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 updated after the Bellatrix upgrade has been activated on the Beacon Chain.<\/p>\n<p class=\"chakra-text css-gi02ar\">When choosing which client to run, validators should be especially mindful of the risks of running a majority client on both the EL and CL. An explainer of these risks and their consequences can be found <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/dankradfeist.de\/ethereum\/2022\/03\/24\/run-the-majority-client-at-your-own-peril.html\">here<\/a>. An estimate of current EL and CL client distribution and guides for switching from one client to another can be found <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/clientdiversity.org\/\">here<\/a>.<\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Note<\/strong>: if you had previously downloaded a client release with a Ropsten TTD of <span class=\"chakra-text css-ons8vw\">43531756765713534<\/span>, you must either update your release or manually override the TTD to <span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span> as specified <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2022\/06\/03\/ropsten-merge-ttd\">here<\/a>.<\/p>\n<h4 class=\"chakra-heading group css-qm6a1\" id=\"consensus-layer\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"consensus layer permalink\" href=\"#consensus-layer\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Consensus Layer<\/h4>\n<div class=\"css-ylxp7t\">\n<table class=\"chakra-table css-nz8z8i\">\n<thead class=\"css-0\">\n<tr class=\"css-0\">\n<th class=\"css-b6vxtn\">Name<\/th>\n<th class=\"css-b6vxtn\">Version<\/th>\n<th class=\"css-b6vxtn\">Link<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"css-i54j9x\">\n<tr class=\"css-0\">\n<td class=\"css-3c0snn\">Lighthouse<\/td>\n<td class=\"css-3c0snn\">Baby Wizard (2.3.0)<\/td>\n<td class=\"css-3c0snn\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/sigp\/lighthouse\/releases\/tag\/v2.3.0\">Download<\/a><\/td>\n<\/tr>\n<tr class=\"css-0\">\n<td class=\"css-3c0snn\">Lodestar<\/td>\n<td class=\"css-3c0snn\">See &#8220;Lodestar Note&#8221; below<\/td>\n<td class=\"css-3c0snn\">See &#8220;Lodestar Note&#8221; below<\/td>\n<\/tr>\n<tr class=\"css-0\">\n<td class=\"css-3c0snn\">Prysm<\/td>\n<td class=\"css-3c0snn\">v2.1.3-rc.2<\/td>\n<td class=\"css-3c0snn\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/prysmaticlabs\/prysm\/releases\/tag\/v2.1.3-rc.2\">Download<\/a><\/td>\n<\/tr>\n<tr class=\"css-0\">\n<td class=\"css-3c0snn\">Nimbus<\/td>\n<td class=\"css-3c0snn\">v22.5.2<\/td>\n<td class=\"css-3c0snn\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/status-im\/nimbus-eth2\/releases\/tag\/v22.5.2\">Download<\/a><\/td>\n<\/tr>\n<tr class=\"css-0\">\n<td class=\"css-3c0snn\">Teku<\/td>\n<td class=\"css-3c0snn\">v22.5.2<\/td>\n<td class=\"css-3c0snn\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ConsenSys\/teku\/releases\/tag\/22.5.2\">Download<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p class=\"chakra-text css-gi02ar\"><strong>Lodestar Note:<\/strong> the latest Lodestar release, <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ChainSafe\/lodestar\/releases\/tag\/v0.37.0\">v0.37.0<\/a>, has an outdated Ropsten TTD value of <span class=\"chakra-text css-ons8vw\">43531756765713534<\/span>. To be compatible with the Ropsten Merge, which now uses a TTD of <span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span>, Lodestar users will need to manually override this value. Instructions about doing so can be found on the team&#8217;s <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.chainsafe.io\/lodestar-v0-37-0-bopsten-ready-release-231d185e3e1e\">release announcement post<\/a>.<\/p>\n<h4 class=\"chakra-heading group css-qm6a1\" id=\"execution-layer\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"execution layer permalink\" href=\"#execution-layer\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Execution Layer<\/h4>\n<div class=\"css-ylxp7t\">\n<table class=\"chakra-table css-nz8z8i\">\n<thead class=\"css-0\">\n<tr class=\"css-0\">\n<th class=\"css-b6vxtn\">Name<\/th>\n<th class=\"css-b6vxtn\">Version<\/th>\n<th class=\"css-b6vxtn\">Link<\/th>\n<\/tr>\n<\/thead>\n<tbody class=\"css-i54j9x\">\n<tr class=\"css-0\">\n<td class=\"css-3c0snn\">Besu<\/td>\n<td class=\"css-3c0snn\">v22.4.2<\/td>\n<td class=\"css-3c0snn\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/hyperledger\/besu\/releases\/tag\/22.4.2\">Download<\/a><\/td>\n<\/tr>\n<tr class=\"css-0\">\n<td class=\"css-3c0snn\">Erigon<\/td>\n<td class=\"css-3c0snn\">v2022.06.01-alpha<\/td>\n<td class=\"css-3c0snn\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ledgerwatch\/erigon\/releases\/tag\/v2022.06.01\">Download<\/a><\/td>\n<\/tr>\n<tr class=\"css-0\">\n<td class=\"css-3c0snn\">go-ethereum (geth)<\/td>\n<td class=\"css-3c0snn\">See &#8220;Geth Note&#8221; below<\/td>\n<td class=\"css-3c0snn\">See &#8220;Geth Note&#8221; below<\/td>\n<\/tr>\n<tr class=\"css-0\">\n<td class=\"css-3c0snn\">Nethermind<\/td>\n<td class=\"css-3c0snn\">v1.13.1<\/td>\n<td class=\"css-3c0snn\"><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/NethermindEth\/nethermind\/releases\/tag\/1.13.1\">Download<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p class=\"chakra-text css-gi02ar\"><strong>Geth Note:<\/strong> the latest go-ethereum (geth) release, <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" 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 be compatible with the Ropsten Merge, which now uses a TTD of <span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span>, geth users must either:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">Build from source on the latest <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/go-ethereum\/tree\/master\"><span class=\"chakra-text css-ons8vw\">master<\/span> branch<\/a><\/li>\n<li class=\"css-0\">Use the latest <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/cloud.docker.com\/u\/ethereum\/repository\/docker\/ethereum\/client-go\">Docker image<\/a><\/li>\n<li class=\"css-0\">Manually override the TTD, by running the following command when starting the client: <span class=\"chakra-text css-ons8vw\">&#8211;override.terminaltotaldifficulty 100000000000000000000000.<\/span><\/li>\n<\/ul>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"upgrade-specifications\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"upgrade specifications permalink\" href=\"#upgrade-specifications\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>Upgrade Specifications<\/h3>\n<p class=\"chakra-text css-gi02ar\">Consensus-critical changes for The Merge are specified in two places:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">The consensus layer changes, under the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" 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-0\">The execution layer changes, under the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" 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 class=\"chakra-text css-gi02ar\">In addition to these, two other specifications cover how the consensus and execution layer clients interact:<\/p>\n<ul role=\"list\" class=\"css-1ars4k6\">\n<li class=\"css-0\">The Engine API, specified in the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/execution-apis\/tree\/main\/src\/engine\">execution-apis repository<\/a>, is used for communication between the consensus and execution layers<\/li>\n<li class=\"css-0\">Optimistic Sync, specified in the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" 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 used by the consensus layer to import blocks as the execution layer client is syncing and to provide a partial view of the head of the chain from the former to the latter<\/li>\n<\/ul>\n<h2 class=\"chakra-heading group css-1kpzc4q\" id=\"faq\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"faq permalink\" href=\"#faq\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>FAQ<\/h2>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-a-node-operator-what-should-i-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as a node operator what should i do permalink\" href=\"#as-a-node-operator-what-should-i-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As a node operator, what should I do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">Post-merge, an Ethereum full node will combine a consensus layer client, which runs the proof-of-stake Beacon Chain, and an execution layer client, which manages the user-state and runs the computations associated with transactions. These communicate over an authenticated port using a new set of JSON RPC methods called the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/execution-apis\/tree\/main\/src\/engine\">Engine API<\/a>. The EL and CL client authenticate each other using a JWT secret. <strong>Node operators should refer to their clients&#8217; documentation for instructions about how to generate and configure these.<\/strong><\/p>\n<p class=\"chakra-text css-gi02ar\">In other words, if you were already running a node on the Beacon Chain, you now also need to run an execution layer client. Similarly, if you were running a node on the current proof-of-work network, you will need to run a consensus layer client. For them to communicate securely, a JWT token must be passed to each client.<\/p>\n<p class=\"chakra-text css-gi02ar\">It is worth emphasizing that while they are both part of consensus layer client releases, running a Beacon Node is distinct from running a Validator Client. Stakers must run both, but node operators only need the former. <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/docs.ethhub.io\/ethereum-roadmap\/ethereum-2.0\/eth-2.0-client-architecture\/\">This post<\/a> explains the difference between both components in more detail.<\/p>\n<p class=\"chakra-text css-gi02ar\">Also, note that each layer will maintain an independent set of peers and expose its own APIs. The <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/beacon-apis\">Beacon<\/a> and <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/execution-apis\">JSON RPC<\/a> APIs will both continue working as expected.<\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Finally, remember to check back on June 3rd for an announcement on this blog of the final Ropsten TTD value.<\/strong><\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-a-staker-what-do-i-need-to-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as a staker what do i need to do permalink\" href=\"#as-a-staker-what-do-i-need-to-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As a staker, what do I need to do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">As explained above, <strong>validators on the Beacon Chain will need to run an execution layer client after The Merge, in addition to their consensus layer clients.<\/strong> Pre-merge, this was strongly recommended, but validators could have outsourced these functions to third-party providers. This was possible because the only data required on the execution layer were updates to the deposit contract.<\/p>\n<p class=\"chakra-text css-gi02ar\">Post-merge, validators need to ensure that transactions in blocks that they create and attest to are valid. To do this, each beacon node must be paired with an execution layer client. Note that multiple validators can still be paired to a single beacon node &amp; execution layer client combo. While this expands validators&#8217; responsibilities, it also gives a validator who proposes a block the right to its associated transaction priority fees (which currently go to miners).<\/p>\n<p class=\"chakra-text css-gi02ar\">While validator rewards accrue on the Beacon Chain and will require a subsequent network upgrade to be withdrawn, transaction fees will continue to be paid, burned, and distributed on the execution layer. Validators can specify any Ethereum address as a recipient for transaction fees.<\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>After updating your consensus client, be sure to set the <span class=\"chakra-text css-ons8vw\">fee recipient<\/span> as part of your validator client configurations to ensure transaction fees are sent to an address you control.<\/strong><\/p>\n<p class=\"chakra-text css-gi02ar\">If you have staked using a third-party provider, it is up to your selected provider to specify how these fees are allocated.<\/p>\n<p class=\"chakra-text css-gi02ar\">Testnet upgrades are the last chance for validators to ensure their setups work as expected and resolve issues. Information about running a validator on the Ropsten Beacon Chain in preparation for The Merge can be found on the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/ropsten.launchpad.ethereum.org\/en\/\">Ropsten staking launchpad<\/a>.<\/p>\n<p class=\"chakra-text css-gi02ar\">We strongly recommend that mainnet validators run through The Merge on Ropsten and other testnets before the Ethereum mainnet transitions to proof-of-stake.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-an-application-or-tooling-developer-what-should-i-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as an application or tooling developer what should i do permalink\" href=\"#as-an-application-or-tooling-developer-what-should-i-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As an application or tooling developer, what should I do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">With The Merge going live on Ropsten, now is the time to ensure that your product works as expected through the proof-of-stake transition and in a post-merge context. As explained in a <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2021\/11\/29\/how-the-merge-impacts-app-layer\">previous post<\/a>, The Merge will have only minimal impact on a subset of contracts deployed on Ethereum, none of which should be breaking. Additionally, the lion&#8217;s share of user API endpoints remain stable (unless you use proof-of-work specific methods such as <span class=\"chakra-text css-ons8vw\">eth_getWork<\/span>).<\/p>\n<p class=\"chakra-text css-gi02ar\">That said, most applications on Ethereum involve much more than on-chain contracts. <strong>Now is the time<\/strong> to ensure that your front-end code, tooling, deployment pipeline and other off-chain components work as intended. We strongly recommend that developers run through a complete testing &amp; deployment cycle on Ropsten (or <a class=\"chakra-link css-vezwxf\" href=\"https:\/\/blog.ethereum.org\/2022\/03\/14\/kiln-merge-testnet\">Kiln<\/a>) and report any issues with tools or dependencies to those projects&#8217; maintainers. If you are unsure where to open an issue, please use <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/eth-clients\/merge-testnets\/\">this repository<\/a>.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-an-ethereum-user-or-ether-holder-is-there-anything-i-need-to-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as an ethereum user or ether holder is there anything i need to do permalink\" href=\"#as-an-ethereum-user-or-ether-holder-is-there-anything-i-need-to-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As an Ethereum user or Ether holder, is there anything I need to do?<\/h3>\n<p class=\"chakra-text css-gi02ar\">No. The Ethereum mainnet is not affected by this testnet. Subsequent announcements will be made on this blog before mainnet&#8217;s transition.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-a-miner-is-there-anything-i-need-to-do\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as a miner is there anything i need to do permalink\" href=\"#as-a-miner-is-there-anything-i-need-to-do\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As a miner, is there anything I need to do?<\/h3>\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 operate entirely under proof-of-stake after The Merge. At that point, mining will no longer be possible on the network.<\/p>\n<p class=\"chakra-text css-gi02ar\">This is expected around June 8, 2022 on Ropsten and later this year for the Ethereum mainnet.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"as-a-validator-can-i-withdraw-my-stake\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"as a validator can i withdraw my stake permalink\" href=\"#as-a-validator-can-i-withdraw-my-stake\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>As a validator, can I withdraw my stake?<\/h3>\n<p class=\"chakra-text css-gi02ar\">No. The Merge is the most complicated upgrade to Ethereum to date. To minimize risks of network disruptions, a minimal approach was taken which excluded any non-transition changes from this upgrade.<\/p>\n<p class=\"chakra-text css-gi02ar\">Withdrawals from the Beacon Chain will likely be introduced in the first upgrade after The Merge. Specifications for both the <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/consensus-specs\/issues\/2758\">consensus<\/a> and <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-4895\">execution<\/a> layers are in progress.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"i-have-more-questions-where-can-i-ask-them\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"i have more questions where can i ask them permalink\" href=\"#i-have-more-questions-where-can-i-ask-them\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>I have more questions, where can I ask them?<\/h3>\n<p class=\"chakra-text css-gi02ar\">A <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/github.com\/ethereum\/pm\/issues\/532\">Merge Community Call<\/a> is scheduled for June 3, 14:00 UTC. Client developers and researchers will be available to answer questions from node operators, stakers, infrastructure &amp; tooling providers and community members.<\/p>\n<h3 class=\"chakra-heading group css-xuzltg\" id=\"wen-merge\" data-group=\"true\"><a class=\"chakra-link css-128fqrf\" aria-label=\"wen merge permalink\" href=\"#wen-merge\"><svg viewbox=\"0 0 24 24\" focusable=\"false\" class=\"chakra-icon css-173jpr1\"><g fill=\"currentColor\"><path d=\"M10.458,18.374,7.721,21.11a2.853,2.853,0,0,1-3.942,0l-.892-.891a2.787,2.787,0,0,1,0-3.941l5.8-5.8a2.789,2.789,0,0,1,3.942,0l.893.892A1,1,0,0,0,14.94,9.952l-.893-.892a4.791,4.791,0,0,0-6.771,0l-5.8,5.8a4.787,4.787,0,0,0,0,6.77l.892.891a4.785,4.785,0,0,0,6.771,0l2.736-2.735a1,1,0,1,0-1.414-1.415Z\"\/><path d=\"M22.526,2.363l-.892-.892a4.8,4.8,0,0,0-6.77,0l-2.905,2.9a1,1,0,0,0,1.414,1.414l2.9-2.9a2.79,2.79,0,0,1,3.941,0l.893.893a2.786,2.786,0,0,1,0,3.942l-5.8,5.8a2.769,2.769,0,0,1-1.971.817h0a2.766,2.766,0,0,1-1.969-.816,1,1,0,1,0-1.415,1.412,4.751,4.751,0,0,0,3.384,1.4h0a4.752,4.752,0,0,0,3.385-1.4l5.8-5.8a4.786,4.786,0,0,0,0-6.771Z\"\/><\/g><\/svg><\/a>wen merge?<\/h3>\n<p class=\"chakra-text css-gi02ar\">As of the publication of this post, the date for the Ethereum mainnet proof-of-stake transition has <strong>not<\/strong> been set. Any source claiming otherwise is likely to be a scam. Updates will be posted on this blog. Please stay safe!<\/p>\n<p class=\"chakra-text css-gi02ar\">Assuming no issues are found with Ropsten, once client testing is complete, Ethereum&#8217;s other testnets, will run through The Merge. Once Goerli and Sepolia have successfully transitioned and stabilized, a slot height will be chosen for the Bellatrix upgrade on the Beacon Chain and a <a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-vezwxf\" href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-3675#terminal-total-difficulty-vs-block-number\">difficulty value<\/a> will be set for the mainnet transition. Clients will then make releases that enable The Merge on mainnet. These will be announced on this blog and in other community publications.<\/p>\n<p class=\"chakra-text css-gi02ar\">This assumes no issues are found. However, if issues are found at any point in the process or test coverage is judged to be insufficient, these things will be addressed before continuing with the deployment process.<\/p>\n<p class=\"chakra-text css-gi02ar\">Only then will it be possible to estimate the exact date for The Merge.<\/p>\n<p class=\"chakra-text css-gi02ar\">In other words, \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 first longstanding testnet to run through The Merge A new Ropsten Beacon Chain was launched on May 30, 2022 to provide consensus to the network The Ropsten Beacon Chain will upgrade to merge-compatible protocol rules (Bellatrix) at slot 24000, expected on June 2, 2022 After this, a Terminal Total Difficulty (TTD) [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":17987,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tdm_status":"","tdm_grid_status":"","footnotes":""},"categories":[24],"tags":[],"kronos_expire_date":[],"class_list":["post-17986","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ethereum"],"_links":{"self":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/17986","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/comments?post=17986"}],"version-history":[{"count":0,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/posts\/17986\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media\/17987"}],"wp:attachment":[{"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/media?parent=17986"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/categories?post=17986"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/tags?post=17986"},{"taxonomy":"kronos_expire_date","embeddable":true,"href":"https:\/\/cryptoted.net\/index.php\/wp-json\/wp\/v2\/kronos_expire_date?post=17986"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}