PANews reported on May 11 that Lido stated on the X platform that Lido DAO initiated an emergency proposal to replace the single Lido oracle node it was responsible for due to the suspected leakage of Chorus One's oracle private key. Staking users are not affected, and the protocol remains safe and operating normally. Lido's oracle system uses a 9-choose-5 multi-signature mechanism. A single oracle failure will not threaten the system, and the remaining nodes are not affected. At present, the oracle system is operating normally, and no software or data anomalies have been found; the remaining 8 oracle nodes have not been breached after inspection; and there are no signs of a wider attack on Chorus One as a whole.