$ETH — Prysm Releases Post-Mortem on April 12 Ethereum “Fusaka” Incident
The Prysm development team has published a detailed post-mortem report following the Fusaka mainnet incident that occurred on 04/12.
🔹 What happened?
The issue was caused by resource exhaustion on Prysm nodes. While processing asynchronous attestations, affected nodes began re-executing expensive state calculations, which overloaded the system and led to stalls.
🔹 Impact on the network
• Ethereum missed 41 epochs
• Network participation dropped to ~75%
• Validators were unable to perform duties, resulting in an estimated 382 ETH lost in rewards
• The Prysm team has since released fixes in v7.0.1 and v7.1.0
🔹 Key takeaway
This incident highlights the systemic risk of over-reliance on a single client. While the short-term losses were significant, the event acted as a real-world stress test—demonstrating that Ethereum’s decentralized design works. One client struggled, but the network as a whole remained resilient.
