Lido: The issue caused by the Prysm consensus layer client has been fixed, with no impact on stakers.

BlockBeats news, on December 4, Lido officially announced that after the successful completion of the Ethereum Fusaka hard fork, a vulnerability appeared in the Prysm consensus layer client, causing issues with network participation. The Lido protocol is operating normally, and stakers do not need to worry. Due to the distributed and decentralized nature of the protocol’s underlying validator set, Lido is less affected by this incident, and the quick response from the Prysm client team and node operators has helped mitigate the issue. The Lido team worked closely with the Prysm team, monitored the incident overnight, and assisted affected node operators in implementing the recommended temporary solutions. Currently, most Prysm setups running Lido have been restored, and some nodes that temporarily switched to other client configurations have completed repairs.