Ethereum Prysm Client Bug Leads to 25% Validation Participation Drop, Risking Finality

On December 5, shortly after the Ethereum network’s Fusaka upgrade, a bug in the Prysm consensus client triggered a sharp drop in validator participation rates—with a large number of voting nodes going offline. In a Thursday announcement, Prysm explained its v7.0.0 client unnecessarily generated an outdated state while processing stale attestations, causing node malfunctions. Developers advised users to temporarily launch the client with the `--disable-last-epoch-targets` flag as a workaround. Data from Beaconcha.in shows that in Epoch 411,448, the network’s sync participation and voting participation rates fell to 75% and 74.7%, respectively. Voting participation dropped by 25%, coming just 9 percentage points short of the two-thirds (66.6%) supermajority required to maintain network finality. The decline’s magnitude roughly aligns with Prysm’s share of network validators, suggesting attestation failures were concentrated among Prysm users. Previously, Prysm’s share peaked at 68.1%. As of press time, the network’s current Epoch (411,712) has a voting participation rate near 99% and sync participation at 97%—signaling full recovery. MigaLabs data now shows Lighthouse holds 52.55% of consensus nodes, with Prysm ranking second at 18%. Ethereum educator Anthony Sassano noted that if Lighthouse had encountered this bug, the network would have lost finality. (Source: Cointelegraph)