Alpha LINK Enhanced V2
Risk reportEthereum0x610f…ae7e
Risk
Depositing into Alpha LINK Enhanced V2 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% $2.49m modeled all-to-zero bad-debt ceiling
wstLINKHybrid$2.49mbad debtOracle exposure $389,893$2.88m100% of vault$2.49m$389,893
wstLINKHybrid$2.49mbad debtOracle exposure $389,893What it's made of
wstLINK is priced from an exchange-rate/NAV leg ((unnamed feed)) — no market-rate feed, so it tracks redemption value, not market price.
- → LINK92% LLTV0x833b…b6d1
If it breaks
vault −30%Oracle dependencies
Up to$389,893drainable if these feeds are mispriced · 14% 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.
- Unidentified feeds· vendor and on-chain control not resolvedprices wstLINK$389,893 · 14% of vaultmispriceable if these feeds lie
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% | $2.87m | Full deposit | Instant | ||
| 20% | $585,346 | up to $2.49m | Instant | ||
| Price-driven collateral stress(1) | |||||
| 20% | $585,346 | up to $2.49m | Instant | ||
| Oracle & liquidation failures(4) | |||||
| 20% | $585,346 | up to $2.49m | Instant | ||
| 20% | $585,346 | up to $2.49m | Instant | ||
| 20% | $585,346 | up to $2.49m | Instant | ||
| — | — | up to $389,893 | Instant | ||
| Vault role & allocator(3) | |||||
| — | — | up to $2.49m | 3 days | ||
| — | — | up to $2.49m | Instant | ||
| — | — | up to $1.44m | 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 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.
- single key (EOA)0xca47…66d9
Allocators2 · 2 multisigsReaches 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.
- 2-of-4 multisig0x6788…9da5
- 2-of-4 multisig0xeb4a…4645
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
6 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.