In accordance with PANews, Lido stated on X that following the successful Fusaka hard fork, a vulnerability in the Prysm consensus layer client caused network-wide participation issues. Lido emphasized that its protocol continues to operate normally, with stakers advised not to be concerned. Due to the distributed and decentralized nature of its validator set, as well as the quick response from Prysm developers and node operators, the impact on Lido was less severe than on other major staking solutions. According to the 'Q3 2025 Validator and Node Operator Metrics' report, around 15% of Lido's validators are operated using Prysm by node operators. This strategy of balanced client usage helps reduce risks from relying on a single client. Most Prysm setups managed by Lido have now resumed normal operations after either using the --disable-last-epoch-targets flag or temporarily switching to other client configurations.
Lido Protocol Remains Unaffected Amid Prysm Client Outage
KuCoinFlashShare
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.