How Does HypurrFi Pooled Work?
HypurrFi Pooled is a lending protocol on the Hyperliquid blockchain where users can deposit assets like HYPE, stHYPE, and USDC to earn interest or borrow against their holdings. Built on the Euler vault technology stack, it uses a pooled design where all supplied assets share a single collateral base for higher capital efficiency. With $38M in deposits, it is one of the largest lending protocols on Hyperliquid, but the young age of both the protocol and the underlying chain introduce elevated risk compared to established lending platforms.
TVL
$31M
Sector
Lending
Risk Grade
C
Value Grade
D+
Core Mechanisms
6.1.1
Overcollateralized pooled lending with unified collateral base on Hyperliquid EVM
Standard Aave-inspired lending model. Borrowers deposit collateral worth more than loan value. Pooled design means all assets share risk.
6.2.2
Kinked utilization curve for interest rate determination
Standard Aave/Compound-style kinked interest rate model with a jump multiplier above the kink point.
6.3.2
Automated liquidation with fixed bonus incentive
Liquidators receive a fixed bonus for liquidating undercollateralized positions. Standard pattern from Euler vault framework.
6.4.3
NovelHyperliquid validator oracle feeds with Redstone and Pyth fallbacks
Novel oracle approach using Hyperliquid's own validator network as primary price source. Less battle-tested than Chainlink. Fallback to Redstone and Pyth provides redundancy.
6.1.3
Cross-collateralized shared pool design for multi-asset risk pooling
All supplied assets form a unified collateral base. Higher capital efficiency than isolated markets but contagion risk from any single bad asset.
2.1.2
Percentage-based borrowing fee accruing to liquidity providers
Standard interest spread model where borrowers pay rates and lenders earn a portion. Protocol takes a reserve factor cut.
5.4.1
Multisig-controlled protocol parameters and upgrades
Protocol parameters controlled by team multisig. No decentralized governance token for HypurrFi Pooled specifically.
How the Pieces Interact
If Hyperliquid validator oracle feeds lag or fail for any single asset in the shared pool, the entire pool's health factor calculations become unreliable, potentially allowing undercollateralized borrowing or preventing timely liquidations across all positions.
Hyperliquid has experienced multiple exploits at the chain level (HLP vault attacks). A chain-level vulnerability could simultaneously compromise the oracle feeds, liquidation infrastructure, and collateral custody that HypurrFi depends on.
The Hyperliquid DeFi ecosystem is young with limited secondary markets. During a cascade liquidation, insufficient on-chain liquidity to absorb liquidated collateral could result in bad debt accumulation faster than on established chains.
HypurrFi leverages Euler's vault technology stack but operates under its own multisig governance. Parameter changes (collateral factors, oracle sources) could be made without the Euler community's oversight or risk review.
What Could Go Wrong
- HypurrFi is built exclusively on Hyperliquid EVM, a relatively young chain that has suffered multiple exploits including a $4M HLP vault drain in March 2025 and a $5M attack in November 2025. Chain-level risk directly impacts all HypurrFi deposits.
- Pooled markets combine all supplied assets into a single unified collateral base, meaning a problem with any single supported asset (depeg, oracle failure) contaminates the entire pool rather than being isolated.
- Oracle infrastructure relies on Hyperliquid validator feeds as the primary price source, with Redstone and Pyth as fallbacks. The primary oracle is only as decentralized as the Hyperliquid validator set, which is relatively small and concentrated.
Hyperliquid Chain-Level Exploit Cascading into HypurrFi
ModerateTrigger: A chain-level vulnerability on Hyperliquid EVM is exploited, similar to the March or November 2025 HLP attacks, but affecting the broader EVM execution environment.
- 1.An exploit targets Hyperliquid EVM infrastructure, disrupting validator operations or oracle feeds — HypurrFi oracle prices become stale or manipulated, health factor calculations across all pooled positions become unreliable
- 2.Liquidation bots cannot execute correctly due to compromised on-chain state — Undercollateralized positions remain open, accumulating bad debt as asset prices move
- 3.Panic withdrawal attempts overwhelm the protocol as users rush to exit — Utilization spikes to 100%, locking remaining depositors in the pool with no withdrawal liquidity
- 4.Bad debt exceeds protocol reserves — Lenders face haircuts on their deposits with no insurance fund or safety module to backstop losses
Risk Profile at a Glance
Overall: C (45/100)
Lower score = safer