{"id":6245,"date":"2024-12-18T00:32:57","date_gmt":"2024-12-17T23:32:57","guid":{"rendered":"https:\/\/wsj-crypto.com\/?p=6245"},"modified":"2024-12-18T00:32:57","modified_gmt":"2024-12-17T23:32:57","slug":"unveiling-the-sepolia-merge-a-new-chapter-for-ethereum","status":"publish","type":"post","link":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/","title":{"rendered":"Unveiling the Sepolia Merge: A New Chapter for Ethereum"},"content":{"rendered":"\n<div id=\"\">\n<ul role=\"list\" class=\"css-1onhfjo\">\n<li class=\"css-cvpopp\"><strong><span class=\"chakra-text css-ons8vw\">Note<\/span>:<!-- --><\/strong> on July 5, 2022, the advised releases for go-ethereum and Erigon were updated. Refer to &#8220;Client Releases&#8221; for further information.<!-- --><\/li>\n<li class=\"css-cvpopp\">Sepolia is set to be the second of three public testnets to undergo The Merge.<!-- --><\/li>\n<li class=\"css-cvpopp\">The network will shift to proof-of-stake once the overall difficulty on the proof-of-work chain exceeds <!-- --><strong><span class=\"chakra-text css-ons8vw\">17,000,000,000,000,000<\/span><\/strong>, which is anticipated to take place in the upcoming days.<!-- --><\/li>\n<li class=\"css-cvpopp\">After the merge, Sepolia will have a controlled validator set, similar to current proof-of-authority testnets. Goerli\/Prater, which will merge at a later stage, will retain an open validator set to enable stakers to trial the shift.<!-- --><\/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\">Following years of efforts to implement proof-of-stake in Ethereum, we are now deeply engaged in the final testing phase: testnet deployments!<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">With Ropsten already migrated to proof-of-stake and shadow forks occurring regularly, Sepolia is now primed for The Merge. After Sepolia, only Goerli\/Prater requires merging before advancing to mainnet. Other testnets will be regarded as obsolete post-merge, as articulated <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2022\/06\/21\/testnet-deprecation\">in a recent update<!-- --><\/a>.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">The Merge distinguishes itself from earlier Ethereum upgrades in two significant ways. Firstly, node operators must simultaneously update both their consensus layer (CL) and execution layer (EL) clients, instead of just one. Secondly, the upgrade unfolds in two stages: the first occurs at an epoch height on the Beacon Chain and the second upon reaching 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> milestone on the execution layer.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Sepolia has already experienced the Bellatrix upgrade on the Beacon Chain. We are now disclosing the specifics of the second phase of the transition: achieving the <!-- --><span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty<\/span>.<!-- --><\/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> constitutes a two-part process. It begins with a network upgrade on the consensus layer, initiated by an epoch height. This is succeeded by the execution layer&#8217;s transition from proof-of-work to proof-of-stake, activated by reaching a certain <!-- --><span class=\"chakra-text css-ons8vw\">Total Difficulty<\/span> limit, referred to 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 20, 2022<!-- --><\/strong>, at epoch <!-- --><strong><span class=\"chakra-text css-ons8vw\">100<\/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 prepared the Sepolia Beacon Chain for The Merge. At that moment, CL clients began monitoring for a <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span> value to be achieved on the proof-of-work chain.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Given that the hash rate of proof-of-work testnets is quite unpredictable, the <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span> value was initially established at an exceedingly high figure, <!-- --><span class=\"chakra-text css-ons8vw\">100000000000000000000000<\/span>. Based on Sepolia&#8217;s current hash rate, it would take centuries to reach this figure.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">With Bellatrix now operational, a revised <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span> value of <!-- --><strong><span class=\"chakra-text css-ons8vw\">17000000000000000<\/span><\/strong> has been established for the transition. It is anticipated to be reached within the upcoming days. When this new <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span> is hit or surpassed, 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, please note that the hash rate on Sepolia is notoriously erratic, so the actual moment when the <!-- --><span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty<\/span> occurs may vary.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Once the execution layer surpasses the <!-- --><span class=\"chakra-text css-ons8vw\">TTD<\/span>, the subsequent block will be produced exclusively by a Beacon Chain validator. We consider The Merge to be complete when the Beacon Chain finalizes this block. Assuming standard network conditions, this should occur 2 epochs, or roughly 13 minutes, after the initial post-TTD block is reached!<!-- --><\/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>, returns the latest finalized block or an error if no post-merge block exists. This tag can be utilized by applications to verify if The Merge has been accomplished. In a similar vein, 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\">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 check if The Merge has transpired. We encourage infrastructure providers to monitor overall network stability alongside 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 endorse The Merge on the Sepolia testnet. Node operators must 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\">When selecting which client to deploy, validators should particularly be aware of the risks associated with running a dominant client on both the EL and CL. An explanation of these risks and their implications 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 overview of current EL and CL client distribution alongside guides for transitioning from one client to another can be located <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/clientdiversity.org\/\">here<!-- --><\/a>.<!-- --><\/p>\n<p><!-- --><\/p>\n<h4 class=\"chakra-heading css-1u9mv6z\" id=\"consensus-layer\">Consensus Layer<!-- --><\/h4>\n<p><!-- --><br \/>\n<!-- --><\/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\">Refer to the &#8220;Besu Note&#8221; below<!-- --><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">Refer to the &#8220;Besu Note&#8221; below<!-- --><\/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.07.01<!-- --><\/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.07.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\"><del class=\"chakra-text css-0\">v1.10.20<!-- --><\/del> <!-- --><span class=\"chakra-text css-ons8vw\">master<\/span><\/td>\n<td role=\"gridcell\" class=\"css-19nu0k5\">Refer to the &#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\">1.13.4<!-- --><\/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\/c\">Download<!-- --><\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Besu Note:<!-- --><\/strong> for compatibility with the Sepolia merge, Besu users will be required to execute a manual <!-- --><span class=\"chakra-text css-ons8vw\">Terminal Total Difficulty<\/span> override. For this, users must run the latest Besu release, <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/hyperledger\/besu\/releases\/tag\/22.4.3\">22.4.3<!-- --><\/a> at the time of this post\u2019s release, and proceed with the following steps:<!-- --><\/p>\n<p><!-- --><\/p>\n<ul role=\"list\" class=\"css-1onhfjo\">\n<li class=\"css-cvpopp\">When using TOML configuration files, insert the following line: <!-- --><span class=\"chakra-text css-ons8vw\">override-genesis-config=[&#8220;terminalTotalDifficulty=17000000000000000&#8221;]<\/span><\/li>\n<li class=\"css-cvpopp\">When initiating the node via the CLI, include the following flag: <!-- --><span class=\"chakra-text css-ons8vw\">&#8211;override-genesis-config=&#8221;terminalTotalDifficulty=17000000000000000&#8243;<\/span><\/li>\n<\/ul>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Further details about overriding the TTD can be located in the <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2022\/06\/03\/ropsten-merge-ttd\">Ropsten TTD Announcement<!-- --><\/a>.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>Geth Note:<!-- --><\/strong> a regression introduced in go-ethereum v1.10.20 renders it unsuitable for utilization as part of the Sepolia merge. Geth users should instead operate the <!-- --><span class=\"chakra-text css-ons8vw\">master<\/span> branch until a new release is available. Instructions for doing so can be found <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/github.com\/ethereum\/go-ethereum#building-the-source\">here<!-- --><\/a>.<!-- --><\/p>\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\">Consensus-critical 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, found in 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, located in 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> within the execution-specs repository<!-- --><\/li>\n<\/ul>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Besides these, two additional specifications describe the interaction between the consensus and execution layer clients:<!-- --><\/p>\n<p><!-- --><\/p>\n<ul role=\"list\" class=\"css-1onhfjo\">\n<li class=\"css-cvpopp\">The Engine API, detailed 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, described 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, allows the consensus layer to import blocks while 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<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, which operates the proof-of-stake Beacon Chain, and an execution layer client, which handles the user-state and executes computations related to transactions. These components communicate over an authenticated port utilizing a new set of JSON RPC methods known as 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 client authenticate one another using a JWT secret. <!-- --><strong>Node operators should consult their clients&#8217; documentation for guidance on how to create and configure these settings.<!-- --><\/strong><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">In essence, if you were previously running a node on the Beacon Chain, you will now also need to operate an execution layer client. Likewise, if you were managing a node on the existing proof-of-work network, you will have to run a consensus layer client. To ensure secure communication, a JWT token must be delivered to each client.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">It is important to highlight that while both are included in consensus layer client releases, executing a Beacon Node is distinct from operating a Validator Client. Stakers must run both, but node operators only require 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> elaborates on the differences between the two components in greater detail.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Additionally, be aware that each layer will sustain a separate 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 both continue functioning as anticipated.<!-- --><\/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 take?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">The validator set for Sepolia is permissioned, so unless you have already been added as a Sepolia validator, no steps are necessary.<!-- --><\/p>\n<p>&#8211;><\/p>\n<p class=\"chakra-text css-gi02ar\">The transition of Goerli\/Prater to proof-of-stake, set to be revealed later, will be accessible to all validators. Below are some notes to assist in preparation for this. Once more, no action is necessary at this time.<!-- --><\/p>\n<p><!-- --><\/p>\n<blockquote class=\"chakra-code css-1cl98my\"><p>\n<!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">As previously mentioned, <!-- --><strong>validators on the Beacon Chain must operate an execution layer client following The Merge, in addition to their consensus layer clients.<!-- --><\/strong> Prior to the merge, this was highly recommended, but validators could have outsourced these duties to external providers. This was feasible since the only information needed on the execution layer was updates to the deposit contract.<!-- --><\/p>\n<p><!-- --><\/p><\/blockquote>\n<p><!-- --><\/p>\n<blockquote class=\"chakra-code css-1cl98my\"><p>\n<!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">After the merge, validators must verify that the transactions within the blocks they generate and attest to are legitimate. To achieve this, each beacon node must be linked with an execution layer client. It\u2019s important to note that multiple validators can still connect to one beacon node &amp; execution layer client pairing. While this broadens validators\u2019 duties, it also grants a validator proposing a block the entitlement to its correlating transaction priority fees (which currently are awarded to miners).<!-- --><\/p>\n<p><!-- --><\/p><\/blockquote>\n<p><!-- --><\/p>\n<blockquote class=\"chakra-code css-1cl98my\"><p>\n<!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Although validator rewards accumulate on the Beacon Chain and will need a future network upgrade for withdrawal, transaction fees will persist in being paid, incinerated, and distributed on the execution layer. Validators can designate any Ethereum address as the beneficiary of transaction fees.<!-- --><\/p>\n<p><!-- --><\/p><\/blockquote>\n<p><!-- --><\/p>\n<blockquote class=\"chakra-code css-1cl98my\"><p>\n<!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\"><strong>After upgrading your consensus client, make sure to configure the <!-- --><span class=\"chakra-text css-ons8vw\">fee recipient<\/span> within your validator client settings to guarantee that transaction fees are directed to an address you possess.<!-- --><\/strong><\/p>\n<p><!-- --><\/p><\/blockquote>\n<p><!-- --><\/p>\n<blockquote class=\"chakra-code css-1cl98my\"><p>\n<!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Should you have staked using a third-party service, it is your chosen provider&#8217;s responsibility to determine how these fees are distributed.<!-- --><\/p>\n<p><!-- --><\/p><\/blockquote>\n<p><!-- --><\/p>\n<blockquote class=\"chakra-code css-1cl98my\"><p>\n<!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">If you wish to experiment with running a validator on Ethereum post-merge, instructions can be found 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><\/blockquote>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"as-an-application-or-tooling-developer-what-should-i-do\">As a developer of applications or tools, what actions should I take?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">With The Merge commencing on Sepolia, now is the ideal moment to verify that your product functions as anticipated during the proof-of-stake shift and within a post-merge framework. As detailed in a <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2021\/11\/29\/how-the-merge-impacts-app-layer\">previous entry<!-- --><\/a>, The Merge will have minimal effects on a limited range of contracts deployed on Ethereum, none of which should experience disruptions. Furthermore, the majority of user API endpoints will remain constant (unless you utilize proof-of-work specific methods 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, most applications on Ethereum encompass much more than just on-chain contracts. <!-- --><strong>Now is the moment<!-- --><\/strong> to ascertain that your front-end code, tools, deployment pipeline, and other off-chain components operate as expected. We highly advise that developers complete a thorough 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 notify any issues regarding tools or dependencies to the maintainers of those projects. If uncertain about where to raise an issue, please refer to <!-- --><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<p class=\"chakra-text css-gi02ar\">Additionally, you should be aware that all testnets except for Sepolia and Goerli will be phased out after the merge. If you utilize Ropsten, Rinkeby, or Kiln, you should plan to transition to Goerli or Sepolia. More details about this can be found <!-- --><a class=\"chakra-link css-ug8vf0\" href=\"https:\/\/blog.ethereum.org\/2022\/06\/21\/testnet-deprecation\">here<!-- --><\/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 any action I must take?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">No. The Ethereum mainnet is not influenced by this testnet. Further announcements will be made on this blog prior to the mainnet 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 need to take?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">No. If you are mining on the Ethereum mainnet or Sepolia, please note that each network will function purely under proof-of-stake following The Merge. At that stage, mining on the network will cease to be an option.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">This is anticipated to happen in the coming days for Sepolia 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, may I withdraw my stake?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">No. The Merge represents the most intricate upgrade to Ethereum so far. To mitigate risks of network disruptions, a minimalistic strategy was adopted, which excluded any non-transition modifications from this upgrade.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Withdrawals from the Beacon Chain will likely be enabled 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 under development.<!-- --><\/p>\n<p><!-- --><\/p>\n<h3 class=\"chakra-heading css-145upk7\" id=\"i-have-more-questions-where-can-i-ask-them\">I have further inquiries, where can I pose them?<!-- --><\/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\/564\">Merge Community Call<!-- --><\/a> is set for July 15, 14:00 UTC. Client developers and researchers will be present to answer questions 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 will the merge happen?<!-- --><\/h3>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">As of the release of this post, the date for the transition of the Ethereum mainnet to proof-of-stake has <!-- --><strong>not<!-- --><\/strong> been determined. Any source asserting otherwise is likely to be fraudulent. Updates will be provided on this blog. Stay vigilant!<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Assuming no complications arise with Sepolia, after completing client testing, Ethereum&#8217;s other EL testnet, Goerli, will undergo The Merge alongside the Prater CL testnet. After Goerli\/Prater have transitioned successfully and stabilized, an epoch will be selected for the Bellatrix upgrade on the mainnet 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 assigned for the mainnet transition. Clients will then deliver releases enabling The Merge on the mainnet. These updates will be disclosed on this blog and in various community channels.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">This is based on the assumption that no issues are found. If complications arise at any stage during the process or if test coverage is deemed inadequate, these matters will be rectified before proceeding with the deployment process.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Only after this will it be feasible to approximate the exact date for The Merge.<!-- --><\/p>\n<p><!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">In other words, \ud83d\udd1c.<!-- --><\/p>\n<p><!-- --><\/p>\n<hr aria-orientation=\"horizontal\" class=\"chakra-divider css-1e6gg7n\"\/>\n<!-- --><\/p>\n<p class=\"chakra-text css-gi02ar\">Acknowledgments to <!-- --><a target=\"_blank\" rel=\"noopener\" class=\"chakra-link css-ug8vf0\" href=\"https:\/\/unsplash.com\/@justinchrn\">Justin Chrn<!-- --><\/a> for the cover image.<!-- --><\/p>\n<\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/blog.ethereum.org\/en\/2022\/06\/30\/sepolia-merge-announcement\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Note: on July 5, 2022, the advised releases for go-ethereum and Erigon were updated. Refer to &#8220;Client Releases&#8221; for further information. Sepolia is set to be the second of three public testnets to undergo The Merge. The network will shift to proof-of-stake once the overall difficulty on the proof-of-work chain exceeds 17,000,000,000,000,000, which is anticipated<\/p>\n","protected":false},"author":3,"featured_media":6246,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23],"tags":[469],"class_list":{"0":"post-6245","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-sepolia-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>Unveiling the Sepolia Merge: A New Chapter for Ethereum - 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\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/\" \/>\n<meta property=\"og:locale\" content=\"it_IT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Unveiling the Sepolia Merge: A New Chapter for Ethereum - WSJ-Crypto\" \/>\n<meta property=\"og:description\" content=\"Note: on July 5, 2022, the advised releases for go-ethereum and Erigon were updated. Refer to &#8220;Client Releases&#8221; for further information. Sepolia is set to be the second of three public testnets to undergo The Merge. The network will shift to proof-of-stake once the overall difficulty on the proof-of-work chain exceeds 17,000,000,000,000,000, which is anticipated\" \/>\n<meta property=\"og:url\" content=\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/\" \/>\n<meta property=\"og:site_name\" content=\"WSJ-Crypto\" \/>\n<meta property=\"article:published_time\" content=\"2024-12-17T23:32:57+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_f145c876a6e0a4d269f75913dc169507-scaled.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"1584\" \/>\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=\"10 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\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/\",\"url\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/\",\"name\":\"Unveiling the Sepolia Merge: A New Chapter for Ethereum - WSJ-Crypto\",\"isPartOf\":{\"@id\":\"https:\/\/wsj-crypto.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_f145c876a6e0a4d269f75913dc169507-scaled.jpg\",\"datePublished\":\"2024-12-17T23:32:57+00:00\",\"author\":{\"@id\":\"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7\"},\"breadcrumb\":{\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#breadcrumb\"},\"inLanguage\":\"it-IT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"it-IT\",\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#primaryimage\",\"url\":\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_f145c876a6e0a4d269f75913dc169507-scaled.jpg\",\"contentUrl\":\"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_f145c876a6e0a4d269f75913dc169507-scaled.jpg\",\"width\":2560,\"height\":1584},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/wsj-crypto.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Unveiling the Sepolia Merge: A New Chapter for Ethereum\"}]},{\"@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":"Unveiling the Sepolia Merge: A New Chapter for Ethereum - 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\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/","og_locale":"it_IT","og_type":"article","og_title":"Unveiling the Sepolia Merge: A New Chapter for Ethereum - WSJ-Crypto","og_description":"Note: on July 5, 2022, the advised releases for go-ethereum and Erigon were updated. Refer to &#8220;Client Releases&#8221; for further information. Sepolia is set to be the second of three public testnets to undergo The Merge. The network will shift to proof-of-stake once the overall difficulty on the proof-of-work chain exceeds 17,000,000,000,000,000, which is anticipated","og_url":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/","og_site_name":"WSJ-Crypto","article_published_time":"2024-12-17T23:32:57+00:00","og_image":[{"width":2560,"height":1584,"url":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_f145c876a6e0a4d269f75913dc169507-scaled.jpg","type":"image\/jpeg"}],"author":"wsjcrypto","twitter_card":"summary_large_image","twitter_misc":{"Scritto da":"wsjcrypto","Tempo di lettura stimato":"10 minuti"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/","url":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/","name":"Unveiling the Sepolia Merge: A New Chapter for Ethereum - WSJ-Crypto","isPartOf":{"@id":"https:\/\/wsj-crypto.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#primaryimage"},"image":{"@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#primaryimage"},"thumbnailUrl":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_f145c876a6e0a4d269f75913dc169507-scaled.jpg","datePublished":"2024-12-17T23:32:57+00:00","author":{"@id":"https:\/\/wsj-crypto.com\/#\/schema\/person\/88a93723b30416db1a352d5a0096c4a7"},"breadcrumb":{"@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#breadcrumb"},"inLanguage":"it-IT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/"]}]},{"@type":"ImageObject","inLanguage":"it-IT","@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#primaryimage","url":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_f145c876a6e0a4d269f75913dc169507-scaled.jpg","contentUrl":"https:\/\/wsj-crypto.com\/wp-content\/uploads\/2024\/12\/upload_f145c876a6e0a4d269f75913dc169507-scaled.jpg","width":2560,"height":1584},{"@type":"BreadcrumbList","@id":"https:\/\/wsj-crypto.com\/index.php\/2024\/12\/18\/unveiling-the-sepolia-merge-a-new-chapter-for-ethereum\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/wsj-crypto.com\/"},{"@type":"ListItem","position":2,"name":"Unveiling the Sepolia Merge: A New Chapter for Ethereum"}]},{"@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\/6245","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=6245"}],"version-history":[{"count":2,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts\/6245\/revisions"}],"predecessor-version":[{"id":6248,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/posts\/6245\/revisions\/6248"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/media\/6246"}],"wp:attachment":[{"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/media?parent=6245"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/categories?post=6245"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wsj-crypto.com\/index.php\/wp-json\/wp\/v2\/tags?post=6245"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}