Steakhouse High Yield USDT0
Plain-English summary of this vault — what it does, who runs it, where the yield comes from, and what could break it. Generated from the same deterministic inputs shown elsewhere on this page; the numbers are the source, this is just the explanation.
Depositors put USDT0 (a Polygon stablecoin) into this vault, and Steakhouse lends it out on Morpho Blue to borrowers posting MaticX, WBTC, and WETH as collateral. The interest rate borrowers pay funds the 5.10% APY; no cash sits idle.
Steakhouse Financial runs the vault, operating a concentrated bet on MaticX collateral (94% of lending), with smaller WBTC and WETH positions.
The 5.10% APY breaks into 4.34% from borrower interest payments and 0.76% from Morpho protocol incentives and curator rebates on active markets.
MaticX concentration (94% of capital) and high utilization (88%) on that market are the main exposure; MaticX price moves directly hit borrower collateral adequacy. WBTC and WETH positions face similar liquidation risk at their respective 86% loan-to-liquidation thresholds, though smaller in size.
Good fit for an allocator seeking low-complexity stablecoin yield on Polygon if willing to accept MaticX's volatility as the dominant risk lever; avoid if MaticX exposure feels unhedged relative to portfolio.
How the composite risk score breaks down. Every number traces to an explicit input — /methodology documents each factor's formula.
The Steakhouse High Yield USDT0 vault aims to optimize yields by lending USDT0 against a wide range of collaterals.
What you are actually getting paid for, expressed as a share of net APY.
Interest paid by borrowers on Morpho Blue markets the vault supplies into.
Estimated boost from Morpho-side rewards programs and curator rebates active on these markets.
The honest version. Every structural failure mode this vault is exposed to, ranked by severity. If you want to know whether to invest, start here.
Cap-weighted utilization is 87.8%, leaving little idle buffer. Large same-day redemptions may queue behind active loan repayments.
Every market relies on an external price feed. A stale or manipulated feed can mis-price collateral and produce unrecoverable bad debt.
What this vault is actually exposed to — including dependencies that are not visible from the strategy name.
Every market the vault has supplied into, with current LTV, LLTV, oracle, and IRM. Idle balances are listed explicitly.
Modeled NAV impact under historical and hypothetical tail events. Each impact = − (shock magnitude) × (vault exposure) × (pass-through). Hover the calculator icon for the per-scenario formula.
Tail-case: a vulnerability surfaces in Morpho Blue that affects the vault's largest single market (94% of TVL). Modeled at 50% loss on that exposure; full vault is not assumed at risk since markets are isolated.
Curator routes into a market that develops bad debt or an oracle break. Worst single position is 94.4% of TVL; top-3 concentration is 100%. Modeled at 50% bad-debt recovery on the worst position.
100% of TVL is in markets running >85% utilization. Redemption requests on that slice queue until borrowers repay; remaining LPs absorb a small forced-exit discount.
Vault has $0M idle buffer (12% of $0M TVL). $50M of the $50M request queues; the redeemer takes a ~0.50% forced-exit discount weighted across collateral mix plus 12-day TVM cost. $50M of the request exceeds the vault's $0M TVL and cannot be redeemed at all.
48h sequencer halt on Polygon. Collateral drifts while liquidations are frozen; the LLTV buffer absorbs liquidation-clearable moves, the excess accrues as bad debt. Plus a small forced-exit discount on the 100% of TVL sitting in markets above 85% utilization. Total -0.51% NAV loss.
On-chain contracts, control surface, and per-market parameters. The diligence checklist surface — every value here is what an allocator needs to copy into a memo before sizing a deposit.
Market parameters (5)
Oracle, IRM, and LLTV per Morpho Blue market the vault routes into. Click an address to inspect the contract on a block explorer.Curator and parameter changes detected by VaultScanner's snapshot diff. Refreshed every 6 hours.
180 trailing days. APY, TVL, utilization, and an APY drawdown view to show how the vault has actually behaved — not just where it sits today.