.png){kind=logo}
A sudden liquidation cascade hit the decentralized lending protocol Aave and erased nearly $27 million in positions within 24 hours. The event followed a temporary pricing mismatch involving wstETH, the liquid staking token issued by Lido. The issue caused the system to undervalue collateral and triggered automated liquidations across several accounts.
The problem arose from Aave’s internal risk oracle, CAPO. The mechanism briefly reported an incorrect exchange rate between wstETH and ETH. As a result, several positions appeared under-collateralized even though the collateral remained healthy on-chain.
Automated liquidation systems quickly activated once positions dropped below safety thresholds. Within hours, the protocol liquidated more than 10,900 wstETH and closed dozens of leveraged accounts. The event raised concerns about how technical errors in Oracle systems can affect decentralized finance markets.
The incident began when the CAPO oracle reported a lower value for wstETH compared with its real market price. Lending protocols rely on oracle feeds to determine the value of collateral deposited by borrowers.
Several positions suddenly appeared risky as the system recorded a lower price. Once collateral ratios crossed liquidation thresholds, the protocol’s liquidation engine began closing those positions automatically.
Investigations later revealed that a mismatch between an exchange-rate snapshot and its timestamp caused the pricing error. The incorrect data undervalued wstETH by nearly 2.85%. This difference forced the protocol to treat healthy positions as under-collateralized. Consequently, the system liquidated accounts even though market prices did not justify the actions.
The event affected around 34 users on the platform. Automated processes sold about 10,938 wstETH during the liquidation cascade.
Trading activity declined slightly after the liquidation episode. Daily trading volume reached around $29 million and marked an 11% drop compared with the previous day. Data from CoinGlass also showed weaker derivatives activity. Futures trading volume fell by 14% and reached about $300 million. At the same time, open interest dropped nearly 4.97% to around $190 million.
When trading volume and open interest decline together, traders often step back from the market. In this case, the shift followed the liquidation event that occurred on March 10. Despite the scale of the liquidations, the incident did not involve a security breach. The protocol did not experience a hack or a broader market crash.
Instead, the chain of events resulted from a configuration issue inside Aave’s CAPO oracle system.
Liquidation bots participated heavily during the cascade. They closed positions and collected about 499 ETH in liquidation bonuses and fees. After engineers identified the configuration error, Chaos Labs worked with the Aave protocol team to correct the issue. The protocol itself remained solvent and did not accumulate bad debt.
Aave confirmed that affected users will receive compensation. The protocol plans to use recovered funds and DAO resources to reimburse the impacted accounts. Initial refunds have already started. BuildersNet distributed an early reimbursement of 141 ETH to affected users.
Aave DAO service providers have now finalized full compensation for all 34 impacted accounts. Meanwhile, governance discussions continue around improvements to CAPO parameters across all Aave markets.
Also Read: Crypto Market Update: XRP Outperforms Gold and Silver After Israel-Iran Conflict Shock
Teams also review monitoring systems to detect rate divergences earlier. The review focuses on updating stale snapshots and improving risk-management alerts before collateral values approach liquidation thresholds.
A Lido contributor clarified that the issue did not originate from the wstETH token itself. The contributor said the liquidations resulted from incorrect pricing reported by the oracle system. The Lido protocol and the wstETH token continued to operate normally during the incident. Aave also confirmed that the event caused no damage to the core protocol.
Governance discussions now center on future safeguards. If automated synchronization requirements become mandatory, could stricter oracle standards reduce the chance of similar liquidation cascades in decentralized lending markets?
A temporary CAPO oracle pricing error caused Aave to undervalue wstETH collateral and triggered about $27 million in liquidations affecting 34 accounts. Chaos Labs and the Aave team corrected the issue quickly while the protocol remained solvent. Governance reviews now focus on stronger oracle monitoring and completing compensation for impacted users.
