Lido DAO launched an emergency DAO vote following the discovery of a compromised oracle key within Chorus One’s managed infrastructure. This incident underlines Lido’s commitment to robust governance and security models, emphasizing the importance of decentralized responses in ensuring user trust and protocol integrity. 🔎 Upon detecting the compromise, Lido swiftly initiated action, ensuring continued protocol functionality and minimizing potential repercussions. An emergency DAO vote was triggered to rotate the compromised key, with eight out of nine oracle nodes maintaining operational capacity despite this disruption. Lido DAO contributors are now voting to initiate a key rotation in the HashConsensus contracts for the Accounting Oracle. 🤝