The Ethereum consensus layer client side Prysm team released the post-mortem analysis report of the Fusaka mainnet failure, and Prysm experienced a network failure on December 4.
During the event, almost all Prysm nodes experienced resource exhaustion while processing specific proofs, resulting in the inability to respond to validator requests in a timely manner. The failure affected epochs 411439th to 411480th, with a total of 248 blocks lost in 42 epochs, a missing rate of 18.5%, a minimum network participation rate of 75%, and a validator lost about 382 ETH of proof rewards.
The root of the fault occurs because Prysm beacons receive proofs sent by potentially out-of-sync nodes that reference the block root of the previous round. To verify these proofs, Prysm attempts to rebuild the compatibility state, resulting in repeated processing of blocks from past rounds and expensive round conversion recalculations.
The team addressed the issue temporarily by instructing users to use --disable-last-epoch-target parameters, and subsequent v7.0.1 and v7.1.0 releases included long-term fixes.
Ethereum consensus layer client side Prysm released Fusaka mainnet December 4 failure post-mortem analysis report
2025-12-14 03:55:59
Disclaimer:
1. The information provided does not constitute investment advice. Investors should make independent decisions and bear all risks themselves.
2. The copyright of this content belongs to the original author. The views expressed herein are solely those of the author and do not represent the stance or position of this website.
Previous article：
以太坊共识层客户端Prysm发布Fusaka主网12月4日故障事后分析报告Next article：
金色午报 | 12月14日午间重要动态一览
