Lido DAO has initiated an emergency proposal to replace a suspected private key-leaking oracle node. The protocol operation remains unaffected.

BlockBeats News, May 11th, Lido announced on social media that the Lido DAO has initiated an emergency proposal to replace the single Lido oracle node previously managed by Chorus One, as the oracle's private key is suspected to have been compromised.

Stakers are not affected, and the protocol continues to operate safely and normally. Lido's oracle system operates on a 9 out of 5 multi-signature mechanism, where the failure of a single oracle does not pose a threat to the system, and the other nodes remain unaffected.

· The oracle system is functioning normally, and no software or data anomalies have been detected

· The other 8 oracle nodes have been verified and were not breached

· There are no signs of a broader attack on Chorus One as a whole