Ethereum’s beacon chain suffers brief finality issue, cause still unknown

The Ethereum network appears to have suffered a technical issue that, for a temporary period, meant that transaction finality wasn’t occurring.

The cause of the issue isn’t clear as of press time and Ethereum developers say the situation is being investigated. For now, network data and statements from developers indicate that transaction finality — referring to the state in which transactions can’t be changed — has returned.

«Finality has been restored,» tweeted Prysmatic Labs co-founder Preston van Loon. «We do not know the root cause yet, but something happened to cause several client implementations to work really hard to keep up with the chain.»

Data sources for Ethereum network activity show that the issue was experienced by validators. Validators propose attestations as the network processes transactions.

Data provider Beaconcha.in shows that Ethereum epochs 200,552 thru 200,554 saw a steep drop in the number of attestations received. The first problematic epoch was at 4:13 p.m. ET. The issue was resolved within a half hour, network data shows.

EthereumPools.info tweeted that «[f]or a couple of epochs almost every pool/operator that we monitor went offline.»

In the wake of the incident, community members pointed to client diversity — meaning a variety of software clients available for use by validators — as a reason for why the issue wasn’t more widespread or long-lasting.

This story is developing.

Source