Gauntlet cbBTC Core
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 supply cbBTC (a Bitcoin wrapper on Base) and it gets lent out entirely to borrowers who post LBTC (Lido's liquid staking Bitcoin) as collateral on Morpho Blue. The borrowing rate—and therefore the deposit rate—floats based on how much demand there is for cbBTC loans against that collateral.
Gauntlet runs this vault, operating a single-collateral, single-asset book concentrated on LBTC borrowing demand.
The 0.10% APY comes entirely from interest paid by LBTC borrowers; there is no idle un-borrowed cash generating additional rate spread, and no incentive programs listed.
The vault's material risk is the tight liquidation threshold—borrowers' LBTC positions get seized at 95% LTV, leaving little margin if LBTC price falls relative to cbBTC. At 76% utilization, most deposited cbBTC is already lent out, so a sudden withdrawal spike could force rapid unwinding.
Good fit for risk-tolerant allocators treating this as a tactical high-LTV Bitcoin lending play; avoid if you need stability or expect volatile Bitcoin-to-Bitcoin asset spreads.
How the composite risk score breaks down. Every number traces to an explicit input — /methodology documents each factor's formula.
The cbBTC Core Vault will list a range of liquid collateral markets and continuously optimize risk-adjusted yield across those markets. This vault targets a higher risk level than Gauntlet's Prime Vaults.
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.
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 94.5%. 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.
Coinbase-custodied; tail risk is regulatory or exchange-level event temporarily breaking redemption. Mark-to-market loss on 100% of vault TVL (loan asset is cbBTC).
Vault has $0M idle buffer (24% 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.
48h sequencer halt on Base. 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 0% of TVL sitting in markets above 85% utilization. Total -0.14% 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 (2)
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.