Morpho eUSD
- Deposits disabledREDVault-level
Morpho has flagged this vault as not accepting deposits. Existing positions remain on-chain but new capital is being turned away — usually a curator-initiated wind-down or response to an active issue.
- Invalid NameREDVault-level
Morpho has flagged this vault: invalid_name.
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 eUSD (a stablecoin) into this vault, and it lends that cash out on Morpho Blue to borrowers putting up cbBTC (Bitcoin on Base, the canonical wrapped version) as collateral. The interest rate borrowers pay is set by supply and demand on Morpho's order-book-style lending market — the vault earns whatever that market rate is.
RE7 Labs runs a single-market vault focused entirely on cbBTC lending, operating at high utilization (80% of available capital lent out).
The 1.36% APY comes almost entirely (1.29%) from borrowers' interest payments against cbBTC collateral; the remaining 0.07% is estimated Morpho protocol incentives and curator rebates. No idle cash buffer exists — all deposits are deployed.
cbBTC price collapse is the core risk. At an 86% liquidation threshold, a ~14% drop in cbBTC price triggers forced collateral sales. The vault also carries counterparty risk on cbBTC itself (the wrapping mechanism and bridge) and concentration risk: 100% of lending exposure sits in a single market with a single collateral type.
Avoid — Morpho has posted RED warnings (deposits disabled; invalid name). Do not allocate until those warnings are resolved and the vault demonstrates normal operation.
How the composite risk score breaks down. Every number traces to an explicit input — /methodology documents each factor's formula.
The Re7 eUSD vault supplies eUSD to various collateral markets with a focus on the Reserve Protocol ecosystem.
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.
Weighted LLTV across markets is 86.0%. Sharp collateral drawdowns can trigger cascading liquidations faster than vault parameters can be adjusted.
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 (100% 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 100.0% of TVL; top-3 concentration is 100%. Modeled at 50% bad-debt recovery on the worst position.
Vault has $0M idle buffer (20% of $0M TVL). $50M of the $50M request queues; the redeemer takes a ~0.50% forced-exit discount weighted across collateral mix plus 11-day TVM cost. $50M of the request exceeds the vault's $0M TVL and cannot be redeemed at all.
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 (4)
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.