Gauntlet WETH Balanced (Ethereum) Risk

Collateral and oracle exposure

Each token you're exposed to, and the market it backs. If that market breaks, this is how much the vault loses, in dollars and as a share of the vault. Open a row for the price feed, stress curve, and supply-cap detail. Below, the oracles those prices depend on and what is at stake if one is compromised.

If collateral prices dropper asset · no liquidations · stress estimate

est. bad debt up to 23% of deposit

Driven by wstETH −30% 19% · weETH −30% 3% · cbBTC −30% <1% · other <1% · −100% 84% modeled all-to-zero bad-debt ceiling

CollateralAllocationMarket ExposureOracle Exposure

wstETHHybridChainlink71%of vault · bad debt · $712,451Oracle exposure 13%

84%of vault · $846,12771%of vault · $712,45113%separate path

What it's made of

wstETH token page

Hybrid· Chainlink(exchange-rate)

wstETH is priced from an exchange-rate/NAV leg (wstETH/stETH exchange rate) — no market-rate feed, so it tracks redemption value, not market price.

BasewstETH/stETH exchange rateExchange rate

Markets this collateral backs · 2

→ WETH97% LLTV0xbd60…71d8
→ WETH95% LLTV0x2a01…ad72Chainlink

Aggregate Collateral Trust (ACT):$611.76m111 vaultsToken:0x7f39…2ca0Allocation: 84% of the vault · $846,127

If it breaks

−30% default

At −30%:est. bad debt up to 19% of depositUses 2 market LLTV curves · capped at allocation $846,127 · drag to set this asset's drop

Oracle exposure: up to 13% of vault drainable if the feed is compromisedseparate path: an attacker borrows against a fake price

weETHHybrid13%of vault · bad debt · $134,343Oracle exposure 3%

16%of vault · $165,34013%of vault · $134,3433%separate path

What it's made of

weETH token page

Hybrid(exchange-rate)

weETH is priced from an exchange-rate/NAV leg (weETH/ETH exchange rate) — no market-rate feed, so it tracks redemption value, not market price.

BaseweETH/ETH exchange rateExchange rate

Markets this collateral backs · 1

→ WETH95% LLTV0xbdd2…8a72

Aggregate Collateral Trust (ACT):$373.61m51 vaultsToken:0xcd5f…b7eeAllocation: 16% of the vault · $165,340

If it breaks

−30% default

At −30%:est. bad debt up to 3% of depositUses 1 market LLTV curve · capped at allocation $165,340 · drag to set this asset's drop

Oracle exposure: up to 3% of vault drainable if the feed is compromisedseparate path: an attacker borrows against a fake price

+3 markets with no current position

Oracle dependencies

2 feeds2 control points

Up to16%of vault drainable if these feeds are mispriced · $164,673

Each price traces to a feed and the onchain admin that can move it. Compromise either to misprice the collateral and borrow against it. Per-row amounts overlap and are not summed.

Chainlink / RedStone·a 4/9 Safe multisigprices cbBTC, WBTC, LBTC, wstETH0x21f7…73ca13% of vault · $133,676drainable if it is compromised
RedStone / Chainlink·a 2/3 Safe multisigprices LBTC0x6906…4472<1% of vault · $0.0000000009drainable if it is compromised
Onchain exchange rate· no external feed or adminprices weETH3% of vault · $30,997mispriceable only via the issuing contract

Loss scenarios

Each row is a distinct failure, and every loss is a share of your deposit — the same percentage whatever you deposited. Loss is that share at a −30% collateral crash, the standard stress; Worst case is the ceiling if everything goes wrong, a conditional loss if it happens rather than a likelihood. Open a row for the loss at every crash depth, the dollar amounts, conditions, and the math.

11 scenarios · 9 with no time to exit · loss as % of deposit


Full-deposit & protocol-level(2)
	100%	Full deposit	Instant
	23%	up to 84%	Instant
Price-driven collateral stress(1)
	23%	up to 84%	Instant
Oracle & liquidation failures(5)
	16%	Full deposit	Instant
	23%	up to 84%	Instant
	23%	up to 84%	Instant
	23%	up to 84%	Instant
	—	up to 16%	Instant
Vault role & allocator(3)
	—	Full deposit	3 days
	—	Full deposit	Instant
	—	up to 50%	3 days

Trust and control

The people and processes that can change this protocol under you.

Track record · no pool-level losses recorded · 5 protocol incidents · 36 audits

Vault operators

The roles that can actually move your deposit — the real principal-loss path.

Reaches deposit, no delayReaches deposit, timelockedCan't reach deposit

Role timelock 3 days to exit before owner/curator actions land

Owner4-of-7 multisig0xc684…faec

Curator3-of-7 multisig0x9e33…0585

Sentinels21 multisig1 EOASafety role · veto only

Safety role, not an attack role: can revoke ANY pending timelocked curator change, instantly cut caps, and pull funds from adapters back to idle. Strictly risk-reducing — a captured sentinel cannot introduce new risk.

3-of-7 multisig0x7084…84cd
single key (EOA)0xdb92…1dca

Allocators21 multisig1 EOAReaches deposit · instant

Moves funds between markets the curator has ALREADY approved — instantly, with NO timelock and no exit window. Cannot reach a brand-new market, but can concentrate you into an approved-but-stressed market or order withdrawals so you hit weak liquidity first.

3-of-7 multisig0x9e33…0585
single key (EOA)0xf9ce…f7ed

Audits

361 critical, 13 high findings logged

CertoraDec 15, 2025report
BlackthornDec 4, 2025report
SpearbitDec 4, 2025report
BlackthornSep 15, 2025report

+32 more audits

Governance & control

Protocol-wide governance: bounded context, not the path to your deposit.

Governance owner6-of-1012 chains0xcba2…9afa

Rewards owner3-of-70xf057…b2e9

Rewards updater3-of-50x5eb9…3297

Snapshot proposer5-of-80x6abf…f6a2

Governance Contract0xcBa2…9AFa

Top-10 Voter Concentration100.0%

Quorum to Pass500,000 MORPHO· top 10 hold 2.49m

Voting TokenMORPHO0x58D9…c2B2

Dependencies that can affect your deposit

9 things this pool relies on but doesn't control. Select one for its story.

Morpho Blue

oracles

Market Specific oracle

Every Morpho Blue market chooses an immutable oracle contract at creation; implementations can be Chainlink-like, exchange-rate, fixed-price, or custom. Failure modes: attacker-favourable price feed (covered in market-oracle-compromise) or price() revert / staleness blocking liquidations (covered in oracle-liveness-or-malfunction).

No quantified loss scenario references this dependency directly.