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

Lido officially stated that after the successful completion of the Ethereum Fusaka hard fork, a vulnerability was found in the Prysm consensus layer client, leading to issues with network participation. The Lido protocol is operating normally, and stakers need not worry.

Due to the distributed and decentralized nature of the underlying validator node set, Lido is minimally affected by this event, and the quick response from the Prysm client team and node operators has helped alleviate the issue. The Lido team worked closely with the Prysm team, monitoring the event's progress overnight and assisting affected node operators in implementing recommended temporary solutions. Currently, most of the Prysm setups running on Lido have been restored, and some nodes have temporarily switched to other client configurations to complete the fix.