However, issues have been discovered in the Geth v1.10.22 (Promavess) and v1.14.0 Mainnet versions by Go Ethereum and Nethermind, respectively. However, since developers are working on speedy fixes and there are alternate execution clients available, the problems are not anticipated to cause the Merge to be delayed.
Ethereum Clients Report Merge Update Bugs in the Mainnet
In their Mainnet Merge upgrades, the Ethereum clients Go Ethereum and Nethermind discovered problems. On August 23, Ethereum developer Péter Szilágyi tweeted about a regression flaw in the Geth v1.10.22 release (Promavess). It is one of the pull requests (PR) that the team combined in order to create the online pruner or new storage model.
The Go Ethereum team is presently investigating and resolving the problem.
In response to Péter Szilágyi's tweet, Nethermind core developer "DanielC" stated that a similar regression fault was discovered in the release v1.14.0. The team decided to switch to a stringent stabilisation phase before to the Merge, which has resolved the problem.
The vulnerabilities are unlikely to affect the planned September 15 merging of the Ethereum Mainnet and Beacon Chain. Users have the option to change to minority execution clients. Other execution clients are available as well, which will aid in getting ready for the Mainnet Merge.
Additionally, the average hash rate of 872.2 TH/s needed for the Merge to take place on September 15 is met by the Ethereum hash rate.