coin-img-ETHETH-1.15%coin-img-BTCBTC-1.22%coin-img-SOLSOL-3.93%coin-img-XRPXRP-4.59%coin-img-USDCUSDC-0.01%coin-img-UCNUCN+0.32%coin-img-HYPEHYPE-5.67%coin-img-DOGEDOGE-2.45%coin-img-ETHETH-1.15%coin-img-BTCBTC-1.22%coin-img-SOLSOL-3.93%coin-img-XRPXRP-4.59%coin-img-USDCUSDC-0.01%coin-img-UCNUCN+0.32%coin-img-HYPEHYPE-5.67%coin-img-DOGEDOGE-2.45%coin-img-ETHETH-1.15%coin-img-BTCBTC-1.22%coin-img-SOLSOL-3.93%coin-img-XRPXRP-4.59%coin-img-USDCUSDC-0.01%coin-img-UCNUCN+0.32%coin-img-HYPEHYPE-5.67%coin-img-DOGEDOGE-2.45%coin-img-ETHETH-1.15%coin-img-BTCBTC-1.22%coin-img-SOLSOL-3.93%coin-img-XRPXRP-4.59%coin-img-USDCUSDC-0.01%coin-img-UCNUCN+0.32%coin-img-HYPEHYPE-5.67%coin-img-DOGEDOGE-2.45%

Lido Reports Full Recovery After Prysm Client Bug Following Fusaka Hard Fork

Lido announced on Dec. 4 that a bug affecting the Prysm consensus layer client has been resolved following Ethereum's Fusaka hard fork, with no impact on stakers. The issue caused network participation problems, but Lido's decentralized validator distribution minimized exposure. Most Prysm setups operated by Lido have been restored, while some nodes temporarily switched to alternative client configurations during the fix.
ETH
ETH-1.13%
LDO
LDO-3.08%
Disclaimer: The content above is only the author's opinion and does not represent BingX’s stance. It shall not be construed as investment advice from BingX. For details, refer to the Terms and Conditions.