MIP-X43 cbETH Oracle Incident Summary

I hope Moonwell stand over this bad debt and repay users since this is really bad from a trusted MM on BASE supplying cbETH which should be a trusted asset. I have lost all of my ETH holdings due to this error :frowning:

Will be great to get a timeline on how soon the oracle can be fixed as there are users who have supplied to cbeth and now their credit health is suffering. When will the proposal for oracle fix be up since it takes 5 days to pass?

1 Like

I reviewed the spreadsheet distributed regarding liquidations. I am a bit confused for instance for myself only my borrowings appear my collateral has not been taken into account. Sounds a bit weard to me

My collateral was about 4x my borrowings prior to the oracle price bug, now it’s all gone cbEth, rEth and wstEth. cbEth was the majority so once that was liquidated the rest got liquidated too. It doesn’t seem like it would be too difficult for Moonwell to do the analysis that shows liquidated assets on those wallets (listed on the spreadsheet) at the time of oracle price bug and then refund those assets or am I missing something?

Attached below is a spreadsheet with data on users who had other collateral (in addition to cbETH) liquidated during or shortly after the oracle update window. These users supplied cbETH as collateral alongside additional assets and were borrowing various tokens. When the oracle update occurred, their entire positions became eligible for liquidation due to the artificially low collateral valuation.

To provide more context and transparency, we’ve compiled liquidation transactions involving cbETH collateral between February 14–18, 2026. From that subset of affected suppliers, we’ve gathered all additional liquidation events for those same addresses during the same timeframe (including non-cbETH related liquidations that may have cascaded).

The attached spreadsheet summarizes:

  • Liquidations per user/address
  • Amounts of each token seized and repaid
  • USD values at the time of liquidation (based on recorded oracle prices)
  • “Actual” recalculated fields using a corrected cbETH price of $2,200 per token at the time of each liquidation event (the original data uses the oracle price of $1.12)

We propose that each user should receive the full amount of cbETH that was liquidated minus the value of debt repaid when seizing that cbETH collateral, plus the value difference between any other seized collateral assets and debt repaid (this should account for the 10% liquidation penalty on other types of collateral).

The spreadsheet containing the full liquidation data of affected addresses can be viewed here

2 Likes

After the cbETH incident, collateral in my two wallets (including rETH, weETH, and wstETH) was fully liquidated.

Is there any possibility of refund for affected users?

Wallet 1:
Supplied: 4.44 rETH / 4.56 cbETH / 4.70 weETH / 4.17 wstETH
Borrowed: 14 ETH

Wallet 2:
Supplied: 7.11 rETH / 7.31 cbETH / 7.52 weETH / 6.67 wstETH
Borrowed: 23 ETH

1 Like

Where do I report an address that was liquidated on Feb-15 (3 min after the cbETH incident began) but that is not listed in the spreadsheet above? My position was only underwater due to the cbETH mispricing, and should not have been liquidated at all. cbETH was a small portion of the total assets supplied but with it going to zero, it put my portfolio into liquidation, and non-cbETH assets were liquidated as a result.

I was expecting to find my address among the 181 addresses listed above, but it is not included.

Please provide your address and we will check if it’s in our records. We want to ensure all affected users are accounted for.

I wanted to report my address that wasn’t included in the spreadsheet either. Can I provide it here or is there a way to private message you?

feel free to DM @cnobles on telegram

Please refer to this website which contains the most up-to-date version of affected addresses (those liquidated as a result of the cbETH oracle update to $1.12)

1 Like

The address is: 0x1a4cBE35e366A1458E4893405C6517Fb160eDcfF

Here are the two liquidation events with the same time stamp:
https://basescan.org/tx/0x959506491470cbc751194c591b151086a812f56515a80527fc42234024851e92

https://basescan.org/tx/0x2147b0975fb574dc1ac933116a3e1d9e1888be8b2a2deeeb76453336ca56a9df

My address is listed on the cbETH dashboard, thanks. I didn’t see it on the initial spreadsheet that was shared.

This ^^. Seems everyone is focusing only on those who got liquidated. What about those of us who supplied cbETH, didn’t get liquidated, but now have no way to withdraw it (because the pool is insolvent)?

1 Like

Are you also compiling addresses who are owed cbETH from the pool but didn’t get liquidated? I’m in that camp and don’t see my address in any of the spreadsheet tabs. Really hoping I’ll be made whole – it’s not a trivial amount. Thanks.

I think the 460cbeth that got taken by the abuser of the error will be bought back and restored as liquidity in the pool so people who are still positionned in the pool will be able to withdraw their cbeth. This amount of cbeth is accounted for in the calculations but just not compiled into your adress since you haven’t been liquidated, once this is restored you will be able to withdraw your share