Hyperithm vbUSDC Apex
- Not whitelistedYELLOWmHYPER / vbUSDC
Vault is not on Morpho's official whitelist. It may still function but has not been reviewed for inclusion in the curated set.
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 in vbUSDC (a stablecoin variant on Katana) and the vault lends it out entirely to borrowers who post Bitcoin and Ethereum as collateral. The interest rate is set by market supply and demand—when borrowers want the stablecoin, rates rise; when demand is slack, they fall.
Hyperithm runs this vault with a simple two-asset lending book: 84% against BTC.b collateral and 16% against vbETH.
The 1.68% APY comes from borrowing demand against those two collateral types; vbETH borrowers are actively using their loans (83% utilization) while BTC.b demand is light (8% utilization). There are no idle reserves and no listed incentive programs.
The vault's main risk is that vbUSDC itself is not a tracked stablecoin, so depeg events aren't monitored—if vbUSDC loses its peg, depositors' value drops with no early signal. The collateral base (BTC.b and vbETH) carries normal crypto asset volatility, though the protocol hasn't flagged elevated severity risks.
Avoid unless you have specific conviction on vbUSDC's stability; the 1.68% APY doesn't compensate for the blind spot on an untracked stablecoin, and the vault is not Morpho-whitelisted.
How the composite risk score breaks down. Every number traces to an explicit input — /methodology documents each factor's formula.
Hyperithm vbUSDC Apex vault maximizes yield by swiftly integrating unique collaterals providing borrowers with high-return opportunities through active optimization while ensuring effective risk management.
Morpho V2 vault — wraps downstream Morpho markets and V1 vaults via adapters.
Some V2 adapters point at Morpho Blue markets directly; their underlying market detail isn't resolvable in the universe-level fetch, so this vault carries a V2 opacity surcharge in the risk model.
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.
V2 vaults route through adapters into downstream venues. A misbehaving adapter (paused, drained, or pointing at a compromised target) can lock or mismark a portion of the vault until governance acts.
Sequencer halt on Katana blocks liquidations and redemptions for 48 hours. Without per-allocation buffers we apply a baseline 0.5% liquidity discount scaled by chain severity (1.5×).
Vault has $0M idle buffer (100% of $0M TVL). $50M of the $50M request queues; the redeemer takes a ~0.50% forced-exit discount weighted across collateral mix plus 0-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.