Following the successful implementation of the Fusaka hard fork yesterday, Lido Protocol faced temporary network participation issues due to a vulnerability in the Prysm consensus layer client, according to reports by Foresight News. The 2025 third-quarter report on validators and node operators reveals that approximately 15% of Lido nodes utilize the Prysm client. Lido contributors dedicated overnight efforts to monitor the situation, collaborating closely with the Prysm team to diagnose the problem and provide necessary support to affected Lido node operators. Most Prysm setups used by Lido have since resumed normal operation, ensuring continued functionality for stakers.