Teku an Ethereum 2.0 client has released the update v22.8.1. which contains the Bellatrix upgrade and Merge transition configuration.
In a tweet on August 22, Ethereum 2.0 client Teku announced the availability of v22.8.1, a necessary update that prepares users for the Bellatrix upgrade on September 6 and the Merge on September 15.
All Mainnet nodes must be updated to the necessary Teku version in order to switch to proof-of-stake (PoS). It involves defining a default charge recipient via validators and connecting to a local execution client’s engine API.
Teku and the execution client must both be upgraded on Mainnet nodes in order to get ready for the Merge. Execution clients that are not updated will notify Teku of a “Merge transition configuration problem.”
The transition on the Mainnet node will be invalidated if the local terminal total difficulty (TTD) and terminal block hash values do not match distant execution client values.
Setting the Bellatrix fork epoch and TTD for the Merge, allowing several beacon nodes to be configured for a single validator client, and making it easier to use the common REST API are additional features and enhancements in the upgrade.
Additionally, it corrects issues with the terminal PoW block, calculates the payload, and repeatedly throws timeout exceptions.
Before the Bellatrix activation date on September 6, all Mainnet users must upgrade to version 22.8.1. Important configurations for the Merge preparation are included in the upgrade.
The Merge to lunch on September 15
On August 18, the most recent Ethereum Core Developers meeting confirmed a final mainnet TTD of 58750000000000000000000. It indicates that programmers are hopeful about the Merge’s launch on September 15.
Prior to this, Vitalik Buterin also reaffirmed that the Merge is dependent on the hash rate. On September 15, a hash rate of 872.2 TH/s is sufficient to reach the TTD of 58750000000000000000000. Data from OKLink’s “Ethereum The Merge Countdown” indicates that the hash rate right now is 872 TH/s.
