> ## Content Index > Fetch the complete content index at: https://www.metatalks.ai/llms.txt > Use this file to discover other available public pages before exploring further. # The Importance of Client Diversity: Ethereum's Latest Stress Test - URL: https://www.metatalks.ai/the-significance-of-client-diversity-ethereums-latest-stress-test/ - Published: 2023-05-15T12:51:46.000Z - Updated: 2023-05-15T12:51:46.000Z - Author: Katelyn Chow - Tags: ethereum, #helen, beacon, techissues A few days after [Binance's BTC withdrawal issues](https://www.metatalks.ai/utter-binance-fud-or-reasonable-reminder/) because of Bitcoin network congestion, Ethereum's Beacon chain temporarily [stopped finalizing](https://blockworks.co/news/beacon-chain-temporarily-stops-finalizing?ref=metatalks.ai) transactions – [twice a 24h](https://www.coindesk.com/tech/2023/05/12/ethereum-resumes-finalizing-blocks-after-second-performance-hiccup-in-24-hours/?ref=metatalks.ai) on last Thursday and Friday. ![](https://storage.ghost.io/c/ef/d4/efd46b24-40c6-4ee1-b2e7-34720b3b26fd/content/images/2023/05/data-src-image-79271434-9ec0-4cca-bd0c-fd4753d36ad4.png) ![](https://storage.ghost.io/c/ef/d4/efd46b24-40c6-4ee1-b2e7-34720b3b26fd/content/images/2023/05/data-src-image-03ad51d7-0d78-4990-9eb2-0525b4e59220.png) For regular users, the impact was minimal. The only noticeable effect was a slightly longer transaction processing time and a somewhat lower guarantee of finality for about 25 minutes. > The beacon chain did not "halt", to suggest that it did is willfully spreading misinformation. Finalization was delayed for 3 epochs (about 19 minutes), and was recovered after turbulence. End users would have no idea this happened and transactions continued normally. > > — superphiz.eth 🦇🔊🛡️ (@superphiz) [May 12, 2023](https://twitter.com/superphiz/status/1657000847782338560?ref%5Fsrc=twsrc%5Etfw&ref=metatalks.ai) For the developer community, though, the incident was viewed as a significant test of the network's strength. Ethereum had difficulties in reaching a consensus, resulting in a brief yet severe decline in validator participation on the consensus layer. *“This led to a period of time where Ethereum blocks were not being finalized, but blocks were still being validated as normal on the execution layer,” –* [*said Blockworks Research Senior Analyst*](https://blockworks.co/news/beacon-chain-temporarily-stops-finalizing?ref=metatalks.ai)*.* On Friday, the same problem emerged again, which doesn't seem to surprise either the Ethereum community members… ![](https://storage.ghost.io/c/ef/d4/efd46b24-40c6-4ee1-b2e7-34720b3b26fd/content/images/2023/05/data-src-image-dd5087b8-03f0-4a1e-9207-6587c6d39e1d.png) …or the Bitcoin folks: > Building a complex and secure app on Ethereum. [https://t.co/NumUZXHbmb](https://t.co/NumUZXHbmb?ref=metatalks.ai) > > — Willy Woo (@woonomic) [May 14, 2023](https://twitter.com/woonomic/status/1657593454229340171?ref%5Fsrc=twsrc%5Etfw&ref=metatalks.ai) But what really happened there? The precise cause is unknown yet at the time of writing, but [it was likely caused by a coincidence of two or three issues](https://blockworks.co/news/ethereum-finality-hiccup-decentralization?ref=metatalks.ai). During the incident, validators faced difficulties with Prysm and Teku nodes that were resolved primarily after a restart. A Prysm developer [@potuz1](https://twitter.com/potuz1?ref=metatalks.ai) explained ([thread](https://twitter.com/potuz1/status/1657031082749861891?ref=metatalks.ai)) that several valid but untimely attestations were broadcasted in the network, which takes place when a node attests with an outdated view of the chain. ![](https://storage.ghost.io/c/ef/d4/efd46b24-40c6-4ee1-b2e7-34720b3b26fd/content/images/2023/05/data-src-image-1450718f-09b6-43d8-97c9-85f3f09b5a61.png) Here you can find a [detailed thread](https://twitter.com/glassnode/status/1657745743086510080?ref=metatalks.ai) about what it looked like from the blockchain perspective: ![](https://storage.ghost.io/c/ef/d4/efd46b24-40c6-4ee1-b2e7-34720b3b26fd/content/images/2023/05/data-src-image-1c375177-c484-4594-851e-f346ed293d10.png) Hotfixes in both clients involved have now been [deployed](https://twitter.com/superphiz/status/1657303471098404866?ref=metatalks.ai). As for the lessons learned from the incident, the [experts agree](https://blockworks.co/news/ethereum-finality-hiccup-decentralization?ref=metatalks.ai) that the loss of finality could be prevented entirely if less than a third of all validators would run the same consensus layer software client, while currently, two clients, Prysm and Lighthouse, are estimated to be running on more than a third of Ethereum nodes, as per clientdiversity.org. So it's all about the significance of decentralization again. ![](https://storage.ghost.io/c/ef/d4/efd46b24-40c6-4ee1-b2e7-34720b3b26fd/content/images/2023/05/data-src-image-02e44c78-4d4a-4845-a898-5b9445c383df.png) Marius van der Wijden, a developer of the [Go Ethereum](https://twitter.com/go%5Fethereum?ref=metatalks.ai) execution layer client for Ethereum, [called](https://twitter.com/vdWijden/status/1656790867506520064?s=20&ref=metatalks.ai) this incident "a great fire drill" for the network, emphasizing that client diversity was critical to the network's ability to recover from such an event. ![](https://storage.ghost.io/c/ef/d4/efd46b24-40c6-4ee1-b2e7-34720b3b26fd/content/images/2023/05/data-src-image-bd350ed7-9ca3-4080-832a-bfe2f5fa3237.png)