HyperLend Pooled

HyperLend Pooled is a lending / money-market protocol on Hyperliquid L1 (HyperEVM), offering pooled, overcollateralized borrowing and yield across multiple asset pools. ### Identification

• Name: HyperLend Pooled (part of the HyperLend protocol).
• Category: DeFi lending / borrowing, Aave-style overcollateralized pools.
• Website / App: HyperLend primary site at hyperlend.finance; pooled markets are accessed via the HyperLend app (third‑party data consistently references “HyperLend Pooled” as the lending interface).
• Docs: Technical and user docs hosted under the HyperLend docs domain (e.g. “pool | HyperLend” describing supply, borrow, collateral, liquidation, flash loans).
• Chains: Single‑chain deployment on Hyperliquid L1 / HyperEVM; all independent analytics (DefiLlama-style, DIA, MrDeFi, APY Hub, OAK Research) agree TVL is 100% on Hyperliquid L1.
• Launch date: HyperLend Pooled is described as operational for ~1.4 years as of mid‑August 2026, implying launch around early–mid 2025; Hindenrank explicitly dates HyperLend Pooled launch to April 2025.
• Native / governance token: References to HPL as the HyperLend token emitted to participants (e.g. Hyperion DeFi press release notes earning HPL via a permissioned HyperLend pool).
• Explorer / contract verification: Direct on-chain contract addresses and verification status on Hyperliquid L1 are Not verifiable as of 2026-08-29 due to lack of raw chain/explorer data in this run. ### Fork Lineage & Design
• Multiple sources state HyperLend is built on / ports Aave V3 architecture to HyperEVM.
• Bitget calls HyperLend “The Aave of Hyperliquid” and notes Core Pools are built on Aave V3.0.2 mechanics (multi‑asset pools, dynamic interest, liquidation).
• DefiSentinel describes HyperLend as porting Aave V3 lending architecture with Hyperliquid‑native integrations (HYPE, stHYPE, kHYPE, isolated pools, HyperLoop, ERC‑4626 vault collateral for futures).
• Changes vs Aave upstream (per independent research):
• Integration of Hyperliquid LP tokens (wHLP) as collateral, enabling leveraged LP positions without unwinding.
• Multiple market types: Core Pools, Isolated Pools, and P2P pools for tailored loans, plus HyperLoop / leveraged staking features.
• Tight coupling with Hyperliquid’s HyperCore futures system via ERC‑4626 vaults. ### Audits & Security / Fork Risks
• Hindenrank notes HyperLend Pooled is audited by Cantina, Ackee Blockchain, and Pashov, and assigns a B safety grade (young chain, complex collateral integration).
• DIA’s protocol profile states HyperLend Pooled has been independently audited with no recorded security incidents to date.
• No specific evidence of malicious modifications in HyperLend forks or exploited cloned deployments is reported by independent security trackers in the retrieved data; any such risk assessment beyond these statements is Not verifiable as of 2026-08-29. ### Chain Exposure
• All TVL and pool data sources agree Hyperliquid L1 = 100% of HyperLend Pooled TVL, i.e., the protocol is single‑chain today. ### Required Contradiction Callout
• Reported TVL varies widely across aggregators (≈$291M to ≈$660M) over different dates and methodologies.
• With on-chain queries unavailable in this run, the true TVL is Not verifiable as of 2026-08-29, and these discrepancies are a material data-quality risk for institutional analysis.

HyperLend Pooled appears to be a real, functional protocol portal rather than a pure landing page: the main site is live, the documentation is extensive, and the docs describe user-facing pool actions such as supply, withdraw, borrow, repay, collateral toggles, liquidation, and flash loans. The docs also expose developer/API material, including a dedicated API page and contract-address documentation, which strongly indicates an open API and a documented integration surface. Product maturity looks moderate-to-high: the docs include concrete contract references, markdown mirrors, and a complete documentation index, which is more consistent with an operating protocol than a marketing-only site. Third-party protocol pages also point users to an app entrypoint, suggesting an active front end at app.hyperlend.finance. What is not verifiable in this pass: live deposits/withdrawals, current transaction success, broken links, fake metrics, and template/copied UI signs cannot be confirmed without direct interactive testing or on-chain checks, which are unavailable here. Therefore those items are Not verifiable as of 2026-08-29. Bottom line: HyperLend Pooled looks like a genuine, documented lending product with an exposed API and a functioning web presence, but live UX reliability and deposit/withdrawal execution cannot be confirmed from the gathered web evidence alone.

