[Lido: The Lido protocol continues to operate normally, minimally affected by the Prysm client malfunction incident] Lido posted on the X platform stating that after the successful completion of the Fusaka hard fork, a vulnerability in the Prysm consensus layer client caused network participation issues. The Lido protocol continues to operate normally, and stakers need not worry. Due to the distributed and decentralized nature of the underlying validator set, as well as the swift response from the Prysm client team and node operators, this incident has had less impact on Lido compared to other large staking solutions, and the overall average impact on the network has been relatively low. As noted in the "Validator and Node Operator Metrics for Q3 2025," approximately 15% of validators in Lido are operated by node operators using Prysm. This strategy of promoting balanced client usage helps the Lido protocol mitigate risks associated with reliance on a single client. Most Prysm setups operated by Lido have now returned to normal after using the --disable-last-epoch-targets flag or temporarily switching to other client configurations.