The Consequence Library · How records are made and graded
An oracle configuration deployed by governance proposal MIP-X43 valued Coinbase Wrapped ETH at approximately $1.12 instead of roughly $2,200, triggering liquidations that left the Moonwell protocol with approximately $1.78 million in bad debt.
Evidence caveat. The AI co-authorship attribution comes from a named security auditor reading public commit records, and is reported rather than confirmed by the project. The mispricing, the liquidations and the loss are on-chain facts.
What happened
On 15 February 2026 MIP-X43 executed, enabling oracle wrapper contracts across core markets. One configuration contained a critical error: instead of deriving the USD price by multiplying the cbETH/ETH feed by the ETH/USD price, the oracle used only the raw cbETH/ETH exchange rate, a roughly two-thousandfold mispricing. Liquidation bots acted within minutes, and the protocol incurred approximately $1.78 million in bad debt. A blockchain security auditor reported that portions of the oracle code were co-authored by an AI model, per commit records in the project's repository. A subsequent governance proposal was submitted to revert the pricing model and consider user remediation.
Where control failed
The configuration passed through the project's review and governance process before deployment. Once deployed, automated market activity reacted to the incorrect price more quickly than the governance process could reverse the change.
The authority question
The proposal received formal approval. The incident therefore distinguishes approval of a change from independent verification of the change's technical effect before execution.
What could be proven afterward
Excellent, and unusually so. The mispricing, the liquidations and the losses are all on-chain and independently reconstructable by anyone, and the commit history is public. This is the rare record where the evidence layer worked: the failure was in control before the action, not in proving it afterward.
Control state, before and after
Before the consequence
Human review and on-chain governance vote as the controls on oracle configuration. Post-execution reversal gated behind a multi-day timelock.
After the consequence
Governance proposal submitted to revert the pricing model and consider user remediation.
Sources
- Primary: Moonwell Governance Forum, "MIP-X43 cbETH Oracle Incident Summary" · https://forum.moonwell.fi/t/mip-x43-cbeth-oracle-incident-summary/2068
- Secondary: The Block, "DeFi lending protocol Moonwell hit with $1.8 million bad debt after oracle misconfiguration" · https://www.theblock.co/post/390302/defi-lending-protocol-moonwell-hit-with-1-8-million-bad-debt-after-oracle-misconfiguration
- Secondary: Crypto Economy, "Moonwell Suffers $1.8M Loss After Oracle Glitch, With Claude Opus 4.6 Cited in Faulty Output" · https://crypto-economy.com/moonwell-oracle-glitch-ai-linked-1-8m-loss/
Record history
Published 16 August 2026. Load-bearing facts re-verified against the cited sources on 16 August 2026. Corrections and material changes are appended here with their dates. To report an error in this record, write to hello@regulayer.com with the record slug and the source you believe is authoritative.
This record describes what sources establish about a consequence and the control state around it. It separates confirmed fact from source-stated cause and from architectural analysis, and it makes no claim that any control or product would have prevented the outcome. Gap codes identify a failure class, not a remedy.