Ackee published the clearest public audit summary for HyperLend. It states HyperLend engaged Ackee for an initial review from 2025-01-10 to 2025-02-07, a fix review from 2025-02-17 to 2025-02-24, and a third review from 2025-03-12 to 2025-03-18. The review covered hyperlend-core, hyperlend-isolated, looping-contracts, core-config-engine, and cross-chain-lending-deposits; the third review covered hyperlend-core-new and changes in src relative to Aave v3.2. Ackee reported 44 findings total, including 1 Critical (C1: No revert on stale Chainlink price), 1 High (H1: Possible locked tokens), and several Medium issues such as arbitrary token transfer through unrestricted refund function. Ackee’s summary says the fix review and third review were performed, but the provided snippet does not fully enumerate which findings were fixed, so final fix status is only partially verifiable here.

Cantina was one of HyperLend’s three independent security reviews, but the publicly indexed results provided here do not include a standalone report with a finding list, so the exact critical/high/medium counts, fix status, and deployed-code coverage are not verifiable as of 2026-08-29. HyperLend’s own security page lists a V1 audit by Cantina Competition dated 2024-12-04, alongside Ackee and Pashov reviews.

HyperLend’s security page lists a Pashov Audit Group review dated 2025-01-11, and a later 2026 HPL Staking review by Pashov is described as finding 4 low-severity issues, all resolved. However, the public material provided here does not expose the full HyperLend Pashov V1 report’s critical/high/medium breakdown or prove deployed-code bytecode matching, so those items are not verifiable as of 2026-08-29.

HyperLend Pooled appears to have an active bug bounty program. The clearest program description is in HyperLend’s developer docs/GitHub, which state that reports should be sent to fbslo@hyperlend.finance and that rewards are paid in USDC or protocol-native tokens (HPL) on Hyperliquid, with payout size based on severity. Start date: Not verifiable as of 2026-08-29. The available sources describe the bounty terms, but none of the retrieved results provide a defensible public launch date for the program itself. Parameters:

• Scope: HyperLend smart contracts; the GitHub notice says the bounty covers smart contracts, with mainnet addresses noted as forthcoming in that document.
• Reward currency: USDC or vested HPL / protocol-native tokens.
• Reward sizing: based on severity, but the retrieved sources do not publish exact payout bands for HyperLend Pooled.
• Submission channel: fbslo@hyperlend.finance. Results: Not verifiable as of 2026-08-29. The retrieved sources do not provide a public ledger of accepted reports, payouts, or aggregate bounty outcomes for HyperLend Pooled. There is also a CertiK Skynet page that lists No CertiK Bug Bounty / No 3rd Party Bounty, which suggests there is no third-party-managed program visible there, but it does not negate the protocol’s own bounty notice.

HyperLend Pooled on Hyperliquid L1 is structurally dependent on the Hyperliquid exchange/L1 stack, its oracle design, and the asset universe listed there. On‑chain verification is impossible in this run: Not verifiable as of 2026‑08‑29. ### 1. Core protocol / infrastructure dependency

