Steakhouse Prime USDC
Risk reportKatana0x61d4…3c1d
Risk
Depositing into Steakhouse Prime 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 vbWBTC −30% 17% · vbETH −30% <1% · −100% 90% modeled all-to-zero bad-debt ceiling
vbWBTCMarketChainlink90%of vault · bad debt · $11.83mOracle exposure 10%99.9%of vault · $13.18m90%of vault · $11.83m10%separate path
vbWBTCMarketChainlink90%of vault · bad debt · $11.83mOracle exposure 10%What it's made of
vbWBTC uses Chainlink market-rate aggregator feed(s).
- → vbUSDC86% LLTV0xb60f…040eChainlink
If it breaks
−30% defaultvbETHMarketChainlink0.1%of vault · bad debt · $7,310.38Oracle exposure <0.1%0.1%of vault · $8,120.290.1%of vault · $7,310.38<0.1%separate path
vbETHMarketChainlink0.1%of vault · bad debt · $7,310.38Oracle exposure <0.1%What it's made of
vbETH uses Chainlink market-rate aggregator feed(s).
- → vbUSDC86% LLTV0xd423…bf47Chainlink
If it breaks
−30% default+2 markets with no current position
Oracle dependencies
1 feed · 1 control pointUp to10%of vault drainable if these feeds are mispriced · $1.35m
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 / RedStone·a 4/9 Safe multisigprices vbWBTC, weETH, vbETH0x0787…333410% of vault · $1.35mdrainable 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 | ||
| 17% | up to 90% | Instant | ||
| Price-driven collateral stress(1) | ||||
| 17% | up to 90% | Instant | ||
| Oracle & liquidation failures(4) | ||||
| 17% | up to 90% | Instant | ||
| 17% | up to 90% | Instant | ||
| 17% | up to 90% | Instant | ||
| — | up to 10% | Instant | ||
| Vault role & allocator(4) | ||||
| — | Full deposit | 7 days | ||
| — | Full deposit | Instant | ||
| — | up to 50% | 7 days | ||
| — | up to 8% | Instant | ||
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
Allocators5 · 2 multisigs · 2 contracts · 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-3 multisig0x0000…9da8
- contract0x39eb…2412
- contract0x5fe1…7852
- 1-of-6 multisig0xe6fc…4887
- 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.
MORPHO0x58D9…c2B2Dependencies that can affect your deposit
11 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.