DeFi User Loses 14 ETH Due to Faulty Oracle Update with No Accountability
A DeFi user, referred to as "jameis," lost 14 ETH (approximately $33,000) due to a faulty price oracle update involving Morpho, Pyth Network, and Re7 Labs. The liquidation occurred when the price feed for cbETH froze for nearly an hour, despite ongoing updates for ETH, leading to a distorted price ratio that triggered automatic liquidation.
Key Points
- Morpho claims no responsibility, stating it is oracle-agnostic and vault curators choose their own oracles.
- Pyth asserts its prices were accurate, suggesting Re7 or the user should have managed price update scheduling.
- Re7 acknowledges a timing mismatch but attributes it to the nature of push-based oracles, promising improvements for the future.
- No party has offered compensation or accountability for the incident.
- The circumstances reveal an architectural failure rather than an exploit, with:
- Pyth's model lacking automatic synchronization for price updates.
- Re7 not implementing an independent scheduler for price updates.
- Morpho not enforcing reliability standards for oracle updates.
- The incident highlights a significant issue in DeFi regarding decentralized responsibility without accountability mechanisms.
- Calls for safeguards, such as timestamp verification and improved scheduling guarantees, have been made to prevent similar occurrences.
The incident exemplifies challenges in DeFi compared to traditional finance, where users have legal recourse for erroneous liquidations. Without measures like insurance or stricter standards, users remain vulnerable to losses caused by system failures.








