關鍵要點：Lido貢獻者發現了合唱One操作的受損的Oracle密鑰後，Lido貢獻者宣布了緊急DAO投票。

調查正在進行中。無限詳細信息，根本原因更新，投票詳細信息 - 全部在論壇帖子中：https：//t.co/vn4gq8w82g

Key Takeaways:

關鍵要點：

* An emergency DAO vote has been announced by Lido contributors to rotate a compromised oracle key being operated by Chorus One. The affected key, nosed for critical data reporting functions, was flagged after an alert showed one of the system’s quorums having its entire ETH balance rapidly depleted.

* Lido貢獻者宣布了緊急DAO投票，以旋轉合唱One操作的折衷的Oracle鑰匙。在警報顯示該系統的整個ETH平衡迅速耗儘後，受影響的密鑰（用於關鍵數據報告功能）被標記為關鍵數據報告功能。

* Subsequent investigation traced the issue to a probable private key leak, possibly from a previously used hot wallet. The incident does not indicate a broader breach of Chorus One’s infrastructure or the oracle system.

*隨後的調查將問題追溯到可能的私鑰洩漏，這可能是從先前使用的熱錢包中。該事件並不表示更廣泛的違反合唱的基礎設施或甲骨文系統。

* This prompted immediate action, including isolation of the compromised key and preparation for replacement on three Oracle contracts: AccountingOracle, ValidatorsExitBusOracle, and CSFeeOracle.

*這促使立即採取了措施，包括隔離損壞的密鑰以及在三個Oracle合同上替換的準備：AccountingOracle，valivatorSexitBusoracle和csfeeoracle。

* The affected address (0x140B.) will be substituted with a fresh, secure key (0x285f.). Insomuch as the incident is severe, there is no loss of staker funds or integrity of the staking protocol for Lido. The 5-of-9 quorum model for the system has redundancy and robustness, inherently avoiding single points of failure.

*受影響的地址（0x140b。）將用新的安全鍵（0x285f。）代替。由於這一事件嚴重，因此沒有損失Staker的資金或LIDO樁規程的完整性。該系統的9個法定人數中的5個模型具有冗餘性和魯棒性，固有地避免了單點故障。

Labs emphasizes Lido’s multi-layered incident response and security strategy throughout its reply. The rapid collaboration of the team with Chorus One and a full audit of all other oracles prevented wider disruption within the system.

實驗室在整個答復過程中強調了Lido的多層事件響應和安全策略。團隊與合唱One的迅速合作以及對所有其他牙齒的全面審核阻止了系統內部的更廣泛破壞。

All eight remaining oracle operators were verified as being secure, with no irregularities within the reporting infrastructure or software layers.

剩下的八個甲骨文操作員均被證實是安全的，報告基礎架構或軟件層中沒有不規則性。

On May 10th, Lido’s Oracle system experienced minor reporting delays due to unrelated issues affecting four other Oracle participants.

5月10日，Lido的Oracle系統經歷了較小的報告延遲，這是由於影響其他四名Oracle參與者的無關問題。

Two of those were linked to a post-Spectra Prism bug, which is expected to be resolved in a future update. Despite this coincidence, all delayed reports were eventually delivered, and quorum functionality has since returned to normal.

其中兩個與後譜系棱鏡錯誤有關，預計將在以後的更新中解決。儘管巧合，但所有延遲報告最終都得到了交付，並且法定人數功能恢復了正常。

During the same day, Lido contributors and Chorus One’s security teams conducted detailed reviews of their systems to pinpoint the breach’s vector.

在同一天，Lido的貢獻者和合唱團的安全團隊對其係統進行了詳細的評論，以查明違規矢量。

No indication has been seen of a deeper exploitation or software-level breach. The problem seems limited to the key itself, potentially from previous use and handling, and not a current intrusion.

尚未看到更深入的剝削或軟件級別的違規行為。這個問題似乎僅限於關鍵本身，這可能是由於以前的使用和處理而不是當前的入侵。

Lido Promises Detailed Post-Mortem Report

利多承諾詳細驗屍報告

The emergency DAO voting for rotating the hacked oracle key is scheduled for two phases: a 72-hour main voting period and a subsequent 48-hour objection period.

緊急DAO投票旋轉入侵的Oracle密鑰定於兩個階段：一個72小時的主要投票期和隨後的48小時異議期。

This change will update all affected contracts so they incorporate the fresh, un-hacked key. The hacked address will be excluded from quorum activities until voting is over.

此更改將更新所有受影響的合同，因此它們包含了新鮮的，未黑的鑰匙。入侵地址將被排除在法定活動之外，直到投票結束。

As a matter of transparency and future reliability, Lido has pledged to release a thorough post-mortem once the ongoing investigation is complete.

作為透明度和未來的可靠性，Lido已承諾在進行的調查完成後釋放徹底的驗屍。

The report will include, among other things, the sequence of events, root cause, and any protocol improvements implemented in consequence.

該報告將包括事件的順序，根本原因和隨後實施的任何協議改進。