Oracle Error Triggers $27 Million in Mistaken Liquidations
A configuration error in Aave's internal price oracle, CAPO, triggered approximately $27 million in automated liquidations after it undervalued Lido's wrapped staked Ether (wstETH). The system briefly reported a price for wstETH that was 2.85% below its actual market rate. This discrepancy caused the collateral of 34 user accounts to appear undercollateralized, initiating a cascade of forced liquidations totaling 10,938 wstETH.
The technical fault stemmed from a mismatch between two key parameters in the oracle's formula: the snapshot ratio and the snapshot timestamp. An on-chain constraint limited how quickly the exchange rate ratio could be updated, while the timestamp adjusted to a more recent value. This misalignment forced the oracle to calculate a lower maximum exchange rate, creating the temporary price error. The incident was a technical failure within the protocol's risk management system, not a security breach or hack.
AAVE Trading Cools as Protocol Commits to User Compensation
In the wake of the liquidations, trading activity for Aave's native token showed signs of investor caution. Daily trading volume declined by 11% to approximately $29 million. The derivatives market saw a more significant retreat, with futures trading volume falling 14% to $300 million and open interest contracting by 4.97% to $190 million. During the event, third-party liquidators captured about 499 ETH in bonuses and profits.
The Aave team responded by temporarily reducing borrowing limits on the affected asset, correcting the oracle configuration, and restoring the accurate exchange rate. The protocol itself remained solvent and did not accumulate any bad debt. Aave DAO service providers have confirmed that all 34 impacted users will be fully compensated, using 141 ETH recovered through BuilderNet, 13 ETH in liquidation fees, and funds from the DAO treasury to cover any remaining shortfall.
Incident Highlights Systemic Oracle Risk in DeFi
This event underscores the critical dependence of decentralized lending protocols on the accuracy of their price oracles. Even without a market crash or external attack, internal configuration issues can lead to significant, unintended financial losses for users. While the Lido protocol and the wstETH token itself operated correctly throughout the incident, the error in how Aave's system interpreted its value was sufficient to trigger the cascade.
In response, Aave's governance is actively discussing improvements to the CAPO oracle parameters and its monitoring systems. The focus is on implementing stricter safeguards to detect rate divergences earlier and prevent stale data from influencing collateral valuations. The incident serves as a crucial case study for the broader DeFi ecosystem on the importance of robust oracle security to maintain user trust.
