How Does HyperLend Work?
HyperLend is a lending protocol on Hyperliquid's HyperEVM blockchain, built as an officially recognized fork of Aave. It offers both shared-risk core pools and isolated markets, with $447M in deposits. Its B grade reflects the proven Aave codebase and standard lending design, with moderate risk from operating on the newer HyperEVM chain.
TVL
$416M
Sector
Lending
Risk Grade
B
Value Grade
D
Core Mechanisms
6.1.1
Overcollateralized lending pools forked from Aave codebase with shared-risk core pools
Standard Aave lending pattern. Recognized as friendly fork by Aave DAO with 10% revenue share.
6.1.4
Isolated lending markets with customizable LTV ratios for higher-risk assets
Standard isolated market pattern from Aave v3 isolation mode.
6.2.2
Kinked utilization curve interest rate model inherited from Aave
Standard Aave-style interest rate curve with kink point.
6.3.2
Fixed-spread liquidation mechanism from Aave with keeper bot execution
Standard Aave liquidation with fixed bonus incentive.
6.4.1
RedStone oracle feeds for price data on HyperEVM chain
Standard oracle integration for lending. Uses RedStone on HyperEVM.
How the Pieces Interact
Aave's battle-tested contracts run on a newer L1 (HyperEVM). Chain-level issues could freeze lending operations including liquidations during volatile markets.
Liquidation accuracy depends on oracle timeliness. On a newer chain with less oracle redundancy, delayed price updates during flash crashes could cause incorrect liquidations.
Dual pool architecture means a bad asset in core pools could contaminate shared liquidity, while isolated markets fragment capital.
Deep integration with Hyperliquid perp trading creates correlated risk. A major Hyperliquid incident could trigger mass withdrawals from HyperLend.
What Could Go Wrong
- HyperLend is a friendly fork of Aave deployed on Hyperliquid's HyperEVM chain. While Aave's codebase is well-audited, HyperEVM is a newer L1 with limited battle-testing compared to Ethereum, introducing infrastructure risk beneath a proven lending protocol.
- Oracle dependencies for liquidation decisions rely on RedStone's HyperStone — dedicated Hyperliquid infrastructure with 3-second updates, but single-provider dependency. Delayed price updates during extreme market conditions could cause incorrect liquidations on a chain where status-page reporting does not reliably reflect EVM-layer health.
- The Unified Trading Account (UTA) deepens integration between HyperLend and Hyperliquid perpetuals — borrowing and trading are executed in a single wallet flow. This architectural coupling amplifies correlated risk: a Hyperliquid market stress event could simultaneously trigger mass liquidations across HyperLend.
HyperEVM Chain Disruption During Market Crash
TailTrigger: HyperEVM experiences sequencer downtime or consensus issues during a >20% market crash, freezing HyperLend liquidations for >30 minutes
- 1.Major market crash causes >20% price decline in major assets within hours — HyperLend positions approach liquidation thresholds across core and isolated pools
- 2.HyperEVM chain experiences congestion or sequencer issues under high transaction load — Liquidation transactions fail to execute, oracle price updates are delayed
- 3.Undercollateralized positions accumulate as liquidations are frozen — Bad debt builds up in core shared pools, contaminating all depositors
- 4.When chain resumes, cascading liquidations execute simultaneously — Liquidation slippage exceeds bonuses, remaining bad debt is socialized across lenders
Risk Profile at a Glance
Overall: B (25/100)
Lower score = safer