- For the final testnet proof-of-stake transition, Goerli will combine with Prater. The united Goerli/Prater network will keep the Goerli name after the merge.
- Bellatrix, the upgrade for Prater preparing it for The Merge will occur at epoch 112260, anticipated at 12:24PM UTC on August 4, 2022.
- Following Bellatrix’s activation, the Goerli/Prater merge will occur when Goerli reaches a total difficulty of 10790000, expected between August 6-12, 2022.
- After the merge, Goerli’s validator set will remain open for individual stakers to operate testnet validators. Stakers wishing to initiate a Goerli/Prater validator can do so at the Prater Launchpad.
Background
After numerous efforts to implement proof-of-stake on Ethereum, we are presently well into the concluding testing phase: testnet deployments!
Following multiple devnets, shadow forks, and merges on deprecated testnets, Sepolia was recently shifted to proof-of-stake. Now, only one more testnet remains: Goerli, along with its associated Beacon Chain, Prater.
The Merge differs from earlier Ethereum upgrades in two aspects. First, node operators must update both their consensus layer (CL) and execution layer (EL) clients simultaneously, rather than just one of the two. Second, the upgrade is activated in two phases: the first, referred to as Bellatrix, at an epoch height on the Beacon Chain, and the second, termed Paris, upon reaching a Total Difficulty value on the execution layer.
Upgrade Information
Timing
The Merge is a two-part process. It commences with a network upgrade, Bellatrix, on the consensus layer, triggered by an epoch height. This is succeeded by the execution layer’s shift from proof-of-work to proof-of-stake, Paris, initiated by a specific Total Difficulty threshold, known as the Terminal Total Difficulty (TTD).
The Bellatrix upgrade is slated for epoch 112260 on the Prater Beacon Chain, anticipated at 12:24PM UTC on August 4, 2022. Paris, part of the execution layer transition, will be triggered upon reaching a Terminal Total Difficulty (TTD) of 10790000 on Goerli, expected between August 6-12, 2022.
Once the execution layer surpasses the TTD, the subsequent block will solely be produced by a Beacon Chain validator. We consider The Merge to be finalized when the Beacon Chain has confirmed this block. Under normal network circumstances, this should occur 2 epochs, or approximately 13 minutes, after the first post-TTD block is produced!
A new JSON-RPC block tag, finalized, provides the latest finalized block or an error if no such post-merge block is available. This tag can be utilized by applications to verify if The Merge has been completed. Additionally, smart contracts can query the DIFFICULTY opcode (0x44), renamed to PREVRANDAO post-merge, to ascertain if The Merge has taken place. It is advisable for infrastructure providers to monitor overall network stability alongside finalization status.
Client Releases
The following client versions support The Merge across the Goerli & Prater testnets. Node operators must run both an execution and consensus layer client to remain on the network during and after The Merge.
When deciding which client to operate, validators should be particularly cautious of the hazards of running a majority client on both the EL and CL. An explanation of these risks and their implications can be found here. An estimation of the current EL and CL client distribution and guides for switching from one client to another can be accessed here.
Consensus Layer
Execution Layer
Upgrade Specifications
Consensus-critical alterations for The Merge are detailed in two locations:
- The consensus layer modifications, located under the bellatrix directory of the consensus-specs repository
- The execution layer modifications, located under the Paris spec in the execution-specs repository.“`html
repository
Alongside these, two additional specifications outline the interaction between the consensus and execution layer clients:
- The Engine API, detailed in the execution-apis repository, facilitates communication between the consensus and execution layers
- Optimistic Sync, detailed in the sync folder of the consensus-specs repository, allows the consensus layer to import blocks while the execution layer client is syncing, and to share a partial view of the chain’s head from the former to the latter
FAQ
As a node operator, what actions should I take?
After the merge, an Ethereum full node will integrate a consensus layer (CL) client, managing the proof-of-stake Beacon Chain, and an execution layer (EL) client, overseeing the user-state and executing transaction-related computations. These communicate over a secure port utilizing a new set of JSON RPC methods referred to as the Engine API. The EL and CL clients authenticate each other via a JWT secret. Node operators should consult their clients’ documentation for guidance on how to generate and set up these.
In essence, if you were already operating a node on the Beacon Chain, you must now also run an execution layer client. Similarly, if you operated on the existing proof-of-work network, a consensus layer client will now be necessary. For secure communication, a JWT token needs to be provided to each client. For summarized instructions on operating a node on the Goerli/Prater network, Click here.
It is important to highlight that, although both are part of consensus layer client releases, running a Beacon Node distinctly differs from operating a Validator Client. Stakers need to run both, whereas node operators are only required to run the former. This article elaborates further on the differences between these two components.
Furthermore, be informed that each layer will sustain its own independent set of peers and present its distinct APIs. Both the Beacon and JSON RPC APIs will continue operating as anticipated.
As a staker, what steps must I take?
The Goerli/Prater Merge represents your final opportunity to guarantee your validators are correctly configured before the mainnet transition. It is highly advisable to navigate through the transition now to prevent any unforeseen issues on the mainnet.
As indicated previously, validators on the Beacon Chain must run an execution layer client post-Merge in addition to their consensus layer clients. Prior to the merge, this was highly recommended, allowing validators to outsource these functions to external service providers. This was feasible as the only information needed on the execution layer pertained to updates of the deposit contract.
After the merge, validators must ensure that the transactions found in the blocks they create and attest to are valid. To facilitate this, each beacon node must be matched with an execution layer client. Note that multiple validators can still be paired to a single beacon node & execution layer client together. While this increases the responsibilities of validators, it also grants a validator proposing a block the entitlement to its associated transaction priority fees (currently allocated to miners).
Although validator rewards accumulate on the Beacon Chain and will require a subsequent network update for withdrawal, transaction fees will persist in being paid, burned, and disbursed on the execution layer. Validators can designate any Ethereum address as a recipient for transaction fees.
Following the update of your consensus client, ensure to configure the fee recipient in your validator client settings to guarantee transaction fees are directed to an address under your control. If you have staked through an external provider, it is up to the chosen provider to determine how these fees are distributed.
The Prater Staking Launchpad offers a Merge Readiness Checklist that stakers can utilize to ensure they have addressed each step of the process. The EthStaker team is also conducting a Merge Validator Preparation Workshop on July 29.
Why does the estimate for the Terminal Total Difficulty date appear so extensive?
The fluctuations in incremental difficulty per block complicate the estimation of a timeframe for the TTD, resulting in a wider predicted range. Users should recognize that this will apply similarly to the mainnet’s transition due to alterations in the proof-of-work hash rate.
As an application or tooling developer, what actions should I take?
With The Merge commencing on Goerli, this is your final opportunity to verify that your application operates as intended throughout the proof-of-stake transition and in a post-merge environment. As discussed in a previous article, The Merge will exert only minimal repercussions on a subset of contracts implementing on Ethereum, none of which should be negatively impacted. Moreover, the majority of user API endpoints will remain stable (unless utilizing proof-of-work specific methods such as eth_getWork).
“`
Having said that, the majority of applications on Ethereum entail significantly more than just on-chain contracts. This is the moment to confirm that your front-end code, tools, deployment pipeline, and all other off-chain elements function as required. We highly advise developers to conduct a thorough testing & deployment cycle on Sepolia, Ropsten, or Kiln and communicate any concerns with tools or dependencies to the respective maintainers of those projects. If you’re uncertain about where to report an issue, please utilize this repository.
Moreover, it’s important to be aware that all testnets aside from Sepolia and Goerli will be phased out following the merge. If you are a user of Ropsten, Rinkeby, or Kiln, you should prepare to transition to Goerli or Sepolia. Additional details regarding this can be located here.
As an Ethereum user or Ether holder, is there something I need to take care of?
No. The Ethereum mainnet remains unaffected by this testnet. Further announcements will be issued on this blog prior to the mainnet transition.
As a miner, is there something I need to take care of?
No. If you are mining on the Ethereum mainnet, it’s crucial to understand that the network will run entirely on proof-of-stake after The Merge. At that stage, mining will no longer be feasible on the network.
As a validator, can I withdraw my stake?
No. The Merge represents the most intricate upgrade to Ethereum thus far. To mitigate the risks of network interruptions, a conservative approach was adopted that excluded any non-transition modifications from this upgrade.
Withdrawals from the Beacon Chain are expected to be implemented in the first upgrade following The Merge. Specifications for both the consensus and execution layers are currently being worked on.
I have additional inquiries, where can I pose them?
The EthStaker community has established a discord channel to address questions from stakers and node operators. You can join their discord here and then utilize the #goerli-prater channel for support. As previously mentioned, EthStaker will also conduct a Merge Validator Preparation Workshop on July 29.
Additionally, a Merge Community Call is arranged for August 12, 14:00 UTC. Client developers and researchers will be available to address inquiries from node operators, stakers, infrastructure & tooling providers, and community members. Please note that this community call is anticipated to occur after the Goerli/Prater merge.
When is the merge?
As of the release of this post, the schedule for the Ethereum mainnet proof-of-stake transition has not been established. Any source claiming otherwise is likely attempting to deceive. Updates will be published on this blog. Please exercise caution!
Assuming no complications arise during the Goerli/Prater merge, when clients have feature-complete releases, a slot height will be selected for the Bellatrix upgrade on the mainnet Beacon Chain and a total difficulty value will be assigned for the mainnet transition. Clients will then release updates that facilitate The Merge on mainnet. These updates will be communicated on this blog and in other community announcements.
However, if any issues arise at any stage in the process or if test coverage is deemed inadequate, these factors will be rectified prior to proceeding with the deployment process.
Only at that point will it be feasible to predict the precise date for The Merge.
In simpler terms, 🔜.