HyperLend Pooled

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

HyperLend is a pooled lending market on Hyperliquid’s EVM with variable rates set by utilization. It held about $425M at the 2026-08-14 survey. The verdict is the chain’s, not the protocol’s. HyperLend documents an Aave-style Pool, hToken claims, liquidations, supply caps and audits by Cantina, Ackee and Pashov. Those controls sit on HyperEVM, which inherits HyperBFT consensus; major bridged assets also depend on signatures representing more than two-thirds of validator stake. The rejected-chain rule is therefore dispositive before market-level credit underwriting. This memo does not claim HyperLend failed an individual protocol review.

Kill criteria: the events that revoke this verdict
• Deploys meaningful liquidity on a chain the registry approves
• The Hyperliquid L1 verdict changes

The research file

The mechanism

Suppliers transfer an asset to HyperLend’s Pool and receive hTokens representing the claim. Borrowers pledge collateral; variable supplier yield comes from borrower interest as utilization changes; and accounts below a health factor of one can be liquidated. Each reserve has its own collateral parameters and supply cap, so TVL is not equivalent to available withdrawal liquidity or uniform credit quality.

Control and operating record

HyperLend governance controls parameters including supply caps, and the protocol documents audits by Cantina, Ackee Blockchain and Pashov Audit Group. Its own risk page correctly notes residual smart-contract and volatile-collateral risk after audit. We found no protocol loss event that changes this class decision; that is not a finding that oracle design, admin keys, every listed reserve or each audit remediation has been individually cleared.

The exit

A supplier can redeem only if Pool cash is available and the withdrawal would not make its own borrowing position unhealthy. HyperLend explicitly says insufficient liquidity requires waiting for more supply or borrower repayment. On top of that utilization constraint, execution depends on HyperEVM consensus; bridged USDC withdrawal also depends on the validator-signature and dispute-period process.

Why the class rule decides

Hyperliquid documents that HyperEVM shares HyperBFT security with HyperCore. Its validator delegation program uses applications, KYC/KYB, Foundation delegation and peer trust, and its bridge requires signatures exceeding two-thirds of stake. Under the standing chain framework, that security and exit dependency bars the market before asset selection. Review reopens if Hyperliquid passes chain approval or HyperLend gains material deployment and liquidity on an approved chain.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• HyperLend Docs — Pool contract and hToken mechanics · primary · accessed 2026-08-14
  Supports: Pool contract, hToken mechanics
• HyperLend Docs — supplier rates and withdrawal liquidity · primary · accessed 2026-08-14
  Supports: supplier rates, withdrawal liquidity
• HyperLend Docs — risks and auditors · primary · accessed 2026-08-14
  Supports: risks, auditors
• Hyperliquid Docs — HyperEVM security inheritance · primary · accessed 2026-08-14
  Supports: HyperEVM security inheritance
• Hyperliquid Docs — bridge security and withdrawals · primary · accessed 2026-08-14
  Supports: bridge security, withdrawals
• Hyperliquid Docs — validator delegation program · primary · accessed 2026-08-14
  Supports: validator delegation program

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.