Gauntlet uETH Vault
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 UETH and the vault lends it out on Morpho Blue to borrowers who post cmETH (Coinbase staked ETH) as collateral. The vault earns interest paid by those borrowers, with the un-borrowed 47% sitting idle. The lending rate is set by supply and demand—when cmETH borrowers need liquidity, they pay the vault's LPs to borrow.
Gauntlet runs this vault; the data shows a single-collateral, single-asset book focused on cmETH lending at 92% loan-to-value.
The 1.70% APY comes almost entirely (1.62%) from borrower interest on cmETH loans at 93% utilization, with a small 0.08% contribution from Morpho rewards. Nearly half the vault sits un-borrowed, dragging the blended rate down.
The vault's sole risk is cmETH price movement relative to UETH—if Coinbase staked ETH falls sharply, the 92% LTV means borrowers near liquidation. The risk score of 15/100 reflects low technical complexity and no material shortfalls in the current cmETH market.
Good fit for conservative allocators seeking stablecoin-like returns on ETH-derivative collateral if comfortable with a single collateral type and willing to accept that 47% idle cash drags yield.
How the composite risk score breaks down. Every number traces to an explicit input — /methodology documents each factor's formula.
The Gauntlet WETH Vault will list a selection of liquid collateral markets and allocate across them to optimize risk-adjusted yield. The Vaults risk strategy will follow the CORE framework where Gauntlet curates deposits to balance security and yield to provide a moderate risk profile and competitive APY for WETH suppliers.
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.
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 (53% 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 52.7% of TVL; top-3 concentration is 53%. Modeled at 50% bad-debt recovery on the worst position.
Vault has $0M idle buffer (51% of $0M TVL). $50M of the $50M request queues; the redeemer takes a ~0.50% forced-exit discount weighted across collateral mix plus 7-day TVM cost. $50M of the request exceeds the vault's $0M TVL and cannot be redeemed at all.
48h sequencer halt on HyperEVM. 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 53% of TVL sitting in markets above 85% utilization. Total -0.27% 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.