The Ethereum ecosystem is taking a monumental leap forward with the implementation of the Merge, transitioning the network from Proof-of-Work (PoW) to Proof-of-Stake (PoS). This upgrade represents one of the most significant milestones in Ethereum's history, and the Sepolia testnet merge serves as a critical testing phase before the mainnet deployment.
Understanding the Sepolia Merge
The Sepolia testnet represents the second of three public testnets scheduled to undergo the Merge process. This strategic approach allows developers to thoroughly test the transition mechanics before implementing them on the main Ethereum network.
When the Sepolia testnet's PoW chain reaches a total difficulty exceeding 17,000,000,000,000,000, the network will automatically transition to PoS consensus. This event is expected to occur within days of the announcement, though exact timing may vary due to the testnet's naturally fluctuating hash rate.
Following the Merge, Sepolia will maintain a permissioned validator set similar to existing Proof-of-Authority testnets. This controlled environment provides optimal conditions for testing while the Goerli/Prater testnet will undergo merging later with an open validator set, allowing stakers to test the complete PoW to PoS transition.
Technical Background and Preparation
The Ethereum development community has invested years of research and testing to bring Proof-of-Stake to the network. We've now entered the final testing phase with testnet deployments. With Ropsten already successfully transitioned to PoS and regular shadow forks occurring, Sepolia stands ready for its Merge moment.
The Merge differs from previous Ethereum upgrades in two fundamental aspects. First, node operators must update both their consensus layer (CL) and execution layer (EL) clients simultaneously rather than updating just one component. Second, the upgrade activates in two distinct phases: beginning with the Bellatrix upgrade at a specific epoch height on the beacon chain, followed by activation when the execution layer reaches the Terminal Total Difficulty value.
Sepolia has already implemented the Bellatrix upgrade on its beacon chain. The final phase involves reaching the Terminal Total Difficulty threshold that will trigger the full transition.
Upgrade Specifications and Timing
The Two-Phase Activation Process
The Merge occurs through a carefully orchestrated two-step process. The initial phase begins with a consensus layer network upgrade triggered by a specific epoch height. This is followed by the execution layer transition from PoW to PoS, activated by reaching a predetermined Total Difficulty threshold known as Terminal Total Difficulty (TTD).
On June 20, 2022, at epoch 100, the Bellatrix upgrade prepared Sepolia's beacon chain for the Merge. At this point, consensus layer clients began monitoring for the TTD trigger on the PoW chain.
Due to the testnet's unpredictable hash rate, the initial TTD was set extremely high at 100,000,000,000,000,000,000,000—a value that would take centuries to reach at current rates. Following the Bellatrix upgrade, the TTD for the transition was updated to 17,000,000,000,000,000, which is expected to be reached within days.
Once the execution layer exceeds the TTD value, the next block will be produced entirely by beacon chain validators. The Merge is considered complete once the beacon chain finalizes this block. Under normal network conditions, finalization occurs approximately two epochs (about 13 minutes) after the first post-TTD block.
A new JSON-RPC block tag "finalized" will return the latest finalized block or generate an error if no post-merge block exists. This tag enables applications to check whether the Merge has completed. Similarly, smart contracts can query the DIFFICULTY opcode (0x44)—renamed to PREVRANDAO after the Merge—to determine if the transition has occurred.
👉 Explore real-time network monitoring tools
Client Version Requirements
Node operators must run both execution and consensus layer clients to maintain operation after the Merge. The following client versions support the Sepolia testnet Merge:
Consensus Layer Clients:
- Lighthouse v2.3.2-rc.0
- Lodestar v0.39.0-rc.2
- Prysm v2.1.3-rc.4
- Nimbus v22.6.1
- Teku v22.6.1
Execution Layer Clients:
- Besu v22.4.3
- Erigon v2022.06.06
- go-ethereum (geth) v1.10.20
- Nethermind v1.13.4
Validators should pay particular attention to the risks associated with running majority clients on both execution and consensus layers. Client diversity strengthens network resilience and reduces systemic risks.
Special Client Considerations
Besu Client Configuration: For Sepolia Merge compatibility, Besu users must manually override the required TTD value. Users need to run the latest Besu client version (v22.4.3 as of publication) and either add override-genesis-config=["terminalTotalDifficulty=17000000000000000"] to their TOML configuration file or include -override-genesis-config="terminalTotalDifficulty=17000000000000000" when starting their node.
Erigon Client Configuration: Erigon users similarly need to manually override the TTD value by running the 2022.06.06-alpha version and adding --override.terminaltotaldifficulty=17000000000000000 when starting their node.
Technical Specifications and Standards
The consensus-critical changes for the Merge are documented in two primary locations:
- Consensus layer changes are modified in the bellatrix directory of the consensus specifications repository
- Execution layer modifications are documented in the Paris specification within the execution specifications repository
Additionally, two other specifications cover how consensus and execution layer clients interact:
- The Engine API facilitates communication between consensus and execution layers
- Optimistic Sync allows the consensus layer to import blocks while execution layer clients synchronize
Frequently Asked Questions
What should node operators do to prepare?
After the Merge, a complete Ethereum node combines a consensus layer client (running the PoS beacon chain) with an execution layer client (managing user state and transaction computations). These components communicate through an authenticated port using a new set of JSON RPC methods called the Engine API. Node operators must generate and configure JWT tokens for secure communication between clients. If you're already running a beacon chain node, you now need to add an execution layer client. Conversely, if you're running a current PoW network node, you'll need to add a consensus layer client.
What actions should stakers take?
Sepolia's validator set is permissioned, so unless you're already a Sepolia validator, no action is required. Goerli/Prater's transition to PoS will be announced later and will be open to all validators. Post-merge, validators will need to run both consensus and execution layer clients. While validators can outsource these functions to third-party providers, running your own execution client ensures you receive transaction priority fees.
How should application and tooling developers prepare?
The Merge has minimal impact on deployed contracts but may affect off-chain components. Developers should complete full testing and deployment cycles on Ropsten or Kiln testnets and report any issues with tools or dependencies. Note that all testnets except Sepolia and Goerli will be deprecated after the Merge, so plan migration accordingly.
Do Ethereum users or ETH holders need to take any action?
No. The Ethereum mainnet remains unaffected by this testnet transition. The community will receive advance notice before any mainnet changes occur.
What should miners expect?
If you're mining on Ethereum mainnet or Sepolia testnet, understand that both networks will operate entirely under PoS consensus after their respective Merges. Mining will no longer be possible on these networks post-transition. Sepolia mining will cease within days, with mainnet mining ending later this year.
When will validators be able to withdraw staked assets?
Withdrawal functionality is not included in the Merge upgrade. This feature will likely be introduced in the first post-merge upgrade, with specifications already in development for both consensus and execution layers.
Where can I find additional information and support?
The Merge community call scheduled for July 15th UTC will feature client developers and researchers answering questions from node operators, stakers, infrastructure providers, and community members. Always refer to official Ethereum Foundation channels for accurate information.
👉 Access comprehensive migration guides
When will the mainnet Merge occur?
As of this publication, no date has been set for the Ethereum mainnet Merge. Any claims specifying exact dates should be treated as potential scams. Updates will be announced on the Ethereum Foundation blog and other official community platforms. The process continues once Sepolia merges successfully without issues, followed by Goerli/Prater testing. Only after successful testing will a mainnet epoch height be selected for Bellatrix upgrade and a TTD value set for mainnet Merge.
The Ethereum community continues to work diligently toward a successful transition, addressing any issues that may arise during testing before proceeding with deployment. The exact timeline remains contingent on successful testing outcomes, but progress continues steadily toward implementation.