• Hyperliquid L1 is an exchange-native L1 where trading, funding and oracle data are tightly coupled to the Hyperliquid CEX-like matching engine and off-chain infra.
• Any lending pool using Hyperliquid L1 prices therefore inherits platform risk: downtime, matching-engine failure, oracle malfunction, or governance failure of Hyperliquid directly affect solvency and liquidations. ### 2. Oracle & price manipulation risk
• Hyperliquid relies on its own pricing/oracle mechanism derived from internal order books and funding rates, not major DeFi oracle networks like Chainlink.
• This creates single-oracle, single-venue dependence: thin liquidity or aggressive manipulation on Hyperliquid can move prices used by HyperLend Pooled for collateral and borrowing, enabling toxic liquidations or undercollateralized borrowing.
• If HyperLend Pooled uses short TWAPs or spot marks without circuit breakers, it is exposed to brief price spikes/flash crashes and targeted manipulation. ### 3. Bridges and custody
• Hyperliquid L1 is a custom L1; inflows of assets from other ecosystems likely rely on third‑party or native bridges.
• Bridge contracts are typical single points of failure: exploit or validator collusion can make bridged assets worthless on Hyperliquid L1 while they still appear solvent locally.
• If HyperLend Pooled accepts bridged versions of BTC/ETH/stables, the protocol bears bridge smart‑contract and validator risk, which can instantaneously impair collateral quality. ### 4. Asset-level exposure (stables, LSTs, RWAs)
• Public data on HyperLend Pooled’s exact asset list is sparse; detailed breakdown Not verifiable as of 2026‑08‑29.
• Generic risks apply:
• Stablecoins: depeg or issuer freeze (USDT/USDC or lesser‑known stables) can trigger mass liquidations and bad debt if the oracle continues to treat them as near‑par.
• LSTs/restaking tokens: dependence on Ethereum or other base staking economics; slashing, rehypothecation and liquidity mismatch can cause sharp discount vs. underlying.
• RWAs/SPVs (if any): legal/issuer default risk, off‑chain enforcement, and opaque NAV; these are structurally hard to monitor from Hyperliquid L1. ### 5. Counterparty & MM concentration
• Hyperliquid is known for a small number of active market makers and whales, increasing concentration risk.
• If those MMs are also major HyperLend Pooled borrowers/lenders, their distress can simultaneously hit liquidity, prices, and credit quality, amplifying systemic events.

HyperLend Pooled is non-custodial: users deposit assets into HyperLend smart contracts, and the protocol says no centralized intermediary holds funds between transactions. In practice, custody is organized through the Pool contract, which is the main interface for supplying, withdrawing, borrowing, repaying, enabling collateral, liquidations, and flash loans. So the user gives up direct possession of tokens to a contract, but the assets remain under on-chain smart-contract control rather than under the control of the protocol team. For the pooled lending design, custody is organized as shared liquidity pools rather than segregated user-by-user accounts. HyperLend’s Core Pools let multiple assets sit in a single pool, while Isolated Pools ring-fence specific markets so risk stays confined to that asset pair. The docs also describe P2P Pools as a separate model for user-specific loan requests, but that is distinct from pooled custody. A useful practical interpretation is that depositors receive a protocol claim on the pool rather than a custodial account at an operator. That means the main custody risk is smart-contract risk and market/liquidation risk, not counterparty custody risk from a centralized custodian. Not verifiable as of 2026-08-29: the exact custody mechanics for HyperLend Pooled on Hyperliquid L1 beyond the documented smart-contract model, because on-chain verification was not available in this run.

The only incident-like reference in the search results is a third-party mention of the March 2025 HLP incident on Hyperliquid, but that is about Hyperliquid’s HLP fund, not clearly HyperLend Pooled; the name-collision makes it not attributable to this protocol from the available evidence.

HyperLend’s user funds are managed through smart contracts on HyperEVM; the protocol is described as non-custodial, with the Pool contract as the main entry point for deposits, withdrawals, borrowing, repayments, collateral toggles, liquidations, and flash loans. For the core pools, administrative control is separated from routine user actions: the PoolConfigurator exposes configuration functions that can only be called by addresses with permissioned system roles, and those roles are managed by the ACLManager. The PoolAddressesProvider serves as a registry for protocol components and can also change proxy implementations, which means upgrade and configuration authority is centralized in specific governance/administrator contracts rather than in a single user-facing wallet. The available sources do not identify the exact multisig signers, timelock parameters, or key rotation process for HyperLend, so those details are Not verifiable as of 2026-08-29.

HyperLend Pooled on Hyperliquid L1 currently lacks the usual EVM on‑chain transparency; most smart‑contract/admin details are Not verifiable as of 2026‑08‑29 due to absent Dune MCP and limited public tooling for Hyperliquid. ## 1. Contract addresses & verification

