Following yesterday’s successful Fusaka hardfork, a Prysm Consensus Layer client bug caused network-wide participation issues. The Lido protocol continues to operate normally and there is no cause for concern for stakers. Lido was less affected by this incident than other large notable staking solutions, and the network on average, owing to the distributed and decentralized nature of the validator set underlying the protocol, as well as speedy response by the Prysm client team and Node Operators.

Lido contributors monitored the incident overnight, coordinated closely with the Prysm team on diagnosis, and supported affected Lido Node Operators in applying the recommended workarounds. Most Lido-run Prysm setups have now recovered after using the --disable-last-epoch-targets flag or temporarily switching to alternative client configurations.

A huge thanks is owed to the Prysm team for the quick diagnosis and fix, as well as to Node Operators for rapid remediation. Client diversity is a core enabler of Ethereum’s resiliency, and in events like today it is easy to see the value that it adds to the network and protocols that embrace it.