关键要点：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.

该报告将包括事件的顺序，根本原因和随后实施的任何协议改进。