tecrübe-deneyim

BlockBeats News, December 4th, the official Lido announcement stated that after the Ethereum Fusaka hard fork was successfully completed, a vulnerability was discovered in the Prysm consensus layer client, leading to a network participation issue. The Lido protocol is running normally, and stakers need not worry. Due to the protocol's underlying validator node set being distributed and decentralized, Lido was minimally affected by this event, and the prompt response from the Prysm client team and node operators helped mitigate the issue.The Lido team closely collaborated with the Prysm team, monitoring the event overnight and assisting affected node operators in implementing the recommended temporary solutions. Currently, most of the Prysm setups running on Lido have been restored, with some nodes temporarily switched to other client configurations to complete the repairs.

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.