Yearn KAT
Risk reportKatana0x9b1a…b8cc
Risk
Depositing into Yearn KAT means underwriting risks you usually can't see: how much you could lose, whether you'd get out in time, and what would cover it.
Left to right, a deeper collateral crash. Hover any point for the scenarios that drive the loss — only a smart-contract bug reaches a total loss.
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.
−100% $279,606 modeled all-to-zero bad-debt ceiling
avKATHybrid$279,606bad debtOracle exposure $42,882$322,488100% of vault$279,606$42,882
avKATHybrid$279,606bad debtOracle exposure $42,882What it's made of
avKAT is priced from an exchange-rate/NAV leg rather than a direct market-rate feed.
- → KAT77% LLTV0xc5d4…f47c
If it breaks
vault −30%Oracle dependencies
Up to$42,882drainable if these feeds are mispriced · 13% of vault
Each price traces to a feed and the on-chain admin that can move it. Compromise either to misprice the collateral and borrow against it. Per-row amounts overlap and are not summed.
- On-chain exchange rate· no external feed or adminprices avKAT$42,882 · 13% of vaultmispriceable only via the issuing contract
Loss scenarios
Each row is a distinct failure. Possible loss is the share of your deposit at the selected collateral drop; Worst case is the ceiling if everything goes wrong — a conditional loss if it happens, not a likelihood. Price-scaling rows move with the drop selector; the rest are fixed. Enter a deposit to see the dollar figures as your own. Open a row for conditions, mitigations, and the math.
| Full-deposit & protocol-level(2) | |||||
| 100% | $322,488 | Full deposit | Instant | ||
| 8% | $25,419 | up to $279,606 | Instant | ||
| Price-driven collateral stress(1) | |||||
| 8% | $25,419 | up to $279,606 | Instant | ||
| Oracle & liquidation failures(5) | |||||
| 8% | $25,419 | up to $279,606 | Instant | ||
| 8% | $25,419 | up to $279,606 | Instant | ||
| 8% | $25,419 | up to $279,606 | Instant | ||
| 8% | $25,419 | up to $279,606 | Instant | ||
| — | — | up to $42,882 | Instant | ||
| Vault role & allocator(3) | |||||
| — | — | up to $310,327 | 3 days | ||
| — | — | up to $310,327 | Instant | ||
| — | — | up to $161,244 | 3 days | ||
Trust and control
The people and processes that can change this protocol under you.
Vault operators
The roles that can actually move your deposit — the real principal-loss path.
Role timelock 3 days to exit before owner/curator actions land
Sentinels1 · 1 multisigSafety 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-5 multisig0xe6ad…7162
Allocators3 · 1 contract · 2 EOAsReaches 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.
- single key (EOA)0x50b7…a8fa
- single key (EOA)0x75a1…780d
- contract0xffb8…0862
Audits
- Certora· 15 Dec, 2025report
- Blackthorn· 4 Dec, 2025report
- Spearbit· 4 Dec, 2025report
- Blackthorn· 15 Sep, 2025report
Governance & control
Protocol-wide governance: bounded context, not the path to your deposit.
MORPHO0x58D9…c2B2Dependencies that can affect your deposit
7 things this pool relies on but doesn't control. Select one for its story.
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.