After the day of affirmation for the Ethereum merge client update, two Ethereum clients, Nethermind and Go Ethereum have found bugs in their mainnet merge updates, which were fixed later.
Ethereum developer, Péter Szilágyi identified a regression in Go Ethereum’s latest update, Geth 1.10.22, also known as Promavess. He mentioned that the bug can cause the “trie/state to go bad.”
Also, he added that it could be one of the pull requests (PR) that “merged towards the new storage model / online pruner.”
The bug was critical as it could harm the running node with the v1.10.22 and could lose the data or corrupt the entire database.
However, in the latest update, Go Ethereum released Geth v1.10.23, Sentry Omega with a hotfix to patch a state corruption in v1.10.22.
While the Ethereum Merge is about to take place on or around September 15, this unpleasant news prompted panic in the community. Rumors also spread that these bugs could delay the Ethereum Merge. But there are fewer chances of it as there are other clients on Ethereum who already waved a green single for client update.
Also Read: Ethereum Mainnet Merge Clients launched
Those who already updated their nodes with 1.10.22 will have to set on the 2 days older state of the chain to re-run and ensure that everything is “OK” for Ethereum Merge.
On the other hand, the Ethereum core developer at Nethermind also identified similar bugs on their client update v1.14.0 and took the measure to switch to a strict stabilization phase before the Merge. This bug was fixed afterward.