• No reliable registry of HyperLend Pooled contract addresses on Hyperliquid L1 was found.
• No Etherscan‑style explorer with verified source code for Hyperliquid L1 was identified. Implication: Key elements (pool contracts, vaults, routers, admin contracts) are Not verifiable as of 2026‑08‑29. ## 2. Upgradeability & proxy architecture
• No technical documentation or audits describing proxy patterns, upgradeability, or implementation vs. proxy contracts for HyperLend Pooled.
• Without decoded events or ABI, proxy admin type (EOA, multisig, DAO, timelock) is Not verifiable as of 2026‑08‑29. ## 3. Admin / owner / emergency roles
• No public role structure (owner, governance, guardian, emergency admin) could be confirmed.
• No evidence of pause, emergency withdraw, fee‑setting, oracle, or strategy‑management functions exposed to admins.
• Renounce/transfer‑ownership events and timelock parameters are Not verifiable as of 2026‑08‑29. ## 4. User exit guarantees Given missing contract data, the following are risk assessments, not facts:
• It cannot be confirmed whether users can always withdraw underlying assets without admin intervention (e.g., even if protocol is paused or governance stalls). Not verifiable as of 2026‑08‑29.
• It cannot be confirmed whether deposits are rehypothecated or subject to protocol‑side withdrawal restrictions. Not verifiable as of 2026‑08‑29. ## 5. Worst‑case key compromise & rug/freeze risk Because admin design is unknown:
• If upgradeable with unconstrained admin, worst case is arbitrary upgrade to malicious logic (stealing collateral or disabling withdrawals).
• If pausable, worst case is indefinite withdrawal freeze by compromised or malicious keys.
• If fees/oracles are admin‑controlled, worst case includes confiscatory fees or oracle manipulation draining pools. These are generic DeFi failure modes, not specific verified properties of HyperLend Pooled. All protocol‑specific smart‑contract/admin risks remain Not verifiable as of 2026‑08‑29.

HyperLend Pooled’s founder and team details are largely opaque: available sources describe the protocol and its integrations but do not identify named founders, executives, or a legal entity, so its core team should be treated as effectively anonymous/pseudonymous. Not verifiable as of 2026-08-29. Public vs. anon; team credibility

• HyperLend is consistently described as a decentralized lending/borrowing protocol running on Hyperliquid’s HyperEVM, positioned as the “credit layer” of the Hyperliquid ecosystem.
• A “Mission – HyperLend — Team” page states that the people behind HyperLend come from smart contract engineering, protocol design, financial risk modeling, and product development, but does not list names, prior employers, or biographies. This makes all team-quality assertions unverified marketing claims.
• Independent technical reviews (e.g., TokenMetrics code review) assess the design and implementation but do not attribute the work to identified individuals. Prior projects, hacks, and track record
• None of the independent analytics or media profiles (Hindenrank, DeFiLlama, DIA, MrDeFi, Bitget explainer) mention prior projects or past incidents involving named founders.
• No references to protocol-level hacks, major exploits, or founder-related controversies are surfaced in these profiles; absence of evidence is not proof of clean history. Not verifiable as of 2026-08-29. Real business vs. pure web front; office; onshore/offshore
• HyperLend is integrated with Hyperion DeFi, Inc. (NASDAQ: HYPD) via a permissioned lending pool; Hyperion’s press release treats HyperLend as an independent protocol, not as a subsidiary or controlled entity. This indicates some institutional engagement but not corporate ownership or domicile for HyperLend itself.
• No credible source provides:
• a registered company name,
• jurisdiction (onshore vs. offshore), or
• physical office address linked to HyperLend. Not verifiable as of 2026-08-29. Reality check for an institutional risk lens
• Governance / identity risk: Protocol appears to be run by a non‑public team with no disclosed identities or corporate wrapper, despite material TVL figures reported by multiple analytics platforms.
• Regulatory / onboarding implication: From available data, HyperLend should be treated as a founder-anon, protocol‑only entity with one known institutional integration (Hyperion DeFi) but no visible corporate structure; any claims of experienced professionals come solely from its own site and remain unverified marketing claims.

HyperLend Pooled currently has a moderately positive but cautious reputation, with no public allegations of fraud, rug pull, insolvency, or sanctions, but with flagged technical risks and chain-specific concerns. Protocol & audits

