Lido DAO launches emergency proposal to replace oracle node suspected of leaking private keys

Odaily News Lido posted on the X platform that Lido DAO initiated an emergency proposal to replace the single Lido oracle node it is responsible for because the private key of Chorus One's oracle was suspected to be leaked. It is reported that the pledged users are not affected and the protocol is still safe and running normally. Lido's oracle system adopts a 9-choose-5 multi-signature mechanism. A single oracle failure will not threaten the system, and the remaining nodes are not affected:
The oracle system is operating normally, and no software or data anomalies were found. The remaining 8 oracle nodes were not compromised after inspection. No signs of a wider attack on Chorus One as a whole were found.