Gauntlet EURC Balanced
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 EURC (a euro stablecoin on Base) which the vault lends out entirely to borrowers who post ETH, stETH, Bitcoin, or other crypto collateral. The vault earns interest from borrowing demand; the rate adjusts based on supply and demand for each collateral type, with no idle cash buffer.
Gauntlet runs the vault with a conservative posture—all collateral is blue-chip crypto assets (ETH variants and Bitcoin) at uniform 86% loan-to-value thresholds.
The 0.99% APY comes entirely from borrowing demand against four ETH/Bitcoin collateral markets, each running at 81% utilization. No idle cash and no listed incentives.
The vault is 109% allocated to WETH, meaning it's over-leveraged relative to deposits—a structural mismatch typical of Morpho Blue design. Collateral risk is concentrated in ETH/stETH/Bitcoin; a sharp drop in any would trigger liquidations and potential recovery friction. EURC itself shows a healthy depeg signal.
Good fit for an allocator seeking low-friction euro stablecoin lending with minimal operational complexity if you're comfortable with concentrated ETH collateral and modest yield. Avoid if you need diversified collateral types or capital preservation above ~1%.
How the composite risk score breaks down. Every number traces to an explicit input — /methodology documents each factor's formula.
The Gauntlet EURC Balanced vault aims to optimize for risk-adjusted yield across large and medium market cap assets and high liquidity yield sources. The vaults risk strategy follows Gauntlets Balanced framework whereby we curate supply to balance security and yield to provide a low risk profile at competitive APYs.
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.
Tail-case: a vulnerability surfaces in Morpho V2 that affects the vault's largest single market (84% 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 83.8% of TVL; top-3 concentration is 100%. Modeled at 50% bad-debt recovery on the worst position.
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 (19% of $0M TVL). $50M of the $50M request queues; the redeemer takes a ~0.58% 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.09% 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.