🚀 Lido Protocol Resolves Prysm Client Issue Following Fusaka Hard Fork
#LidoProtocol #PrysmClient #FusakaHardFork #Validators #NodeOperators #Vulnerability #NetworkParticipation #LidoContributors #PrysmTeam #Blockchain #Ethereum #Staking #Crypto #LDO
According to Foresight News, Lido reported that a vulnerability in the Prysm consensus layer client led to network participation issues following the successful Fusaka hard fork yesterday. The 2025 third-quarter report on validators and node operators indicates that approximately 15% of validator nodes in the Lido protocol are operated using the Prysm client. Lido contributors worked overnight to monitor the situation, closely coordinating with the Prysm team to diagnose the issue and support affected Lido node operators in implementing recommended solutions. Most Prysm setups used by Lido have now returned to normal operation, and the Lido protocol continues to function smoothly, assuring stakers that there is no cause for concern.#LidoProtocol #PrysmClient #FusakaHardFork #Validators #NodeOperators #Vulnerability #NetworkParticipation #LidoContributors #PrysmTeam #Blockchain #Ethereum #Staking #Crypto #LDO
🚀 Ethereum Client Prysm Releases Analysis on Fusaka Mainnet Issue
#Ethereum #Prysm #FusakaMainnet #ConsensusLayer #NodeIssue #ResourceExhaustion #ValidatorRequests #Epochs #ProofRewards #ETH #Blockchain #NetworkParticipation #BeaconNodes #Proofs #SynchronizedNodes #RoundConversions #v7.1
According to ChainCatcher, the Prysm team, responsible for the Ethereum consensus layer client, has published an analysis report on the Fusaka mainnet issue. During the incident, nearly all Prysm nodes experienced resource exhaustion while processing specific proofs, resulting in an inability to respond promptly to validator requests. The fault affected epochs 411439 to 411480, with 248 blocks lost across 42 epochs, leading to a missing rate of 18.5%. Network participation dropped to a low of 75%, and validators lost approximately 382 ETH in proof rewards.
The root cause was identified as Prysm beacon nodes receiving proofs from potentially unsynchronized nodes, which referenced block roots from previous rounds. To verify these proofs, Prysm attempted to reconstruct compatible states, causing repeated processing of past round blocks and costly recalculations of round conversions. The team temporarily addressed the issue by advising users to use the --disable-last-epoch-target parameter. Future versions v7.1 and v7.1.0 will include long-term solutions.#Ethereum #Prysm #FusakaMainnet #ConsensusLayer #NodeIssue #ResourceExhaustion #ValidatorRequests #Epochs #ProofRewards #ETH #Blockchain #NetworkParticipation #BeaconNodes #Proofs #SynchronizedNodes #RoundConversions #v7.1