On May 11th, according to the official announcement from Lido on the X platform (formerly Twitter), Lido DAO launched an urgent proposal to replace the oracle node operated by Chorus One, after suspicions arose about a potential private key leak related to this oracle node.
However, Lido affirmed that staking users are not affected, and the entire protocol is still operating stably and safely. Lido's oracle system is designed with a 9-of-5 multisignature mechanism, which means that an issue with one oracle node does not threaten the integrity and operation of the system.
After conducting an internal investigation, Lido stated:
The oracle system is still operating normally, with no abnormalities detected in software or data.
The eight remaining oracle nodes have not been compromised after thorough verification.
There are no signs indicating a widespread attack on Chorus One.
The quick proposal to replace the oracle node is seen as a proactive measure to protect the reliability of the decentralized oracle system that Lido DAO is operating. This is also evidence of the safe governance and rapid risk response approach of the Lido DAO community – one of the largest decentralized staking protocols in the Ethereum market today.
