Aave's CAPO oracle misconfiguration results in a loss of 345 ETH; affected users will receive full compensation.

Foresight News reported that Aave founder Stani Kulechov stated that a configuration error in Aave's CAPO oracle led to the liquidation of wstETH E-Mode, resulting in a loss of 345 ETH. No bad debt was incurred, and all affected users will be fully compensated. Aave DAO SPs are finalizing the reimbursement plan, which will be announced soon, and 141 ETH have already been recovered through BuilderNet refunds.

Stani Kulechov further added that Risk Oracles were launched over a year ago and have transmitted more than 1,200 payloads involving around 3,000 parameters, with no incidents occurring. This contributed to the strongest growth phase in Aave's history. The Aave CAPO (related asset price oracle) system is designed to prevent well-known oracle exploit vectors, including artificially inflated exchange rates and donation attacks. It calculates the maximum cap for the exchange rate oracle based on observed real growth dynamics. CAPO is a hybrid oracle system: off-chain Chaos Oracles calculate and submit maximum exchange rate and growth rate updates, while BGD's smart contracts serve as the source of truth and enforce verification logic.