Original title: "ethereum foundation blog: Mainnet Merge Announcement"
Author: Protocol Support Team
Original compilation: Unitimes
Ethereum is moving to Proof of Stake (PoS)! This transition is calledThe Merge, must first be activated on the Beacon Chain via the Bellatrix upgrade. Afterwards, the Ethereum Proof-of-Work (PoW) chain will migrate to Proof-of-Stake (PoS) when a certain total difficulty value is reached.
According to the plan, the Bellatrix upgrade will be in 2022September 611:34:47 UTC at epoch 144896 of the beacon chain.
The total difficulty value of the terminal that triggers the merger is 58750000000000000000000, which is expected to be inBetween 10 and 20 September 2022。
background
background
After years of hard work, Ethereum’s PoS upgrade is finally here! All public testnets have now been successfully upgraded, and a merged upgrade to the Ethereum mainnet has been scheduled.
The merger differs from past network upgrades in two ways. First, node operators need to update bothIts consensus layer (CL) client and execution layer (EL) client, not just one of them. Second, this upgrade is activated in two phases: the first phase is calledBellatrix, will be completed at a certain epoch height on the beacon chain; the second stage is calledParisfirst level title
secondary title
time
Merging is divided into two steps, the first step is triggered at the consensus layer at a certain epoch heightBellatrix Network Upgrade. Subsequently, the execution layer transitions from Proof-of-Work (PoW) to Proof-of-Stake (PoS), a step known asParis, by a term called the terminal total difficulty (TTD) Triggered by a specific total difficulty value of .
The Bellatrix upgrade is scheduled forSeptember 6, 2022 at 11:34:47 AM UTCCarry out when beacon chain height reaches 144896.
And the execution layer upgrades Paris, will be in TTD The total difficulty value reached 58750000000000000000000 is triggered at , which is expected to occur atBetween September 10th - September 20th, 2022as well asbordel.wtfas well as797.io/themergeturn up.
Once the execution layer reaches or exceeds the predetermined TTD value, the beacon chain validator will be responsible for generating subsequent blocks. Once the beacon chain finalizes the block, the merge upgrade is considered complete. Under normal network conditions, the first block generated after the TDD difficulty value is reached will be finalized within 2 epochs (about 13 minutes).
A new JSON-RPC block tag finalizedbybyQuery DIFFICULTY opcode (0x44)(renamed to PREVRANDAO after the merge)secondary title
client version
The following client versions support merge upgrades to the Ethereum mainnet. Note that node operators must run both the execution layer and the consensus layer client in order to remain on the network during and after the merge.
herehereherehereFind estimates of the distribution of clients in the execution and consensus layers, as well as guidelines for switching from one client to another.
1) Consensus layer client
client:Lighthouse
Version: v3.0.0
client:Lodestar
Version: v1.0.0
client:Nimbus
Version: v22.8.0
client:Prysm
Version: v3.0.0
client:Teku
Version: 22.8.1
client:Erigon
Version: v2022.08.02-alpha
client:go-ethereum (geth)
Version: v1.10.23
client:Nethermind
Version: v1.14.0
secondary title
upgrade specification
Merged consensus key changes are specified in two places:
1. The consensus layer is based on the consensus specification repositoryBellatrixTable of contentschange.
2. The execution layer executes theParisspecificationchange.
In addition to this, two other specifications cover how consensus layer and execution layer clients interact:
1. inexecution-apisThe Engine API specified in the repository is used for communication between the consensus layer and the execution layer.
2. In the consensus specification repositorysyncsecondary title
Incorporating a Bug Bounty Program
Between now and September 8th, all merge-related bug bounties will have a 4x multiplier. Serious bug bounties can go up to $1 million.
secondary titleBug bounty program 。
FAQ
1. As a node operator, what should I do?
Post-merger, Ethereum full nodes are a combination of Consensus Layer (CL) clients running the Proof-of-Stake beacon chain and Execution Layer (EL) clients managing user state and running transaction-related computations. Execution Layer (EL) and Consensus Layer (CL) clients use a set ofEngine APIA new JSON RPC method for communicating over authenticated ports. Execution Layer (EL) and Consensus Layer (CL) clients authenticate each other using JWT keys. Node operators should refer to their client's documentation for instructions on how to generate and configure this value.
In other words, if you already have a node running on the beacon chain, you now also need to run an execution layer client. Likewise, if you run a node on the current proof-of-work (PoW) network, you also need to run a consensus layer client. In order for them to communicate securely, a JWT token must be passed to each client. The ethereum.org website's"Run a Node" sectionThe update describes the steps in more detail.
This articleThis articleThe difference between these two components is explained in more detail.
andBeacon APIandJSON RPC APIBoth will continue to work as expected.
2. What do I need to do as a staker?
As mentioned above, in addition to running the consensus layer client, validators on the beacon chain also need to run the execution layer client after the merger. Stakers are strongly encouraged to do so before merging, but some validators have outsourced these functions to third-party providers. This is possible because the only data required by the execution layer is the update of the deposit contract.
While validator rewards are still generated on the beacon chain and require subsequent network upgrades to be withdrawn, transaction fees will be paid, burned and distributed on the execution layer. Validators can designate any Ethereum address as a recipient of transaction fees.
While validator rewards are still generated on the beacon chain and require subsequent network upgrades to be withdrawn, transaction fees will be paid, burned and distributed on the execution layer. Validators can designate any Ethereum address as a recipient of transaction fees.
After updating the consensus client, be sure to set fee recipient as part of the validator client configuration to ensure transaction fees are sent to addresses you control. If you use a third-party provider for staking, it is up to the provider you choose to specify how these fees are distributed.
Staking Launchpad has aMerge Readiness Checklist, which stakers can use to ensure they complete each step of the process. EthStaker also held validator readiness workshops, with more workshops planned.
Stakers who wish to run validators on a testnet in preparation for the mainnet PoS transition can do so on the Goerli testnet (now merged), which also has a Staking Launchpad instance.
3. Why is the estimated date range for TTD so wide?
The increased difficulty of each block depends on the unstable network computing power, if more computing power joins the network, the TTD will be reached faster. Similarly, if computing power withdraws from the network, the arrival time of TTD will be delayed. In the event of a significant drop in hashrate levels, a TTD coverage value can be coordinated as has been done on the Ropsten testnet.
4. What should I do as an application or tool developer?
As stated in a previous post, the merge has minimal impact on the subset of contracts deployed on Ethereum, none of which should be broken. Also, most of the user API endpoints will remain stable (unless you use proof-of-work specific methods such as eth_getWork).
That said, most applications on Ethereum involve far more than on-chain contracts. Now is the time to ensure that front-end code, tooling, deployment pipelines, and other off-chain components work as expected. We strongly recommend that developers run a full test and deploy cycle on Sepolia or Goerli, and report any tooling or dependency issues to the maintainers of those projects. If you're not sure where to open issues, please use this repository.
Also, note that all testnets, except Sepolia and Goerli, will be deprecated after the merge. If you are a user of Ropsten, Rinkeby or Kiln, you should plan to migrate to Goerli or Sepolia. For more information on this, seethis link 。
5. What do I need to do as an Ethereum user or ETH holder?
Whether you're using Ethereum applications on-chain, holding ETH on an exchange, or in a wallet in your own custody, you don't have to do anything. If the app, trading platform, or wallet you use provides additional instructions or advice, you should verify that those instructions or advice come from them. Beware of scams!
6. What else can I do as an Ethereum miner?
No, if you are mining on the Ethereum mainnet, you should know that after the merger, the network will run entirely under the Proof of Stake (PoS) algorithm, at which point POW mining will no longer be possible.
7. What happens if I am a miner or node operator and I am not involved in the upgrade?
If you are using an Ethereum client that is not updated to the latest version (listed above), your client will sync to the pre-forked blockchain once the network upgrade is complete.
You will be stuck on an incompatible chain following the old rules, unable to send ether or operate on the merged ethereum network.
8. As a validator, can I withdraw my pledged ETH rights?
No, the merge is the most complex upgrade to Ethereum to date, and to minimize the risk of network disruption, we took a minimal approach that excluded any non-transitional changes in this upgrade.
Withdrawals from the beacon chain, likely to be introduced in the first post-merger upgrade. The specifications of the consensus layer and the execution layer are under development.
9. I have more questions, where can I ask them?
On September 9th at 14:00 UTC there will be a community call about the merge where you can join client developers, ETHStaker members, researchers, and more!
thank you
Ethereum’s transition to Proof-of-Stake (PoS) has been in the works for a long time. Thanks to everyone who contributed to researching, developing, analyzing, testing, breaking, fixing, or explaining everything about The Merge.
There are too many contributors over the years to list here, but you know who you are. We could not have built this cathedral without all of you.
Original link
