Ethereum's Beacon Chain is updated after finality issues
Ethereum core developers rolled out patches for Prysm Labs and Teku clients as a response to two Beacon Chain finality issues within a 24-hour period. The Beacon Chain serves as the consensus layer for the Ethereum network.
On May 11, Ethereum developers reported that the Beacon Chain was experiencing problems confirming transactions. Although new blocks were able to be proposed, an unknown issue prevented their finalization. The outage lasted around 25 minutes. A similar issue took place on May 12, preventing block finalization for over an hour.
Finality was unable to be reached for 3 and 8 epochs, said the Ethereum Foundation in a statement shared by an Ethereum consultant on Twitter. The issue "appears to have been caused by high load on some of the Consensus Layers clients, which in turn was caused by an exceptional scenario."
The beacon chain stopped finalizing about thirty minutes ago. I don't know why yet, but in general the chain is designed to be resilient against this, transactions will continue as usual and finalization will kick in when the problem is resolved. pic.twitter.com/utAS0uAWpG
Although the network was unable to finalize, live and end users were able to transact on the network thanks to client diversity "as not all client implementations were affected by this exceptional scenario."
Client diversity relates to the number of software clients available to network validators. Greater diversity among clients means a more robust and secure network.
Both Teky and Prysm have released upgrades that implement optimizations to prevent beacon nodes from consuming excessive resources.
A similar issue took place on March 15, resulting in a delay in the Goerli testnet version of Ethereum's "Shapella" upgrade, which
Read more on cointelegraph.com
