Ethereum lightfire Chaindie Final problems led to 253 missed blocks in 2 days: Glassnode
Ethereum lightfire Chaindie Final problems led to 253 missed blocks in 2 days: Glassnode
The Illumfire Chain-which serves as a layer of consensus for the Ethereum network-had twice technical problems last week that led to the completion of blocks. While blocks were proposed, they were not validated within a 25-minute window.
The two incidents were registered on May 11th and 12th when more than 60 % of the examiners no longer performed their tasks, which led to a loss of finality.
loss of finality
according to the Glassnode essentially "final". in the state in which a large majority of the validators-two thirds of the overall deployment- The final state of the blockchain has confirmed and guarantees that a block and its processed transactions cannot be changed or removed from the blockchain.
The performance of the Beacon chain decreased last week because almost 60 % of the validators were offline and did not do their consensus. The analysis company found that around 3.68 % of the daily slots were missed and 253 blocks were not proposed in time. This is still significantly less than the 658 blocks that were lost in the Shapella upgrade.
Glassnode also found that some clients of the consensus layer came across older attests and forced to load older status for checking while trying to process new incoming certificates. As a result, this led to "overheating and malfunctions" of these systems.
Due to a different design approach, not all customers were affected. As a result, the validators who execute them were able to process transactions and create blocks.
In both cases, the examiners concerned were online again within 20 minutes or an hour. The participation rate rose easily to over 98 %.During the two losses at Finality, no end users were affected in Ethereum-Minnet and were able to carry out transactions in the network due to the customer. However, the second problem led to the very first inactivity leak, an emergency state that is used to restore the final validity on the beacon chain. In such a case, the inactive validators are punished until they are excreted from the chain or start participating.
On a rather technical level, some clients of the consensus layer encountered older attestations and goods to load older conditions for verification, while at the same time trying to deal with new incidents, which ultimately led to overheating and malfunctions of these systems. target = "_ blank" href = "https://t.co/qst8kvukoc" Data-wpel-Link = "external"> pic.twitter.com/qst8kvukoc
-Glassnode (@glassnode) 14. May 2023
after -effects
The developers of the Ethereum core published patches for Prysm Labs and Teku customers in response to the problem. In a statement An Ethereum consultant said due to the high utilization " Consensus Layers-Client was caused, which in turn was caused by an extraordinary scenario. ”
The two customers have published upgrades that implement optimizations to prevent Beacon nodes from consuming excessive resources.
The final validity problems are a result of the increased activity and the premium rates on Ethereum due to the Memecoin re-life, which triggered a massive increase in gas consumption in the network, whereby the fees achieved a 12-month high.
.
Kommentare (0)