Month-old Ethereum client bug blamed for Prysm outage

cointelegraphPublished on 2025-12-15Last updated on 2025-12-15

Abstract

A month-old bug in the Prysm Ethereum client caused a significant outage on December 4, leading to resource exhaustion and performance degradation. The issue occurred when Prysm nodes processed attestations from out-of-sync nodes, forcing them to recompute expensive state transitions. Although the bug had been present on testnets for a month prior, it wasn’t triggered until the mainnet incident. The network experienced an 18.5% missed slot rate for over 42 epochs, with participation dropping to 75%, resulting in approximately 382 ETH lost in attestation rewards. A patch was quickly deployed to resolve the issue. Developers emphasized that client diversity helped prevent a more severe impact, as Prysm only holds a 17.6% share of the network. However, they warned that Lighthouse, the dominant client with 52.6% share, is nearing a dangerous threshold where a single bug could finalize an invalid chain.

Prysm has revealed that a bug introduced in a testnet a month before Ethereum’s Fusaka upgrade was the cause of an Ethereum node validation issue that affected its client earlier this month.

Ethereum developer Terence Tsao posted a post-mortem on Sunday detailing the Fusaka mainnet Prysm incident that impacted the network on Dec. 4.

Prysm nodes experienced “resource exhaustion” when processing attestations from out-of-sync nodes, it stated. This caused Prysm to replay past epoch blocks and recompute expensive state transitions, resulting in a significant impact on performance due to the excessive workload.

The post-mortem revealed that the bug had been present on testnets for a month before the incident, but wasn’t triggered.

“The bug was introduced in Prysm PR 15965 and deployed to testnets a month before the incident without the trigger happening.”

Testnets are designed to identify bugs, but they aren’t a foolproof method.

In May 2023 — a month after the Shanghai hard fork — Ethereum developers were sent into a frenzy when the network temporarily lost transaction finality for around 25 minutes, then again for over an hour the following day, before the blockchain recovered on its own.

Prysm has been patched

Instead of using the current head state, Prysm regenerated prior states from scratch, creating a massive computational burden.

For more than 42 epochs, the network saw an 18.5% missed slot rate with participation dropping to 75% while validators lost approximately 382 Ether (ETH) in attestation rewards, it said.

Related: Vitalik Buterin says Ethereum can handle temporary loss of finality

Node operators were instructed to deploy a temporary solution while developers worked on an update patch for Prysm clients.

Client diversity saved the day

The incident could have been much worse if it had hit Ethereum’s dominant consensus client, Lighthouse, said developers.

Offchain Labs’ Prysm is the second-largest Ethereum client with a 17.6% share, according to ClientDiversity.

“Client diversity prevented a noticeable impact on Ethereum users. A client with more than 1/3rd of the network would have caused a temporary loss in finality and more missed blocks.”

However, the incident highlighted that Lighthouse is dangerously close to the two-thirds threshold where a single client bug could finalize an invalid chain.

Lighthouse currently has a client share of 52.6%, down from around 56% at the time of the incident.

Ethereum developers are pushing for more client diversity. Source: ClientDiversity


Magazine: Big questions: Would Bitcoin survive a 10-year power outage?

Related Reads

Cook's Curtain Call and Ternus Takes the Helm: The Disruption and Reboot of Apple's 4 Trillion Dollar Empire

Tim Cook has officially announced he will step down as CEO of Apple in September, transitioning to executive chairman after a 15-year tenure during which he grew the company’s market value from around $350 billion to nearly $4 trillion. He will be succeeded by John Ternus, a 50-year-old hardware engineering veteran who has been groomed for the role through increasing public visibility and internal responsibility. Ternus’s appointment signals a strategic shift toward hardware and engineering leadership, with Johny Srouji—head of Apple Silicon—taking on an expanded role as Chief Hardware Officer. This consolidation aims to strengthen Apple’s core technological capabilities. However, Cook’s departure highlights a significant unresolved issue: Apple’s delayed and fragmented approach to artificial intelligence. Despite early efforts, such as hiring John Giannandrea from Google in 2018, Apple’s AI initiatives—particularly around Siri—have struggled with internal restructuring and reliance on external partnerships, including with Google. The transition comes at a critical moment as Apple faces paradigm shifts with the rise of artificial general intelligence (ASI). The company’s closed ecosystem of hardware, software, and services—once a major advantage—now presents challenges in adapting to an AI-centric world where intelligence may matter more than the device itself. Ternus must quickly articulate a clear AI strategy, possibly starting at WWDC, to reassure markets and redefine Apple’s role in a new technological era. His task is not only to maintain Apple’s operational excellence but also to reinvigorate its capacity to innovate and lead in the age of AI.

marsbit2h ago

Cook's Curtain Call and Ternus Takes the Helm: The Disruption and Reboot of Apple's 4 Trillion Dollar Empire

marsbit2h ago

Trading

Spot
Futures

Hot Articles

Discussions

Welcome to the HTX Community. Here, you can stay informed about the latest platform developments and gain access to professional market insights. Users' opinions on the price of ETH (ETH) are presented below.

活动图片