292 Interactions, 6 today
Shortly after the Berlin hard fork, Etherscan and OpenEthereum were trapped on a single block.
On Thursday afternoon UTC, the OpenEthereum client for Ethereum, formerly known as the Parity client, is allegedly malfunctioning for a variety of users, including the common block explorer Etherscan.
According to multiple user reports on GitHub, the OpenEthereum client has been stuck on block 12,244,294, or just 294 blocks after the Berlin hard fork was executed. The error message seems to indicate that the client is rejecting the new blocks, thinking that its state Merkle root is invalid.
The problem appears to be limited to OpenEthereum nodes, with the more common Geth operating normally. Due to issues with the OpenEthereum client, Etherscan, the popular block explorer, was unavailable. Its homepage lists block 12,244,294 as the most recently mined block, despite the fact that other explorers are correctly updating.
It is still unknown what caused the issue, and the team is actively working to diagnose and resolve it. Etherscan will remain inoperable before that occurs.
Since the problem still concerns OpenEthereum, the Ethereum network and several service providers, such as Infura, continue to function normally. This time, unlike the previous consensus bug, there is no alternate chain of its own transactions. Given the timing of the Berlin hard fork, some of the modifications seem to have been applied inappropriately.