Lido: Issue caused by Prysm consensus layer client has been fixed, no impact on stakers

ChainCatcher News, Lido officially stated 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 was minimally affected by this incident, and the quick response from both the Prysm client team and node operators helped mitigate the issue. The Lido team worked closely with the Prysm team, monitored the event overnight, and assisted affected node operators in implementing the recommended temporary solutions. Currently, most Prysm setups running Lido have been restored, and some nodes have temporarily switched to other client configurations to complete the fix.