Lido Initiates Emergency Vote After Oracle Compromise

Lido Finance has initiated an emergency DAO vote after detecting a compromised oracle key managed by Chorus One.

The incident underscores the resilience of Lido’s governance and oracle systems, ensuring stable protocol operations.

Lido Responds to Oracle Key Compromise

Lido Finance launched a DAO vote after an oracle key compromise, maintaining system integrity. The compromised key was linked to the Chorus One infrastructure , a prominent blockchain operator. This prompt response highlights Lido’s governance processes.

The emergency DAO vote was called swiftly, adhering to established governance protocols. Lido DAO contributors confirmed that the protocol remains unaffected, with only the compromised key impacting ETH within the oracle module.

“Lido DAO contributors are initiating an emergency DAO vote to rotate this key in the HashConsensus contracts for the Accounting Oracle.” — Lido Forum

User Funds Protected During Incident

Immediate actions by Lido and its DAO ensured that no user funds were affected, maintaining normalcy across the protocol. Stakeholders and stakers experienced no disruption or loss, demonstrating effective incident management.

Financially, the Lido protocol remains robust, with no impact on its Total Value Locked (TVL). The incident was contained, emphasizing the protocol’s risk management and security measures.

Lido’s Oracle System Resilience

Historically, Lido’s multisig structure has minimized similar risks, setting a precedent in oracle security management. The quick action taken highlights the effectiveness of redundancy within the oracle system.

Given historical trends, the incident’s isolated nature suggests continued confidence in Lido’s governance. Analysts note that proactive measures solidify Lido’s position in maintaining protocol security.