StableEarn
Risk reportStable0xb7df…5c08
Risk
Depositing into StableEarn 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 sthUSD −30% 13% · thBILL −30% <1% · −100% 69% modeled all-to-zero bad-debt ceiling
sthUSDMarketRedStone69%of vault · bad debt · $17.21mOracle exposure 7%76%of vault · $19.03m69%of vault · $17.21m7%separate path
sthUSDMarketRedStone69%of vault · bad debt · $17.21mOracle exposure 7%What it's made of
Priced off live market data — a depeg moves the price and can liquidate positions.
- → USDT086% LLTV0xd149…254cRedStone
- → USDT077% LLTV0xd149…254cRedStone
If it breaks
−30% default+1 market with no current position
Oracle dependencies
1 feed · 1 control pointUp to7%of vault drainable if these feeds are mispriced · $1.81m
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.
- RedStone·a 2/3 Safe multisigprices sthUSD, thBILL0x42f0…fc927% of vault · $1.81mdrainable if it is compromised
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 | ||
| 13% | up to 69% | Instant | ||
| Price-driven collateral stress(1) | ||||
| 13% | up to 69% | Instant | ||
| Oracle & liquidation failures(5) | ||||
| 13% | up to 69% | Instant | ||
| 13% | up to 69% | Instant | ||
| — | up to 7% | Instant | ||
| — | up to <1% | Instant | ||
| <1% | up to <1% | Instant | ||
| Vault role & allocator(3) | ||||
| — | up to 69% | 3 days | ||
| — | up to 69% | Instant | ||
| — | up to 50% | 3 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 3 days to exit before owner/curator actions land
Curator change queued
The timelock is your window to exit before each one takes effect.
- increase timelock— applies now; no time to exit first
Sentinels3 · 1 multisig · 2 EOAsSafety 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.
- single key (EOA)0x41a5…1eed
- 3-of-7 multisig0x7084…84cd
- single key (EOA)0xedc1…3cd1
Allocators3 · 1 multisig · 2 EOAsReaches 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.
- single key (EOA)0x5bcf…7352
- 3-of-7 multisig0x9e33…0585
- single key (EOA)0xa690…da21
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.
MORPHO0x58D9…c2B2Dependencies that can affect your deposit
7 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.