Goerli/Prater merger announced | Ethereum Foundation Blog
- For the final testnet proof-of-stake transition, Goerli will merge with Prater. The combined Goerli/Prater network will retain the Goerli name after the merge.
- Bellatrix, Prater Upgrade Preparing for The Merge Will Happen in a New Era 112260Estimated time: August 4, 2022, 12:24 PM (UTC).
- After Bellatrix is activated, a Goerli/Prater merge occurs when Goerli reaches the following total difficulty levels: 10790000expected between August 6-12, 2022.
- After the merge, Goerli’s validator set will remain open for individual stakers to run testnet validators. Stakers who want to start a Goerli/Prater validator can do so here: Prater Launchpad.
background
After years of work to bring Proof of Stake to Ethereum, we have now entered the final phase of testing: testnet deployment!
After several devnets, a shadow fork and merge took place on the deprecated testnet. Sepolia recently converted to proof-of-stake.. There is now only one more testnet left: Goerli and its associated beacon chain, Prater.
Merge differs from previous Ethereum upgrades in two ways. First, node operators must update the consensus layer (CL) and execution layer (EL) clients simultaneously, rather than updating one or the other. Second, the upgrade is activated in two steps. The first step is named Bellatrix and the second step is named Paris, at a landmark height in the beacon chain. total difficulty Values from the execution layer.
Upgrade information
timing
absorption It’s a two-step process. This begins with Bellatrix, a network upgrade of the consensus layer triggered by breakthrough heights. The execution layer then switches from Proof-of-Work to Proof-of-Stake (Paris). total difficulty called threshold Final Total Difficulty (TTD).
that much bellatrix An upgrade is scheduled for Epoch. 112260 Expected from Prater Beacon Chain August 4, 2022, 12:24 PM (UTC). flyThe transition part of the execution layer is Final Total Difficulty (TTD) ~ Of 10790000 In Goerli, it is expected between: August 6-12, 2022.
When the execution layer is exceeded TTD, the next block is created only by the beacon chain validators. We consider the merge complete when the beacon chain completes this block. Assuming normal network conditions, this should occur 2 generations after the block is hit after the first TTD, or approximately 13 minutes!
New JSON-RPC block tags, confirmed, returns the most recently completed block, or returns an error if there are no blocks after merging. This tag can be used in your application to determine whether a merge has completed. Likewise, smart contracts are also possible. Queries difficulty Operation code (0x44)Name changed to Prebrandao After merging, check to see if the merge occurred. We recommend that infrastructure providers monitor overall network stability in addition to completion status.
client release
The next client release will support Merge across the Goerli & Prater testnet. Node Operator must be running. both Execution and consensus layer clients that remain on the network during and after the merge.
When choosing which clients to run, validators should keep in mind the risks of running the majority of clients, especially on both EL and CL. You will find a description of these risks and their consequences here. here. You’ll find estimates of the current EL and CL client distribution and guidance for transitioning from one client to another. here.
consensus layer
execution layer
Upgrade specifications
Significant changes to the agreement for The Merge are specified in two places.
- The consensus hierarchy changes as follows: bellatrix directory Consensus specification repository
- The execution layer changes. fly speculation From the executable spec repository:
In addition to this, there are two other specifications that cover how the consensus and execution layer clients interact.
- The engine API is Execution API RepositoryIt is used for communication between the consensus layer and the execution layer.
- Optimistic synchronization (specified in) tuning Folders in the consensus specification repository are used by the consensus layer to fetch blocks when execution layer clients synchronize and to provide a partial view of the chain head from the former to the latter.
frequently asked questions
What do I do as a node operator?
After merging, an Ethereum full node combines a consensus layer (CL) client that runs the proof-of-stake beacon chain and an execution layer (EL) client that manages user state and executes related computations. work. It communicates over authenticated ports using a new set of JSON RPC methods: Engine API. EL and CL clients authenticate each other using JWT secrets. Node operators should refer to their client’s documentation for instructions on how to create and configure them.
This means that if you were already running nodes on the beacon chain, you now need to run the execution layer client as well. Likewise, if you are currently running a node on a proof-of-work network, you will need to run a consensus layer client. To communicate securely, a JWT token must be passed to each client. You can find summarized instructions for running a node on the Goerli/Prater network. here.
Although both are part of the consensus layer client release, it is worth emphasizing that running a beacon node is different from running a validator client. Stakers need to run both, but node operators only need the former. this post The differences between the two components are explained in detail.
Additionally, each layer maintains an independent set of peers and exposes its own API. that much beacon and JSON RPC All APIs continue to work as expected.
What should I do as a staker?
The Goerli/Prater merge is our last opportunity to ensure that our validators are configured correctly before the mainnet transition. We recommend executing the transition now to avoid unexpected issues on mainnet.
As explained above, In addition to the consensus layer client, the validator of the beacon chain must also run a post-merge execution layer client. Pre-merge is strongly recommended, but validators can also outsource these functions to third-party providers. This was possible because the only data needed by the execution layer were updates to the deposit contract.
After merging, validators must verify that the transactions in the blocks they create and prove are valid. This requires each beacon node to be paired with an execution layer client. Multiple validators can still be connected to a single beacon node and execution layer client combo. This expands the responsibilities of validators while giving validators proposing blocks the right to the associated transaction priority fees (currently passed on to miners).
Validator rewards are accumulated on the beacon chain and require a subsequent network upgrade to be withdrawn, but transaction fees continue to be paid, burned, and distributed by the execution layer. Validators can designate any Ethereum address as the recipient of transaction fees.
After updating the consensus client, you must fee recipient It is part of the validator client configuration to ensure that transaction fees are sent to addresses you control. If you use a third-party provider to stake, it is up to the provider you choose to specify how these fees are allocated.
Prater Stake Launchpad Merge Preparation Checklist It can be used to check if the staker has passed each step of the process. The EthStaker team also Merge Validator Preparation Workshop July 29th.
Why the estimate? Final Total Difficulty Is dating that broad?
The variation in incremental difficulty per block allows us to estimate the following window: TTD It is more difficult than block or epoch height, so the expected range is wider. Users should note that this also applies to mainnet transitions due to Proof-of-Work hash rate changes.
What should I do as an application or tool developer?
With The Merge rolling out to Goerli, now is the last opportunity to verify that the product is working as expected with Proof-of-Stake conversion and post-merge context. As explained in previous post, a merge has minimal impact on a subset of contracts deployed on Ethereum, none of which must be violated. Additionally, most of the user API endpoints remain stable (unless you use proof-of-work specific methods, such as: eth_getWork).
That said, most applications on Ethereum involve much more than on-chain contracts. Now is a golden opportunity Ensure that frontend code, tools, deployment pipelines, and other off-chain components are working as intended. Developers are strongly encouraged to run a full test and deployment cycle on Sepolia, Ropsten, or Kiln and to report any issues related to tools or dependencies to the maintainer for that project. If you are not sure where to open the issue, use: this repository.
Additionally, all testnets except Sepolia and Goerli will be deprecated after the merge. If you are a Ropsten, Rinkeby or Kiln user, you should plan to migrate to Goerli or Sepolia. You can find more details about this. here.
Is there anything I need to do as an Ethereum user or Ethereum holder?
no. The Ethereum mainnet is not affected by this testnet. Follow-up announcements will be made through this blog before the mainnet transition.
Is there anything I need to do as a miner?
no. If you mine on the Ethereum mainnet, you should know that after The Merge, the network will operate entirely on Proof-of-Stake. At that point mining will no longer be possible on the network.
Can I withdraw my stake as a validator?
no. The merge is the most complex upgrade to Ethereum to date. To minimize the risk of network outage, a minimalist approach was taken with this upgrade, excluding any untranslated changes.
Withdrawals from the beacon chain will likely be introduced in the first upgrade after The Merge. Specifications of both products consensus and execution Layers are in progress.
I have more questions. Where can I ask?
The EthStaker community has set up a Discord channel to answer questions from stakers and node operators. You too can join their feud here after that #goerli-talk This is a channel where you can get help. As mentioned above, EthStaker also Merge Validator Preparation Workshop July 29th.
additionally, Community currency merge It is scheduled for August 12th at 14:00 UTC. Client developers and researchers can answer questions from node operators, stakers, infrastructure and tool providers, and community members. This community call is expected to occur. ~ after Goerli/Prater merge.
Do you want to merge?
As of the time this post was published, the Ethereum mainnet proof-of-stake conversion time is as follows. ~ no It’s set. Any source that claims otherwise is likely a scam. Updates will be posted on this blog. Stay safe!
Assuming no issues are discovered during the Goerli/Prater merge, once the client has a feature-complete release, a slot height will be selected for the Bellatrix upgrade on the mainnet beacon chain. total difficulty value Set up for mainnet transition. The client then makes a release that activates The Merge on the mainnet. These will be announced through this blog and other community publications.
However, if at any point during the process we discover issues or determine that our testing coverage is insufficient, we will address these before continuing with the deployment process.
Only then can we estimate the exact date of The Merge.
In other words 🔜.