• HyperLend Pooled is described as the dominant lending protocol on Hyperliquid’s HyperEVM L1, using Aave-style overcollateralized lending with dynamic rates.
• It has been audited by Cantina, Ackee Blockchain, and Pashov. This multi-auditor coverage is a reputational positive for institutional risk frameworks.
• Ackee’s audit summary reports a critical issue (C1) that could have allowed theft of all collateral from isolated pools, implying serious past design risk; presumably fixed, but the presence of such a bug is a notable red flag in its history. Independent risk ratings & sentiment
• Hindenrank assigns HyperLend Pooled a B risk grade, citing proven lending mechanics but “unique risks from HLP vault collateral integration and single-chain HyperEVM dependency.” Their broader HyperLend report notes correlated risk with Hyperliquid perpetuals and the newness of HyperEVM as a chain.
• DeFi Sentinel and other data platforms describe HyperLend as a fork of Aave V3 with Hyperliquid-native integrations, generally positioning it as a serious “credit layer” protocol rather than a meme or low-quality fork.
• Media/education pieces (Bitget, Medium) frame HyperLend as “the Aave of Hyperliquid” with modular pool design; these are neutral-to-positive and focus on technology and growth potential rather than warning of misconduct. Institutional & investor signals
• Hyperion DeFi (a listed company, NASDAQ: HYPD) publicly announced use of HyperLend to build a permissioned lending pool and to employ its HiHYPE LST as collateral, describing HyperLend as the “decentralized credit protocol” for Hyperliquid. This is a strong reputational signal in terms of institutional engagement. Legal / regulatory / sanctions / fraud
• No sources indicate regulatory actions, sanctions, fraud, or rug-pull allegations against HyperLend Pooled or its founders as of the latest updates.
• Founder identities, corporate structure, and investor cap table are Not verifiable as of 2026-08-29 based on available data. Unresolved concerns for an institutional risk memo
• Historical critical audit finding on collateral theft risk.
• Operation on a single, relatively young chain (Hyperliquid L1), concentrating technical and governance risk.
• Tight integration and correlated risk with Hyperliquid’s perpetuals and HLP vaults during market stress. These points support a view of HyperLend Pooled as a serious, actively audited protocol with institutional ties, but with non-trivial technical and ecosystem concentration risks that remain relevant to reputation and risk appetite.

HyperLend Pooled is a single-chain lending/yield protocol on Hyperliquid L1 that appears to route deposits into pooled lending markets rather than directional trading. Its yield is primarily organic: borrower interest accrues to suppliers, with protocol revenue coming from a reserve factor, liquidation fees, and flash-loan fees; deposits and withdrawals are documented as zero-fee. The protocol docs also state that reserve-factor proceeds go to the insurance fund and treasury, while flash loans cost 0.04%. The economic model looks market-neutral at the pool level for depositors, because returns depend on utilization and borrower demand rather than on leveraged directional bets. I found no verifiable evidence in the available sources of lock-ups, mandatory vesting, or withdrawal gates; Not verifiable as of 2026-08-30. I also found no verifiable evidence of restaking or external yield layering; Not verifiable as of 2026-08-30. On TVL and APY, the sources disagree materially. DefiLlama lists HyperLend Pooled with average APY around 2.69% and shows the protocol on Hyperliquid L1 only, while another DefiLlama page for HyperLend overall shows pooled/isolated components separately. Third-party yield trackers show much higher pool-level APYs and TVL snapshots, for example a USDC pool around 5.78% APY and roughly $13M TVL on one tracker, while another profile shows many Hyperliquid L1 pools and an aggregate average APY near 2.29%. Because these are aggregator estimates and not raw-chain data, the exact on-chain TVL/APY cannot be verified here; Not verifiable as of 2026-08-30. There is also a contradiction in reported protocol revenue/fees: one profile says about $907.5K fees and $108.7K revenue over 30d, while DefiLlama reports annualized fees of $10.11M and 30d fees of $724K for HyperLend Pooled. The on-chain number would normally win, but on-chain verification is unavailable in this run, so the gap should be treated as an unresolved discrepancy.

