Key Insights Aave liquidating $27 million worth of user positions on March 10, 2026, made the top crypto news. But these weren’t risky positions. They were healthyKey Insights Aave liquidating $27 million worth of user positions on March 10, 2026, made the top crypto news. But these weren’t risky positions. They were healthy

Crypto News: Aave Liquidates $27M After Oracle Misprice, What Went Wrong?

2026/03/12 05:15
4 min read
For feedback or concerns regarding this content, please contact us at crypto.news@mexc.com
aave crypto news

Key Insights

  • Crypto news for today highlights an Aave oracle error that undervalued wstETH by 2.85%, liquidating $27 million wrongly.
  • CAPO timestamp mismatch between off-chain and on-chain systems triggered incorrect liquidations.
  • All affected users are receiving a 345 ETH refund from liquidator profits and the Aave treasury, per crypto news.

Aave liquidating $27 million worth of user positions on March 10, 2026, made the top crypto news. But these weren’t risky positions. They were healthy. The problem was a broken oracle.

An oracle is a price feed that tells Aave what assets are worth. It showed the wrong price for wstETH, which is wrapped staked Ethereum.

When the oracle shows wrong prices, the system makes wrong decisions. In this case, it thought safe positions were dangerous. It liquidated them.

Users with perfectly fine Health Factors got their collateral seized and sold. This affected 34 accounts in total.

Crypto News: Aave Oracle Error Liquidates $27M

As per the latest crypto news, the oracle undervalued wstETH by about 2.85%. It showed a ratio of 1.1939 ETH per wstETH. The real market price was 1.228 to 1.229. That gap seems small. But in leveraged lending, small differences matter.

Aave uses Health Factor to measure safety. A value above 1.0 means safe, and below 1.0 means liquidatable. The wrong oracle made the system calculate incorrectly. Positions actually above 1.0 looked below 1.0. Liquidation bots seized collateral.

A total of 10,938 wstETH got liquidated. About $27 million at market prices.

The crypto news showed that the first detection came at 12:50 GMT on March 10, when the LTV protocol was noticed and paused operations.

Crypto News: CAPO Max Price Was Changed | Source: XCrypto News: CAPO Max Price Was Changed | Source: X

Liquidator bots made 499 ETH in profits. Aave clawed back 141 ETH through BuilderNet refunds, whereas the protocol earned 13 ETH in fees.

An important part is that Aave took no bad debt. Protocol stayed solvent, meaning it did not lose money or end up owing funds it could not pay back.

CAPO Timestamp Mismatch Explained

The broken piece was CAPO, which stands for Correlated Asset Price Oracle. As per the crypto news, Aave uses this for assets like wstETH that correlate with ETH.

The system caps how fast the wstETH to stETH ratio can grow. The maximum is 3% every three days. This prevents manipulation.

CAPO relies on two things working together. Off-chain logic from Chaos Labs recommends what ratio to use. On-chain contracts enforce growth limits. The error happened when these disagreed.

Off-chain targeted ratio of 1.2282 based on market data. On-chain rules said the ratio could only reach 1.1919 due to the 3% limit.

The timestamp got set to reference seven days ago. The system thought it was catching up to old data.

This created a fake cap below the real market rate, which is not a design flaw. The crypto news showed that this is a configuration alignment failure under rate limits.

Crypto Users Getting Refunded, but Risk Remains for DeFi

Aave founder Stani Kulechov confirmed all affected users would get full refunds. Total reimbursement is 345 ETH, worth about $700,000. This represents only 0.00274% of total protocol size. Money comes from recovered liquidator profits, protocol fees, and treasury.

The fix happened the same day. The crypto developers manually reverted the bad Oracle update. They temporarily set borrow caps to 1 as a safety measure. This prevented more liquidations while verifying everything worked. Caps are now being restored to normal levels.

The crypto news bit from today highlighted mixed responses. Many praised the quick response and transparent postmortem from Chaos Labs.

Full compensation matters. But some worry about DeFi adoption. If top protocols like Aave can have oracle errors, what about smaller ones?

Also, this crypto news lesson goes beyond Aave. Every DeFi protocol relies on oracles. Those oracles can break. Users should understand that this risk exists even with blue-chip DeFi platforms.

The post Crypto News: Aave Liquidates $27M After Oracle Misprice, What Went Wrong? appeared first on The Coin Republic.

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact crypto.news@mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.