This does not affect the -suggested-fee-recipient flag. We advise that anyone using the -strict-fee-recipient flag should remove it and restart the Validator Client as soon as possible. We are presently inside that period of time and therefore all stakers using that flag are affected.
The -strict-fee-recipient flag for the Lighthouse Validator Client has also been found to prevent block proposals in the period between the Bellatrix upgrade (Sept 6th) and the TTD date (estimated Sept 15th). Warning: Lighthouse version v3.1.0 is a high-priority release contains an important fix to ensure that Lighthouse does not attempt to produce invalid blocks. It also improves compatibility with Besu, Prysm and slow block builders and provides a speed boost in block processing important for those running on Raspberry Pi and similar hardware. Warning: Nimbus version v22.9.0 is a high-urgency upgrade that fixes a critical pre-TTD block production issue affecting users that restarted their node after Bellatrix. An estimate of current EL and CL client distribution and guides for switching from one client to another can be found here. An explainer of these risks and their consequences can be found here. When choosing which client to run, validators should be especially mindful of the risks of running a majority client on both the EL and CL. Node operators must run both an execution and consensus layer client to remain on the network during and after The Merge. The following client releases support The Merge on the Ethereum mainnet. We recommend infrastructure providers monitor overall network stability in addition to finalization status. Similarly, smart contracts can query the DIFFICULTY opcode ( 0x44) (renamed to PREVRANDAO post-merge) to determine if The Merge has happened. This tag can be used by applications to check if The Merge has been completed. Under normal network conditions, this will happen 2 epochs (or ~13 minutes) after the first post-TTD block is produced!Ī new JSON-RPC block tag, finalized, returns the latest finalized block or an error if no such post-merge block exists. The Merge transition is considered complete once the Beacon Chain finalizes this block. Once the execution layer reaches or exceeds the TTD, the subsequent block will be produced by a Beacon Chain validator. Estimates for the transition can be found at bordel.wtf and 797.io/themerge. The exact date at which TTD is reached depends proof-of-work hash rate. Paris, the execution layer's portion of the transition, will be triggered by the Terminal Total Difficulty (TTD) of 58750000000000000000000, expected between Sept 10-20, 2022. The Bellatrix upgrade is scheduled for epoch 144896 on the Beacon Chain - 11:34:47am UTC on Sept 6, 2022. This is followed by the execution layer's transition from proof-of-work to proof-of-stake, Paris, triggered by a specific Total Difficulty threshold called the Terminal Total Difficulty ( TTD). The first step is a network upgrade, Bellatrix, on the consensus layer triggered by an epoch height. Second, the upgrade activates in two phases: the first, named Bellatrix, at an epoch height on the Beacon Chain, and the second, named Paris, upon hitting a Total Difficulty value on the execution layer.
First, node operators need to update both their consensus layer (CL) and execution layer (EL) clients in tandem, rather than just one of the two. The Merge is different from previous network upgrades in two ways. Operators will shut down on September 6, 2022.įollowing years of hard work, Ethereum's proof-of-stake upgrade is finally here! The successful upgrade of all public testnets is now complete, and The Merge has been scheduled for the Ethereum mainnet.