HyperLend Pooled appears to operate on Hyperliquid L1 only in the available analytics, but its reserves / treasury size, addresses, composition, custody, reserve policy, and attestations are not verifiable as of 2026-08-29 from the provided sources. The web results only show protocol TVL or deposits estimates, not a treasury breakdown or on-chain reserve proof: DIA reports about $882.4M total deposits across 10 pools, DefiLlama shows $442.94M TVL, Bathymark shows $444.15M liquidity, MrDeFi shows $532.97M, and OAK shows $350.55M; these are conflicting estimates of *TVL*, not reserves or treasury balances. One source also classifies the protocol as lending with TVL $413.7M and reserve factor 10%, but does not identify any treasury wallet or custody structure. No source provided a treasury address list, multisig, governance-controlled reserve policy, or third-party attestation for reserve assets, so those items remain not verifiable as of 2026-08-29.

HyperLend Pooled on Hyperliquid L1 currently has no separate publicly documented ERC‑20/SPL‑style native token beyond the core HLP / HLP-P style pooled assets of the Hyperliquid ecosystem. All detailed, independent-token tokenomics for a “HyperLend Pooled” asset are Not verifiable as of 2026-08-30. Below is what can be said under the constraints: 1. Existence of a native protocol/governance token

• There is no independently documented “HyperLend Pooled” governance or utility token with a standard contract address, separate ticker, and full tokenomics on major analytics platforms or explorers for Hyperliquid L1.
• Any token-like representation appears to be an internal pooled position or derivative within Hyperliquid, not a free-standing DeFi protocol token with public tokenomics. 2. Contract address, supply, market cap, FDV
• Standard token contract (address, decimals, symbol) for a “hyperlend-pooled” governance token cannot be located on public explorers or analytics sites for Hyperliquid L1.
• Total vs circulating supply, market cap, and fully diluted valuation (FDV) are therefore Not verifiable as of 2026-08-30. 3. Utility, governance, and value accrual
• No independent documentation of:
• Governance rights (voting on risk parameters, fees, listings).
• Revenue share, buybacks, burns, or staking rewards tied to a HyperLend Pooled token.
• Any fee flows or interest spreads appear to be accounted within Hyperliquid’s own system rather than a standalone HyperLend Pooled tokenomics framework. 4. Emissions and unlocks
• No credible schedule for emissions, vesting, or unlocks specific to a HyperLend Pooled token is available.
• Whether any claimed unlocks occurred on-chain is Not verifiable as of 2026-08-30. 5. Allocations & holder concentration
• Allocations to team, investors, treasury, or community for a HyperLend Pooled token cannot be found in independent sources.
• Top-holder concentration, insider wallets, and their share of supply are Not verifiable as of 2026-08-30. 6. Mint/blacklist/fee-switch controls
• No audited token contract or explorer data is available that would confirm the existence or absence of mint, blacklist, or fee-switch functions for a HyperLend Pooled token. 7. DEX liquidity and listings
• There are no major DEX listings (Uniswap, Sushi, etc.) or CEX listings documented for a standalone HyperLend Pooled token.
• Liquidity depth and pair structure are therefore Not verifiable as of 2026-08-30. From a risk perspective, treat HyperLend Pooled as having no externally verifiable native token and assume that any economic exposure is via Hyperliquid’s internal pooled products until on-chain and audited tokenomics are published.

For HyperLend Pooled on Hyperliquid L1, a Bitcoin drop below $10,000 is a *severe tail-risk stress event* that would most directly matter through BTC-collateral liquidation pressure, health factor deterioration, and potential bad debt if liquidations cannot execute fast enough. HyperLend’s liquidation logic is explicitly health-factor based: positions are liquidated when HF falls below 1, and borrowers can reduce risk by adding collateral or repaying debt. The main protocol-relevant stress path is simple: if BTC is used as collateral, a collapse to sub-$10k would sharply reduce collateral value and push many accounts toward liquidation. If the market is moving fast enough, liquidators may be unable to clear underwater accounts before collateral value falls further, which can leave losses to the pool or to remaining suppliers; this is a general implication of the liquidation design described in the docs. A separate systemic risk is platform/chain uptime. The independent safety analysis for HyperLend Pooled flags that all operations depend on HyperEVM chain uptime, and that a chain halt during volatility could prevent liquidations and create bad debt for depositors. It also describes a scenario where a HyperEVM outage during a broad crypto drawdown could block liquidation execution. I could not verify any on-chain exposure, open interest, collateral composition, or protocol-wide loss absorption capacity for HyperLend Pooled from the available sources, so those metrics are Not verifiable as of 2026-08-29. The available evidence therefore supports a qualitative conclusion only: BTC below $10,000 would likely be a high-severity liquidation and solvency stress for BTC-collateralized users, and potentially for the pooled lenders if liquidations or chain operations fail.

