Lido: Issue Caused by Prysm Consensus Layer Client Resolved, Stakers Unaffected

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.