BlockBeats News, December 14th: The Prysm team released an incident retrospective report stating that during the Ethereum mainnet Fusaka period on December 4th, almost all Prysm validator nodes experienced resource exhaustion when processing specific attestations, resulting in delayed responses to validator requests and causing a significant number of missed blocks and attestations.The incident affected 42 epochs from epoch 411439 to 411480, with 248 missing blocks out of 1344 slots, resulting in an approximate 18.5% miss rate. Network participation briefly dropped to 75%, and validators lost approximately 382 ETH in attestations rewards. The root cause was Prysm receiving attestations from potentially out-of-sync nodes with the mainnet, referencing the block root of the previous epoch. To validate their legitimacy, Prysm repeatedly replayed old epoch states and performed costly epoch transitions, leading to resource exhaustion under high concurrency.The Prysm team provided a temporary solution by enabling the --disable-last-epoch-target parameter in version 7.0.0. Subsequently released versions 7.0.1 and 7.1.0 include a permanent fix that validates attestations using the head state to avoid re-replaying historical states.

#ETH