PANews reported on December 4th that Lido stated on its X platform that a vulnerability in the Prysm consensus layer client caused a network-wide participation issue following the successful Fusaka hard fork. The Lido protocol continues to operate normally, and stakers need not worry. Given the distributed and decentralized nature of the underlying validator set, and the rapid response of the Prysm client team and node operators, the impact of this event on Lido is less than on other large staking solutions, and the overall average impact on the network is relatively low. As stated in the "Q3 2025 Validator & Node Operator Metrics," node operators use Prysm to run approximately 15% of their validators in Lido. This strategy of promoting balanced client usage helps the Lido protocol reduce the risk posed by a single client. Most Prysm settings running on Lido have now returned to normal after using the `--disable-last-epoch-targets` flag or temporarily switching to other client configurations.PANews reported on December 4th that Lido stated on its X platform that a vulnerability in the Prysm consensus layer client caused a network-wide participation issue following the successful Fusaka hard fork. The Lido protocol continues to operate normally, and stakers need not worry. Given the distributed and decentralized nature of the underlying validator set, and the rapid response of the Prysm client team and node operators, the impact of this event on Lido is less than on other large staking solutions, and the overall average impact on the network is relatively low. As stated in the "Q3 2025 Validator & Node Operator Metrics," node operators use Prysm to run approximately 15% of their validators in Lido. This strategy of promoting balanced client usage helps the Lido protocol reduce the risk posed by a single client. Most Prysm settings running on Lido have now returned to normal after using the `--disable-last-epoch-targets` flag or temporarily switching to other client configurations.