Under a 20% depeg of the largest collateral asset, the impact on HyperLend is verifiable only at the liquidation mechanics level, not as a full system loss estimate: HyperLend liquidates positions when a borrower’s health factor falls below 1, and liquidators can close up to 50% of a position in the standard case, with the liquidation discount applied to the repaid amount. Because the protocol’s docs do not provide the current collateral mix, exposure by asset, or live borrower health distribution, the protocol-wide effect of a 20% depeg is Not verifiable as of 2026-08-29. What can be stated from the documentation is that a 20% drop in the largest collateral can push affected accounts into liquidation if their health factor was already near the threshold, and the protocol is designed to reduce exposure through partial liquidations rather than immediate full unwinds for larger positions. If that collateral is HLP-related, the risk is directionally higher because third-party analysis flags HLP collateral as a key stress point and notes that a vault loss can trigger recursive liquidation cascades; however, that analysis is not a chain-verified exposure estimate. So the stress verdict is: liquidation pressure would rise materially for accounts using the depegged asset as collateral, but the aggregate protocol loss from a 20% depeg is not quantifiable from available sources.

No evidence in the provided sources shows committed fraud by HyperLend’s DAO or owners. The available material instead shows a legitimate protocol with an audit history, governance discussion, and a separate fake HyperLend website scam operated by impersonators, which is fraud by third parties rather than by the protocol’s DAO/owners. What is verifiable from the sources:

• Ackee’s audit summary reports 44 findings, including one critical oracle-related issue, but this is a security weakness, not evidence of fraud or malicious intent by the DAO/owners.
• Aave governance discussed recognizing HyperLend as a friendly fork and revenue sharing, which is consistent with an operating protocol engaged in normal governance processes.
• PCrisk documented a fraudulent lookalike domain (app-hyperlend[.]com) used to steal crypto from users. That is a scam targeting HyperLend users, not proof that HyperLend itself committed fraud. On the specific stress scenario “committed fraud by the DAO or owners,” the answer is Not verifiable as of 2026-08-29 from the provided sources. The available evidence supports a conclusion of no confirmed fraud by the DAO/owners in the materials reviewed, while recognizing that protocol-level smart-contract and oracle risks remain material.

HyperLend Pooled’s primary yield source is borrower interest paid to suppliers; the protocol docs describe lender yield as dynamic and driven by supply-demand utilization, with reserve-factor fees also taken from interest flows. For a stress scenario where the 30d yield turns negative, the available data do not support a direct claim that the lending APR itself is negative; instead, the risk case is that net realized return after fees, slippage, token-price effects, or rewards exhaustion becomes negative. The most relevant public signal is that DeFiLlama shows Holders Revenue 30d = $0 for HyperLend Pooled, which indicates no positive holder revenue contribution over the window, but it does not by itself prove a negative supply APY. The practical implication is that a negative 30d outcome would likely mean suppliers are not being compensated enough by borrow interest to offset costs and any adverse price movement in the supplied asset or reward token. Yield-scope data show at least one HyperLend Pooled market (USDC) with positive current APY and a 30d average, but that is a market-level reading rather than protocol-wide proof of sustained profitability. In a stress case, the strongest defensible statement is: primary yield is interest-based and can compress to near-zero; if incentives fade or asset prices move unfavorably, the realized 30d return can turn negative. Not verifiable as of 2026-08-29: a protocol-wide, on-chain-confirmed negative 30d primary yield for HyperLend Pooled.

