Ethereum Announces Announcement, Mainnet Merger Enters Countdown
Original title: "ethereum foundation blog: Mainnet Merge Announcement"
Original author: Protocol Support Team
Original compilation: Unitimes
< /p>
· Ethereum is moving to Proof of Stake (PoS)! This transition is called The Merge (The Merge), and must first be activated via the Bellatrix upgrade on the Beacon Chain. 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 2022 September 6th ;UTC time 11:34:47 at 144896 epoch of the beacon chain.
· The total difficulty value of the terminal that triggers the merge is 587500000000000000000000, estimated at Between September 10 and 20, 2022.
· Note: As previously announced, the Kiln testnet is about to be deprecated and the operator will closed.
Background
After years of hard work, Ethereum’s The 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 previous network upgrades in two ways. First, node operators need to update both their Consensus Layer (CL) Client and Execution Layer (EL)< b>client, not just one of them. Second, this upgrade is activated in two stages: the first stage is called Bellatrix, and will be completed at a certain epoch height on the beacon chain; the second stage is called Paris, will complete when the execution layer reaches a predetermined total difficulty value.
Upgrade Information
Time
The merger is divided into two steps, the first step is At a certain epoch height, the Bellatrix network upgrade is triggered at the consensus layer. Subsequently, the execution layer transitions from Proof-of-Work (PoW) to Proof-of-Stake (PoS), a step called Paris, controlled by a process called Terminal Total Difficulty (TTD) triggers at a certain total difficulty value.
Bellatrix upgrade scheduled for September 6, 2022 at 11:34:47 AM UTC Carried out when the chain height reaches 144896.
The execution layer upgrades Paris, and the total difficulty value will reach 58750000000000000000000< /b> on , which is expected to be between September 10th - September 20th, 2022. The exact date of reaching TTD depends on the computing power of proof of work. For the estimated transition time, you can find it at bordel.wtf and 797.io/themerge Found.
Once the execution layer reaches or exceeds a predetermined TTD value, the beacon chain validators 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 in 2 epochs (about 13 minutes).
A new JSON-RPC block tag finalized, returns the latest finalized block, or if not If such a merged block exists, an error is returned. Applications can use this tag to check whether a merge has completed. Similarly, smart contracts can query DIFFICULTY ;opcode (0x44) (renamed to PREVRANDAO after the merge) to determine if a merge occurs. We recommend that infrastructure providers monitor overall network stability in addition to monitoring final state.
Client Version
The following client versions support merge upgrades of the Ethereum mainnet, note that node operators must run both execution layer and consensus layer clients in order to remain on the network during and after the merge.
When choosing which client to run, validators should pay special attention to the risk of running a majority of clients on EL and CL. You can run it here Find an explanation of these risks and their consequences. You can also find estimates of the execution and consensus layer client distributions, and switching from one client here A guide to another client.
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
2) Execution layer client
Client: Besu
Version: 22.7.1
Client: Erigon
< /p>
Version: v2022.08.02-alpha
Client: go-ethereum (geth) < /b>
Version: v1.10.23
Client: Nethermind
Version: v1.14.0
Warning: geth v1.10.22 version client contains serious database problems, do not use this version, if you are using this version of the client, please upgrade to v1.10.23 as soon as possible.
Upgrade specification
Consensus critical changes merged in two Specified here:
1. The consensus layer is based on the The Bellatrix directory has changed.
2. Execution layer according to Paris specification has changed.
In addition to this, two other specifications cover how consensus layer and execution layer clients interact:
1. In execution-apis The Engine API specified in the repository is used for communication between the consensus layer and the execution layer.
2. In the consensus specification repository sync folder is used by the consensus layer to import blocks when the client side of the execution layer is synchronized, and provides a link from the former to the latter partial view of the chain head.
Incorporated bug bounty program
Between now and 9 All merge-related bug bounties will have a 4x multiplier during the period of August 8th. Serious bug bounties can go up to $1 million.
For more details, see Vulnerabilities Bounty Program .
FAQ
1. Operate as a node Merchant, what should I do?
After the merger, the Ethereum full node is a combination of the consensus layer (CL) client and the execution layer (EL) client, the former Runs the proof-of-stake beacon chain, which manages user state and runs transaction-related computations. Execution Layer (EL) and Consensus Layer (CL) clients use a set called Engine API New JSON RPC method to communicate 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 executive 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. "Run a Node" section of the ethereum.org website< /a> The update describes these steps in more detail.
It is worth emphasizing that while they are both part of the consensus layer client version, running a beacon chain node is not the same as running a validator client. Stakers must run both, while node operators only need to run the former. This article in more detail The difference between these two components is explained.
Also, note that each layer will maintain an independent set of peer nodes and expose its own API. Beacon API JSON RPC API will continue to work as expected.
2. As a staker, what do I need to do?
As mentioned above, in addition to running the consensus layer client, validators on the beacon chain also need to run Execution layer client. 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.
After the merger, validators must ensure that the blocks of user transactions and state transitions they created and attested to are valid. To do this, each beacon chain node must be paired with an execution layer client. Note that multiple validators can still be paired with a single beacon chain node and execution layer client combination. This expands validator responsibilities, but also entitles validators who propose blocks to associated transaction priority fees (which currently belong to miners).
While validator rewards are still generated on the beacon chain and require subsequent network upgrades to withdraw, transaction fees will be paid, burned and distribute. 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 Make sure to send transaction fees to an address 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 a merge readiness A checklist that 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 Terminal Total Difficulty (TTD) so wide?
The increased difficulty of each block depends on the unstable network computing power, if more computing power joins the network, then TTD will be reached sooner. Similarly, if computing power leaves 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. As an application or tool developer, what should I do?
As stated in the 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 like 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. See this link for more information on this .
5. As an Ethereum user or ETH holder, what do I need to do?
Whether you are using Ethereum applications on the chain, or holding ETH on the trading platform, or in your own wallet , 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. As an Ethereum miner, what else can I do?
No, if you mine on the Ethereum mainnet, you should know that after the merger, the network will be fully Proof of Stake (PoS) algorithm, at that time, 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 the Ethereum client you are using is not updated to the latest version (listed above), once the network upgrade is complete, your Clients will sync to the pre-forked blockchain.
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 merger is by far the most complex upgrade to Ethereum, in order to minimize Risk of network disruption, we have taken a minimal approach that excludes any non-transitional changes in this upgrade.
Withdrawals from the beacon chain may 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 9 at 14:00 UTC there will be a community call about the merge where you can talk to the client Join developers, ETHStaker members, researchers, and more!
Thanks
< /p>
Ethereum's transition to Proof-of-Stake (PoS) has been in the works for a long time. Thanks to everyone who contributed to research, develop, analyze, test, break, fix, or explain 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.
When will it be merged? will be very fast.
Original link
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia
Related Articles
