M1 USDC
Risk reportEthereum0xab59…616c
Risk
Depositing into M1 USDC means underwriting risks you usually can't see: how much you could lose, whether you'd get out in time, and what would cover it.
Collateral and oracle exposure
Each token you're exposed to, and the market it backs. If that market breaks, this is how much the vault loses, in dollars and as a share of the vault. Open a row for the price feed, stress curve, and supply-cap detail. Below, the oracles those prices depend on and what is at stake if one is compromised.
Driven by mM1-USD −30% 17% · cbBTC −30% <1% · −100% 91% modeled all-to-zero bad-debt ceiling
mM1-USDHybrid91%of vault · bad debt · $7.68mOracle exposure 9%100%of vault · $8.46m91%of vault · $7.68m9%separate path
What it's made of
Mixes market and exchange-rate inputs — partial depeg insulation, partial market exposure.
- → USDC86% LLTV0xb558…0b0a
If it breaks
−30% default
cbBTCMarketChainlink<0.1%of vault · bad debt · $755.85Oracle exposure <0.1%<0.1%of vault · $842.12<0.1%of vault · $755.85<0.1%separate path
What it's made of
cbBTC is priced via BTC / USD — market-rate feed (Chainlink).
- → USDC86% LLTV0xa6d6…182aChainlink
If it breaks
−30% defaultOracle dependencies
1 feed · 1 control pointUp to9%of vault drainable if these feeds are mispriced · $775,222.89
Each price traces to a feed and the on-chain admin that can move it. Compromise either to misprice the collateral and borrow against it. Per-row amounts overlap and are not summed.
- Chainlink·a 4/9 Safe multisigprices cbBTC0x21f7…73ca<1% of vault · $86.27drainable if it is compromised
- Unidentified feeds· vendor and on-chain control not resolvedprices mM1-USD9% of vault · $775,136.62mispriceable if these feeds lie
Loss scenarios
Each row is a distinct failure, and every loss is a share of your deposit — the same percentage whatever you deposited. Loss is that share at a −30% collateral crash, the standard stress; Worst case is the ceiling if everything goes wrong, a conditional loss if it happens rather than a likelihood. Open a row for the loss at every crash depth, the dollar amounts, conditions, and the math.
| Full-deposit & protocol-level(2) | ||||
| 100% | Full deposit | Instant | ||
| 17% | up to 91% | Instant | ||
| Price-driven collateral stress(1) | ||||
| 17% | up to 91% | Instant | ||
| Oracle & liquidation failures(3) | ||||
| 17% | up to 91% | Instant | ||
| 17% | up to 91% | Instant | ||
| — | up to 9% | Instant | ||
| Vault role & allocator(3) | ||||
| — | Full deposit | 7 days | ||
| — | Full deposit | Instant | ||
| — | up to 50% | 7 days | ||
Trust and control
The people and processes that can change this protocol under you.
Vault operators
The roles that can actually move your deposit — the real principal-loss path.
Role timelock 7 days to exit before owner/curator actions land
Curator change queued
The timelock is your window to exit before each one takes effect.
- set send assets gate— applies now; no time to exit first
Sentinels3 · 1 multisig · 1 contract · 1 EOASafety role · veto only
Safety role, not an attack role: can revoke ANY pending timelocked curator change, instantly cut caps, and pull funds from adapters back to idle. Strictly risk-reducing — a captured sentinel cannot introduce new risk.
- 1-of-7 multisig0x0000…9da8
- single key (EOA)0x53e4…a4b5
- contract0x5c48…92fc
Allocators3 · 1 multisig · 1 contract · 1 EOAReaches deposit · instant
Moves funds between markets the curator has ALREADY approved — instantly, with NO timelock and no exit window. Cannot reach a brand-new market, but can concentrate you into an approved-but-stressed market or order withdrawals so you hit weak liquidity first.
- 1-of-7 multisig0x0000…9da8
- contract0xaad8…35e7
- single key (EOA)0xfeed…3c9a
Audits
- Certora· Dec 15, 2025report
- Blackthorn· Dec 4, 2025report
- Spearbit· Dec 4, 2025report
- Blackthorn· Sep 15, 2025report
Governance & control
Protocol-wide governance: bounded context, not the path to your deposit.
Dependencies that can affect your deposit
8 things this pool relies on but doesn't control. Select one for its story.
Every Morpho Blue market chooses an immutable oracle contract at creation; implementations can be Chainlink-like, exchange-rate, fixed-price, or custom. Failure modes: attacker-favourable price feed (covered in market-oracle-compromise) or price() revert / staleness blocking liquidations (covered in oracle-liveness-or-malfunction).
No quantified loss scenario references this dependency directly.