Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Ethereum consensus client Prism said validators lost 382 ether, equivalent to more than $1 million, after a software bug caused network disruptions immediately after the recent Fusaka update.
The post-incident report titled “Prism Incident on Fusaka Mainnet” explained that the incident occurred as a result of resource exhaustion that affected almost all Prism nodes and resulted in the loss of blocks and certificates.
Sponsored
Sponsored
What caused Prysm to be discontinued?
Chain Labs’ Prism developer said the problem appeared on December 4 when a software bug introduced earlier caused delays in auditor requests.
That delay resulted in the loss of blocks and certificates at the network level.
The project explained that Prism Beacon nodes received certificates from nodes that may be out of sync with the network, and those certificates indicated the root of a block from the previous session.
This disruption resulted in 41 lost spins, with 248 lost blocks out of 1,344 available lots. This represented a loss of 18.5% and reduced overall network traffic to 75% during the incident.
Off Chain Labs said that the bug responsible for this behavior was included and implemented in testnets about a month ago, before being activated on the main network. After Fusaka’s promotion.
Although a temporary mitigation reduced the immediate impact, Prism explained that it has since implemented permanent changes to the certificate verification logic to prevent the problem from occurring again.
Sponsored
Sponsored
Customer Diversity in Ethereum
At the same time, this interruption renewed the scrutiny Concentration of Ethereum customers And the risks caused by a single software.
Off Chain Labs said that this disruption could have led to more serious consequences if Prism had controlled a larger percentage of Ethereum Base Validator. The company pointed to the diversity of Ethereum’s customers as a key factor in preventing widespread network failure.
The company stated that if a client controls more than 1/3 of the network, it will lead to a temporary loss of the final shape and the loss of more blocks, while a faulty software client that controls more than 2/3 could make the chain unsuitable for the final installation.
Despite that precaution, the incident underscored the need to promote customer diversity.
Data from MegaLabs indicates that Lighthouse remains the dominant client for Ethereum by consensus, Representing 51.39% of listeners, Prism comes in second place with 19.06%, followed by Tico with 13.71% and Nimbus with 9.25%.
Put Lighthouse’s stake closer to 15% at a point away from what some researchers consider a systemic risk.
Developers and ecosystem participants have once again urged validators to consider switching to alternative clients to reduce the possibility that a single software bug could disrupt the blockchain’s core operations.