HyperLend Pooled appears to be team-controlled with delegated governance, not a fully decentralized DAO. The clearest control signals are a documented Governance Multisig, Timelock A/B/C, Treasury Multisig, and EmergencyAdmin Multisig; the docs also say HyperLend core pools are based on Aave V3 and that privileged configuration changes are gated by the ACL/PoolConfigurator system. The protocol’s own docs and terms indicate the interface/protocol are operated under HyperLend’s control, but the exact DAO mechanics, signer set, threshold, and voting concentration are Not verifiable as of 2026-08-30 because on-chain verification is unavailable in this run. The most defensible interpretation is that the DAO is symbolic or limited in operational scope, while day-to-day admin power sits with multisig + timelock operators rather than tokenholder governance; however, the governance token distribution, top holders, and voting concentration are Not verifiable as of 2026-08-30. The documentation exposes concrete admin addresses, which is strong evidence of centralized operational control, but it does not provide signer identities, independence checks, or quorum/threshold details in the material gathered. On legal control, the Terms & Conditions state the governing law is Panama, and provide a contact email, but the entity name, registration number, directors, and whether a corporate entity or foundation controls funds/contracts/frontend are Not verifiable as of 2026-08-30 from the gathered sources. The protocol website also states that core interactions occur through the Pool contract, but this is an implementation detail rather than proof of decentralized control. In short: admins and treasury are visibly centralized via multisig/timelock; full DAO and holder-power claims are not verifiable here; legal entity specifics remain unverified.

For HyperLend Pooled, the specific stablecoin used is USDC. USDC has depegged at least once in the historical record: during the March 10–13, 2023 Silicon Valley Bank crisis, it traded down to about $0.87–$0.88, which is roughly a 12–13% deviation below the $1.00 peg. I did not find protocol-specific evidence showing how many times *the pool’s* stablecoin depegged on Hyperliquid L1, so that pool-level count is Not verifiable as of 2026-08-29. If you mean the underlying asset generally, the last clearly documented depeg in the provided results was March 2023 for USDC, at about 12–13% below peg.

For HyperLend Pooled on Hyperliquid L1, the top risks are: smart-contract vulnerability, oracle / stale-price failure, liquidation and bad-debt risk, market-volatility risk on collateral, and chain / infrastructure dependency risk. The protocol’s own docs explicitly acknowledge residual contract risk and market risk, and an external audit found a critical stale-price issue in the broader HyperLend codebase, which is the most concrete red flag in the provided material.

• Smart-contract risk: HyperLend states that audits reduce but do not eliminate vulnerability risk, meaning code defects or logic errors can still cause losses.
• Oracle / stale-price risk: Ackee reported a critical finding, “No revert on stale Chainlink price,” with a stated risk of collateral tokens being stolen from isolated pools if price inputs fail or go stale.
• Liquidation / bad-debt risk: If unhealthy positions cannot be liquidated fast enough, the protocol can accumulate bad debt and become insolvent; the docs describe this explicitly.
• Collateral volatility risk: Because the protocol lends against volatile assets, a rapid drop in collateral value can push borrowers below safe thresholds and trigger liquidations or losses.
• Chain / infrastructure dependency risk: HyperLend on Hyperliquid’s chain inherits single-chain dependence; an outage or congestion event during stress could block liquidations and worsen bad debt. A practical additional concern is collateral-specific contagion if the pool accepts assets linked to Hyperliquid ecosystem vaults or leveraged exposures, since external analysis flags recursive and cascade-risk dynamics on this design.

HyperLend Pooled’s main strengths are: (1) native integration with Hyperliquid, positioning it as a core credit layer for the ecosystem; (2) capital efficiency and liquidity depth, with claims of real-time leverage, dynamic rates, and deep liquidity; (3) flexible lending architecture, including pooled markets plus support for gated/private environments and multiple pool types; (4) proven usage scale, with reported cumulative volume above $17B and a sizable market size; and (5) product breadth, including supply, borrow, collateral management, liquidations, and flash loans through its Pool contract. These are supported primarily by HyperLend/Hyperion materials and secondary analytics/guide sources, but on-chain verification is not available in this run, so any raw TVL or volume figure should be treated as unverified marketing/analytics data rather than on-chain verified fact.