Gauntlet USDC Prime
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 USDC into this vault, and Gauntlet lends it all out to borrowers who post Bitcoin (WBTC) as collateral. Borrowers can draw down to 86% of their Bitcoin's value, and they pay interest on what they borrow—that interest flow is what generates the 3.69% APY for USDC depositors.
Gauntlet runs this vault; the data shows a single-collateral book concentrated entirely on WBTC lending at tight utilization (86%).
The 3.69% APY comes from borrowing demand against WBTC collateral. With 86% of the vault's USDC already deployed and no idle buffer, nearly all deposits are at work.
The vault's entire exposure is to WBTC price moves. If Bitcoin falls sharply, borrowers approach liquidation at the 86% loan-to-value threshold, which could create forced selling pressure or bad debt. The vault carries a 29/100 risk score and faces no flagged material risks above elevated severity.
Good fit for an allocator seeking simple, low-complexity USDC yield backed by Bitcoin collateral if comfortable holding Bitcoin price risk; avoid if you need diversification across collateral types or demand a meaningful cash buffer.
How the composite risk score breaks down. Every number traces to an explicit input — /methodology documents each factor's formula.
The Gauntlet USDC Prime vault aims to optimize for risk-adjusted yield by allocating across large market cap assets and high liquidity yield sources. The vaults risk strategy follows the Gauntlet Prime conservative framework whereby we curate supply to manage security and yield to provide a low risk profile at competitive APY
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.
March 2023 SVB episode: USDC traded as low as $0.88 before banking exposure was clarified. Mark-to-market loss on 100% of vault TVL (the loan asset is USDC).
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.
Vault has $0M idle buffer (14% 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.
Tail-case: a vulnerability surfaces in Morpho V2 that affects the vault's largest single market (0% 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 0.0% of TVL; top-3 concentration is 0%. Modeled at 50% bad-debt recovery on the worst position.
0% 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.
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.