Hyperithm USDC Apex
Risk reportEthereum0x7777…7777
Risk
Depositing into Hyperithm USDC Apex 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.
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.
Driven by mHyperBTC −30% 7% · mHYPER −30% <1% · −100% 90% modeled all-to-zero bad-debt ceiling
mHyperBTCHybridChainlink79%of vault · bad debt · $1.9mOracle exposure 9%88%of vault · $2.11m79%of vault · $1.9m9%separate path
mHyperBTCHybridChainlink79%of vault · bad debt · $1.9mOracle exposure 9%What it's made of
mHyperBTC uses a composite oracle path; verified external provider(s): Chainlink.
- → USDC77% LLTV0xece5…a3c1Chainlink
If it breaks
−30% defaultmHYPERMarket11%of vault · bad debt · $262,719.02Oracle exposure 1%12%of vault · $295,189.8511%of vault · $262,719.021%separate path
mHYPERMarket11%of vault · bad debt · $262,719.02Oracle exposure 1%What it's made of
mHYPER is priced via mHYPER/USD — market-rate feed.
- → USDC77% LLTV0xdabd…f1c0
If it breaks
−30% default+3 markets with no current position
Oracle dependencies
1 feed · 1 control pointUp to10%of vault drainable if these feeds are mispriced · $240,961.47
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.
- Chainlink·a 4/9 Safe multisigprices cbBTC, WBTC, wstETH, mHyperBTC0x21f7…73ca9% of vault · $208,490.63drainable if it is compromised
- Unidentified feeds· vendor and on-chain control not resolvedprices mHYPER1% of vault · $32,470.84mispriceable if these feeds lie
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.
| Full-deposit & protocol-level(2) | ||||
| 100% | Full deposit | Instant | ||
| 8% | up to 90% | Instant | ||
| Price-driven collateral stress(1) | ||||
| 8% | up to 90% | Instant | ||
| Oracle & liquidation failures(5) | ||||
| 8% | up to 90% | Instant | ||
| 8% | up to 90% | Instant | ||
| 9% | up to 88% | Instant | ||
| 7% | up to 79% | Instant | ||
| — | up to 10% | Instant | ||
| Vault role & allocator(4) | ||||
| — | Full deposit | 3 days | ||
| — | Full deposit | Instant | ||
| — | up to 50% | 3 days | ||
| — | 0% | Instant | ||
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
Allocators2 · 1 contract · 1 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.
- contract0xfd32…c75d
- single key (EOA)0x345e…3c5f
Audits
- Certora· Dec 15, 2025report
- Blackthorn· Dec 4, 2025report
- Spearbit· Dec 4, 2025report
- Blackthorn· Sep 15, 2025report
Governance & control
Protocol-wide governance: bounded context, not the path to your deposit.
MORPHO0x58D9…c2B2Dependencies that can affect your deposit
9 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.