Lido DAO launched an emergency proposal to replace the oracle node suspected of leaking the private key, and the operation of the protocol was not affected

Lido said on social platforms that the Lido DAO launched 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.
The staking user is not affected, and the protocol is still safe and running normally. Lido's oracle system adopts a multi-signature mechanism of 9 out of 5. A single oracle failure will not threaten the system, and the rest of the nodes are not affected.
The oracle system is operating normally, and no software or data abnormalities have been found
The remaining 8 oracle nodes were not breached after inspection
No sign of a wider attack on Chorus One as a whole