Lido: The Lido protocol continues to operate normally and is minimally affected by the Prysm client outage incident.

According to news from CoinWorld on December 4, Lido posted on X that after the successful Fusaka hard fork, a bug in the Prysm consensus layer client caused network-wide participation issues. 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 quick response from the Prysm client team and node operators, the impact on Lido from this incident was smaller than on other major staking solutions, and the overall average impact on the network was relatively low. As stated in the “Q3 2025 Validator and Node Operator Metrics” report, node operators use Prysm to run about 15% of the validators in Lido. This strategy of promoting balanced client usage helps the Lido protocol reduce the risk from relying on a single client. Most Prysm setups run by Lido have now returned to normal after using the --disable-last-epoch-targets flag or temporarily switching to another client configuration.