Lido Responds to Aave Liquidation Incident: Oracle Price Error, Not Related to Lido Protocol

iconTechFlow
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
On March 11, 2026, Lido clarified that the Aave liquidation incident resulted from a CAPO oracle price error, not a flaw in the Lido protocol. The error triggered the incorrect liquidation of wstETH E-Mode positions, resulting in the loss of approximately 345 ETH. No bad debt was generated, and all affected users will be reimbursed. Lido emphasized that user funds in Lido Earn remain secure. With ETH prices under close watch, altcoins may also experience ripple effects from such oracle-related risks.

According to Lido (@LidoFinance), on March 11, an incorrect configuration of Aave’s CAPO oracle led to the erroneous liquidation of wstETH E-Mode positions, resulting in a loss of approximately 345 ETH. No bad debts have been incurred, and all affected users will be fully reimbursed. Lido emphasized that this incident is unrelated to the underlying assets of wstETH or the Lido protocol itself, and user funds in Lido Earn products remain secure.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.