Hyperliquid HLP

Hyperliquid HLP is the liquidity provider vault for the Hyperliquid perpetuals exchange on the proprietary Hyperliquid L1 chain. Identification

• Name: Hyperliquid HLP (Hyperliquid Liquidity Pool)
• Website / App: app.hyperliquid.xyz (HLP section accessible via Earn → HLP)
• Docs: Hyperliquid “HLP” and “Liquidity” documentation pages (linked from app and main docs hub)
• Category: Perpetual DEX liquidity pool / LP vault (provides collateral and counterparty liquidity for perp traders; users earn funding + fees and take directional risk vs traders).
• Chains: Runs on the Hyperliquid L1 custom chain; not deployed on Ethereum, L2s, or other main public chains.
• Native token: The vault issues an HLP share token representing proportional claim on the pool; the broader Hyperliquid ecosystem uses HYPE as its governance/points token, but HLP itself is a vault token, not a standard ERC‑20 on Ethereum.
• Launch date: Public HLP pool was introduced with the mainnet perpetuals launch in late 2023; exact block-time for initial deployment is Not verifiable as of 2026‑09‑04 due to lack of independent chain explorer with historical contract timestamps. Main contract addresses & verification status Hyperliquid runs on its own L1 with an integrated explorer; concrete contract addresses for the HLP vault and router are referenced only in internal docs/UI and not in independent explorers or Dune (Dune does not yet support Hyperliquid L1). Therefore:
• Precise HLP vault contract address: Not verifiable as of 2026‑09‑04 (no independent explorer + no Dune).
• Contract verification status: Not verifiable as of 2026‑09‑04; available only via Hyperliquid’s own tooling, which counts as “unverified marketing claim” for risk analysis. Fork lineage & code provenance
• Hyperliquid positions itself as a custom chain and matching engine, not a direct fork of GMX, dYdX, Perpetual Protocol, or other major perp DEXs; external analyses describe it as a “bespoke high‑performance perp exchange on its own L1,” not an Ethereum/L2 fork.
• No credible independent source identifies HLP as a direct fork of a specific upstream DeFi protocol (e.g., GMX GLP). Not verifiable as of 2026‑09‑04 whether any backend components reuse upstream open‑source code.
• Audits: Hyperliquid security reviews and audits (where mentioned) cover the exchange and chain broadly, but there is no publicly available, auditor-hosted report specifically detailing HLP contract diffs vs an upstream fork. Not verifiable as of 2026‑09‑04.
• Malicious‑modification history in similar forks: For HLP itself, no documented incidents or exploit history are reported by independent security trackers; generalized GLP/LP‑style vault exploits on other platforms do not directly implicate HLP. Not verifiable as of 2026‑09‑04 beyond absence of reported incidents in major media/security databases.

Hyperliquid HLP appears to be a real, functional product portal rather than a static landing page: the official docs describe live deposit and withdrawal flows through the Hyperliquid web app and public API, including vault deposits/withdrawals and bridge-based USDC movement. The documentation also exposes a public API surface for programmatic access, so yes, it does have an open API. Product maturity looks reasonably high for a DeFi app: the app supports deposits, withdrawals, vault pages, and developer endpoints, with documented settlement times and lockups (HLP 4 days; withdrawals processed by the protocol/bridge flow).

A separate implementation guide notes a public stats endpoint powering the web UI, which suggests the portal is not just marketing copy but backed by live data services. What is not verifiable from the available evidence is the presence of broken links, fake metrics, or template signs on the site itself: those require live page inspection and were not confirmed here. Not verifiable as of 2026-09-04. ## Bottom line

• Real portal: yes, with documented app workflows and vault operations.
• Live deposits/withdrawals: yes, documented in official materials and third-party API guides.
• Open API: yes, public API endpoints are documented.
• Broken links / fake metrics / template signs: Not verifiable as of 2026-09-04.

Hyperliquid’s bug bounty program is active and covers mainnet bugs that would cause an outage or logical error on nodes or API servers; experimental testnet features are generally out of scope unless separately announced. Reports must include detailed reproduction steps and a proof of concept, and must be sent to bugbounty@hyperfoundation.org. Rewards are paid in USDC on Hyperliquid and are severity-based, with published tiers including High under 50,000 USDC for network downtime without incorrect state and Medium under 10,000 USDC for API server performance issues.

Public coverage in February 2025 described the program as newly launched alongside HyperEVM, with reward ranges from under 10,000 USDC up to nearly 1 million USDC for the most severe issues. I did not find a reliable public record of actual payout results or disclosed bounty awards, so those results are not verifiable as of 2026-09-04.

As of September 6, 2026, no active dependency outage is indicated: Hyperliquid’s status page reports Hyperliquid L1, frontend, and API operational after a September 5 scheduled upgrade. Primary dependency / counterparty: HLP is economically dependent on the Hyperliquid L1 and its perpetual/spot venue. It market-makes, supplies USDC in Earn, and acts as the backstop liquidator; losses are borne by vault depositors. This creates single-venue, shared-risk exposure to the exchange’s matching, margin, liquidation, validator, and withdrawal systems. Oracle and manipulation risk — material and demonstrated: Mark prices incorporate external venue prices and Hyperliquid market data.

Thinly traded assets can therefore be manipulated externally and transmit losses to HLP through forced liquidation. The March 26, 2025 JELLY incident led to emergency validator intervention and demonstrated that governance can override normal settlement; later filings also report an approximately $4.9 million HLP loss tied to a November 2025 POPCAT manipulation and a temporary bridge/withdrawal halt. These are realized historical events, not merely theoretical scenarios. Bridge / custody: The documented bridge operates on Arbitrum and currently supports USDC.

Withdrawals depend on validator signatures, dispute periods, and bridge controls; a bridge pause or validator/bridge compromise could delay or block access. HLP itself is not described as relying on an external custodian, but deposited capital remains exposed to Hyperliquid’s platform controls and validator governance. CEX/MM and asset exposure: External exchanges and market makers are relevant indirectly through oracle pricing and liquidity conditions. USDC is the principal documented quote/deposit asset; USDC depeg, issuer freeze, or banking/insolvency stress could impair HLP NAV and withdrawals.

No verified RWA issuer/SPV, LST, or restaking dependency was identified. Exposure measurement: On-chain HLP asset, venue, stablecoin, and bridge exposure percentages are Not verifiable as of September 6, 2026 because Dune MCP is unavailable. Historical incident loss percentages versus current HLP TVL are likewise Not verifiable as of September 6, 2026.

HLP custody is organized as a pooled protocol vault on Hyperliquid: users deposit USDC into the vault, and the vault uses that capital for market making, liquidations, and fee/PnL accrual rather than keeping assets segregated per depositor. Hyperliquid’s vault docs say the HLP deposit lock-up period is 4 days, and third-party explainers describe withdrawals as redeeming vault shares at current NAV after that lockup, which means custody is pooled and pro rata once deposited. For the related fields: withdrawal_paused is not verifiable as of 2026-09-06, and segregated_assets is false because the available evidence describes pooled vault custody rather than segregated depositor assets.

2023-08-08: YGG volatility created >50% oracle/mark-price divergence, causing unfair short liquidations and HLP/Liquidator imbalances. Affected: YGG short traders and HLP/Liquidator users. Response: compensation for affected short maintenance margins and net vault losses; insurance-fund process formalized.

Loss amount: Not verifiable as of September 6, 2026. Users were compensated. Status: resolved.

2023-08-22: FRIEND-USD’s TVL-based oracle was shown to be manipulable through artificial subject creation and atomic purchases, creating a potential liquidation exploit. Affected: FRIEND traders and the protocol’s oracle/liquidation system. Response: oracle switched to a median of top subjects without advance notice; maintenance-margin refunds were issued during the transition.

No realized protocol loss was reported. Status: resolved; oracle design changed.

2023-11-14: During YGG volatility, liquidation transfer from the Liquidator vault to HLP produced uneven P&L: approximately $160,000 loss for the Liquidator vault versus approximately $200,000 HLP gain. Affected: early vault depositors. Response: voluntary Assurance Fund compensation; Liquidator-vault design was retired/integrated into HLP. Status: resolved.

2023-12-09: A user accidentally submitted a market order in the wrong BTC denomination, suffering excessive slippage. Affected: the individual trader. Response: Assurance Fund refund of $15,400; maximum-notional limits were added for future orders. Status: resolved.

2024-03-01: Record trading volume caused severe network/API congestion, mark-price volatility, and unusual liquidations affecting users and HLP operations. Response: ticket review and Assurance Fund compensation; scaling, consensus, and mark-price improvements were initiated. Realized loss and total compensation: Not verifiable as of September 6, 2026. Status: resolved.

2024-06-21: ZRO-USD used an erroneous mark price, producing incorrect negative P&L for short holders. Response: automatic Assurance Fund refunds based on pre-error position value plus a 2% buffer. Loss amount and total refunds: Not verifiable as of September 6, 2026. Status: resolved; affected traders were compensated.

March 12, 2025: a trader used an oversized, highly leveraged ETH long and withdrew collateral, leaving HLP to absorb the liquidation deficit. Affected: HLP vault depositors/liquidity providers; no evidence of unauthorized protocol access. Response/fix: Hyperliquid reduced maximum leverage to 40x for BTC and 25x for ETH.

No user reimbursement was reported. Current status: resolved, with parameter remediation implemented. Attacker proceeds were reported at approximately $1.8M.

Market manipulation / oracle-usage attack on the JELLYJELLY perpetual that put the HLP vault at risk but was reversed by governance.

• Date: 2025‑03‑18 to 2025‑03‑26 (attack and response window).
• Cause: Economic design/oracle usage issue – attacker opened a very large short on JELLYJELLY, then pushed the token price up off‑platform, making the short deeply underwater and leaving HLP on the hook when the position would be liquidated.
• Loss / bad debt: Contemporary reporting highlights ~$12–13.5m of unrealized HLP losses / bad debt risk rather than a crystallized loss; the vault’s $230m was at risk but not ultimately lost.
• Affected: HLP vault depositors (USDC liquidity providers).
• Protocol response: Hyperliquid validators executed an oracle override, ignoring the manipulated JELLY oracle and force‑closing the attacker’s position at a price that removed the bad debt and produced a ~$700k gain for HLP.
• Recovered_usd: ~$0 net loss; HLP reportedly realized a ~$700k gain when the position was closed.
• Reimbursement: No user reimbursement was required since HLP depositors did not suffer a net loss; instead, the attacker’s expected gain was confiscated.
• Current status: resolved at the protocol level, but underlying design risk (HLP inheriting large, illiquid positions) remains per later risk analyses. Important caveat: Multiple later sources describe additional 2025–2026 HLP loss events (e.g., POPCAT manipulation with ~$4.9–5m HLP loss, a series of illiquid‑token liquidation attacks, and a broader pattern of design‑driven vault drawdowns), but I cannot re‑query primary sources or on‑chain data in this turn to independently verify precise per‑incident loss, recovery, or reimbursement figures. Where exact user‑level reimbursement outcomes are not explicitly documented in independent coverage, they are Not verifiable as of 2026‑09‑03 and are therefore omitted here rather than inferred.

March 26, 2025: coordinated JELLYJELLY trading manipulated the market and transferred a large short position to HLP. Affected: HLP depositors and JELLY market participants. Validators delisted JELLY and settled positions at $0.0095 rather than the manipulated market price; innocent long users were refunded, while flagged addresses were excluded.

The realized HLP loss was approximately $4M; the approximately $12M figure was an unrealized exposure avoided by the intervention. Current status: resolved, although the underlying liquidation-design risk remains. Attacker proceeds: Not verifiable as of September 5, 2026.

2025-07-29: API servers congested during a traffic spike, causing roughly 37 minutes of order delays and confusing error responses while transactions still reached the mempool. Affected: traders unable to execute or close positions normally. Response: automated refunds and API-infrastructure improvements; blockchain consensus and HyperEVM were unaffected.

CONTRADICTION: public refund estimates range from approximately $1.49M to $1.99M; the official incident page does not disclose a final total. Status: resolved; users were reimbursed.

November 12, 2025: a coordinated POPCAT long-and-spoofing strategy was liquidated after the buy wall was removed, leaving HLP with the position as POPCAT fell further. Affected: HLP depositors. Response: deposits/withdrawals were temporarily paused and Hyperliquid manually closed the inherited position; the Arbitrum bridge was also temporarily halted.

No reimbursement was reported. Current status: resolved operationally; broader structural remediation is not verifiable as of September 5, 2026. Attacker proceeds and recovery are not verifiable as of September 5, 2026.

April 9, 2026: a highly leveraged FARTCOIN long collapsed, triggering liquidations and auto-deleveraging. Affected: traders with opposing positions and potentially HLP as liquidation backstop. HLP’s realized loss, recovery, reimbursement, and any permanent fix are Not verifiable as of September 5, 2026. The incident was operationally resolved after positions were closed.

No additional incident after the September 5, 2026 check was verified in the September 6, 2026 search window. For previously recorded ETH, JELLYJELLY, POPCAT, and FARTCOIN events, no newer independent evidence was found changing the previously recorded loss, reimbursement, or status conclusions. Structural remediation beyond the documented parameter changes remains Not verifiable as of September 6, 2026.

Hyperliquid HLP’s key management is not described publicly as a separate vault-key or multisig framework in the sources I found. The available documentation instead shows that HLP is a protocol-managed vault on Hyperliquid’s L1, with actions executed inside the chain’s trading engine, and users access it through Hyperliquid’s delegated-signing / agent-wallet model for their own accounts. For user-side access, Hyperliquid’s security guide says the app uses delegated signing through agent wallets: when a user establishes a connection, Hyperliquid creates an agent wallet in the browser.

A technical library write-up also states that Hyperliquid trading actions are authorized by ECDSA signatures from the user’s private key, and that the private key is stored client-side and never transmitted over the network. For HLP itself, the docs and third-party explainers describe it as a protocol-owned / protocol-managed liquidity vault that runs market-making and liquidation strategies, but they do not spell out any public key-rotation, multisig, or DAO-based signer structure for vault operations. Because of that, the exact internal custody and signer arrangement for HLP vault control is Not verifiable as of 2026-09-04 from the sources available here.

The practical takeaway is that Hyperliquid appears to organize key management as user-held keys plus agent wallets for delegated app interaction, while HLP’s operational control is abstracted into the protocol’s own execution layer rather than exposed as a public key-management design.

Assessment as of September 6, 2026 Address / architecture. Hyperliquid HLP is a native HyperCore vault on Hyperliquid L1, not a conventional EVM Solidity contract. The official API identifies HLP as 0xdfc24b077bc1425ad1dea75bcb6f8158e10df303, with leader 0x677d831aef5328190852e24f13c46cac05f984e7; its relationship includes strategy accounts 0x010461…703a, 0x31ca…f974b, and 0x2e3d…8dd14. ``text Depositor wallet │ deposit / withdraw (4-day HLP lockup) ▼ HLP native vault: 0xdfc24…f303 │ vault accounting / equity / withdrawal rules ▼ Leader: 0x677d…984e │ trading authority ├─ Strategy A: 0x010461…703a ├─ Strategy B: 0x31ca…f974b └─ Liquidator: 0x2e3d…8dd14 ▼ HyperCore order book, margin, liquidation and oracle systems `` Verification and admin controls. No EVM bytecode, ABI, proxy, implementation, proxy-admin, owner, timelock, pause, fee, oracle, or upgrade events were identified for the HLP native vault. Dune/on-chain verification is unavailable in this run.

Therefore: Not verifiable as of September 6, 2026. The native vault model exposes deposits, withdrawals, leader trading, and automatic position reduction, but does not establish that withdrawals cannot be blocked by protocol-level authority. HLP withdrawals are documented after four days; users have a direct withdrawal path, subject to margin/position handling. Key compromise / loss scenarios. A compromised leader or strategy key could trade HLP into severe losses, including liquidation; this is economically equivalent to strategy failure, not proven direct asset drainage.

A compromised Hyperliquid validator/protocol control plane could potentially affect execution, oracle inputs, withdrawals, or availability; exact permissions and recovery controls are Not verifiable as of September 6, 2026. Hyperliquid itself identifies L1 downtime and validator-operated oracle manipulation as risks. Change from prior finding: native HLP and strategy addresses are now documented, but standard contract verification and admin analysis remain unavailable. Architecture conclusion: high transparency gap; material strategy, oracle, validator, and withdrawal-freeze risk; no evidence sufficient to classify HLP as an upgradeable proxy or admin-drainable contract.

Zellic — Hyperliquid Smart Contract Patch Review, published November 27, 2023. This follow-up reviewed only specified changes to Bridge2.sol and Signature.sol on Arbitrum, not HLP vault contracts or Hyperliquid L1 consensus. The report states the reviewed code was not deployed to Arbitrum Mainnet at assessment time.

Zellic — Hyperliquid Smart Contract Security Assessment, published August 14, 2023. This is not an HLP-vault or Hyperliquid L1 audit: it assessed Solidity contracts Bridge2 and Signature at commit 43b5267c on Arbitrum. The report states the assessed code was not deployed to Arbitrum Mainnet at assessment time; bytecode match to current deployed code is Not verifiable as of September 6, 2026.

One source states that Trail of Bits conducted additional security assessments covering Hyperliquid’s HyperBFT consensus and critical infrastructure components, implying an infrastructure‑level review rather than a pure smart‑contract audit.

Hyperliquid bridge / L1 staking-related smart contracts audit. Scope in the report: Hyperliquid contracts repository at commit 43b5267c58778e5e24640c9abac06cb608d63c40, covering Bridge2 and Signature programs on Solidity / Arbitrum. The publicly indexed report states the audited code was not deployed to Arbitrum Mainnet at the time of the audit, so deployed-code coverage via bytecode match is not verifiable from the gathered sources.

Hyperliquid HLP is built and operated by Hyperliquid Labs, a very small, highly technical team centered around its public founder and CEO Jeff(rey) Yan and a pseudonymous co‑founder iliensinc. Founders & background

• Jeff Yan (public, doxxed) – Harvard graduate in mathematics/computer science and former high‑frequency trading quant at Hudson River Trading. He later ran a proprietary trading firm, Chameleon Trading, whose profits reportedly bootstrapped Hyperliquid’s development with no venture capital funding.
• iliensinc (pseudonymous, co‑founder) – described as Jeff’s Harvard classmate and a joint architect of Hyperliquid’s technical and operational design; remains pseudonymous and keeps a low public profile. Team composition & prior track record
• Core team size is consistently reported as ~10–11 people, roughly half engineers and half non‑engineering.
• Team members are said to have prior experience at Hudson River Trading, Citadel, Caltech, MIT, and other elite quantitative/technical institutions.
• Multiple independent profiles claim Hyperliquid generated >$900m profit in 2025 with this 11‑person organization and processes multi‑billion daily derivatives volume, positioning it among the highest revenue‑per‑employee businesses globally.
• The protocol and its L1 were launched in 2023, after design work beginning in late 2022. Public vs. anonymous; office, jurisdiction, and corporate reality
• Only Jeff Yan is fully public; other contributors mostly use pseudonyms, with iliensinc explicitly identified as pseudonymous.
• Media and interview pieces refer to “Hyperliquid Labs” rather than a clearly domiciled operating company; they do not consistently state a registered jurisdiction or physical office location. This is Not verifiable as of 2026-09-04.
• Articles emphasize that the project is self‑funded, no VC, no token allocation to venture funds, lean headcount, and product‑led growth, which is repeatedly framed as a deliberate design choice. Credibility and risk reality check
• Credibility positives: public, technically credentialed founder with HF‑trading background; multi‑year operating history; large reported volumes and revenues; extensive coverage in major outlets (Fortune, Forbes, Colossus, WuBlockchain, etc.).
• Structural risk flags for institutions: largely pseudonymous team beyond the founder; opaque legal entity structure and jurisdiction; no clear disclosure of office or regulatory status; heavy reliance on a very small group (key‑person and operational risk). No prior hacks or catastrophic failures associated with Hyperliquid or its founders were identified in the retrieved material; absence of evidence is not proof of absence, so this remains Not verifiable as of 2026-09-04.

Hyperliquid and its HLP-related ecosystem currently carry elevated reputational and regulatory risk, driven by ecosystem-level rug pulls, criticism of governance decisions, and mounting regulatory scrutiny, rather than any direct fraud finding against the core protocol. 1. Ecosystem fraud/rug allegations (indirect, but material)

• A yield protocol HyperVault / HypervaultFi built on Hyperliquid reportedly executed a rug pull of about $3.6m, withdrawing user funds, bridging to Ethereum and sending 752 ETH to Tornado Cash, with developers disappearing and social channels wiped. This is widely framed as one of the largest rug pulls on the Hyperliquid network to date.
• Coverage stresses that HyperVault was not the core Hyperliquid exchange, but a third‑party high‑yield vault on its chain; community messaging tries to separate this from protocol risk.
• These events nonetheless raise concerns about ecosystem due diligence and security culture around yield products like HLP that may rely on composability with other apps. 2. Governance and “soft rug” criticisms
• Hyperliquid has faced criticism for delisting the $JELLY token, described by one analysis as effectively performing a “rug pull” via governance after realizing the protocol “couldn’t afford to lose.”
• The same critique notes the protocol “pulled the plug” under pressure from centralized exchanges like Binance, raising questions about decentralization, policy independence, and fairness to listed projects.
• Separate reporting describes Trove Markets investors accusing the project of a rug pull when it abruptly migrated from being Hyperliquid‑native to Solana, with complaints of misleading marketing and token dumping. Again, this is ecosystem, not core protocol, but adds to sentiment risk. 3. Regulatory and sanctions-related concerns
• CME Group and ICE are actively lobbying the CFTC and US Congress to impose tighter oversight on Hyperliquid, arguing its KYC‑free, pseudonymous perpetuals venue could facilitate market manipulation, insider trading, and sanctions evasion, particularly in oil markets.
• Reporting indicates no formal US enforcement action yet, but highlights Hyperliquid as a key target of traditional exchanges’ regulatory campaign.
• The UK FCA has issued a warning listing Hyperliquid and Hyper Foundation as unauthorized firms that may be providing or promoting financial services in the UK without permission, explicitly advising consumers to avoid dealing with them. 4. Founders / investors / auditors
• Public coverage focuses on the platform’s structure and markets; founders, cap table, and formal smart‑contract auditors for HLP are Not verifiable as of 2026-09-04. 5. Overall sentiment for institutional risk
• Market narratives emphasize Hyperliquid as a fast‑growing, unregulated, KYC‑free on‑chain derivatives venue, attractive for liquidity but viewed by major incumbents and at least one regulator as a market‑integrity and sanctions‑risk hotspot.
• Combined with the documented HyperVault rug and governance controversies, institutional perception should treat HLP exposure as high reputational and regulatory‑policy risk, even in the absence of direct fraud findings against the core protocol.

Economic model (reviewed September 6, 2026)

• Strategy / assets in: HLP is a Hyperliquid L1 protocol vault accepting primarily USDC. It actively market-makes, performs backstop liquidations, supplies USDC to Earn, and receives a share of trading fees. Returns therefore combine spread/inventory PnL, liquidation outcomes, Earn yield, and fee share—not fixed lending interest.
• Directional profile: Market-making is intended to provide liquidity, but it is not risk-free or demonstrably delta-neutral: inventory, adverse selection, liquidation positions, volatility, and trader flow can create directional exposure. No external-chain, restaking, or recursive looping exposure is identified in the official description.
• Yield quality: No separate incentive emissions were reported for the broader Hyperliquid protocol by DeFiLlama; HLP’s modeled fees derive from trading activity. However, the organic share of depositor yield cannot be decomposed from available data: Not verifiable as of September 6, 2026.
• Lock-up / withdrawals: Withdrawals are permitted four days after the most recent deposit; subsequent deposits reset the lock. Exact minimums, withdrawal fees, capacity limits, and emergency gates: Not verifiable as of September 6, 2026.
• TVL / trend: DeFiLlama reports $189.39m, entirely on Hyperliquid L1 (100%), down 12.3% over 30 days. HLP fees were $557,118 over 30 days, with reported HLP protocol revenue of $0 because the modeled fee flow is attributed to depositors. Dune comparison, block-height as-of data, and product-level decomposition: Not verifiable as of September 6, 2026.
• APY history / sustainability: A reliable historical APY series, volatility, drawdown, and sustainable forward yield are Not verifiable as of September 6, 2026. Treat returns as variable trading PnL, not promised APY. Contradiction / correction: Prior notes called HLP “protocol-owned.” Current official documentation describes it as a fully community-owned protocol vault; the latter wording is used here.

As of September 6, 2026, HLP’s reserve position is only partially verifiable. Hyperliquid describes HLP as a fully community-owned protocol vault used for market making, backstop liquidations, USDC lending/“Earn,” and fee accrual; deposits have a four-day lock-up. This describes vault mechanics, not a reserve policy or audited balance sheet.

A third-party tracker reports approximately $190.0M TVL as of September 5, 2026, with leader address shown only as 0x677d...84e7. TVL is an analytics estimate of vault equity, not proof of liquid reserves, and does not disclose asset composition, open-position liabilities, or withdrawal liquidity. The full HLP vault address, wallet-level balances, component-vault balances, and current composition are Not verifiable as of September 6, 2026.

Dune MCP was unavailable for this run; therefore on-chain balances, transfers, positions, control relationships, and latest-block reserve composition are Not verifiable as of September 6, 2026. No independent reserve attestation or liability statement for the native HLP vault was identified. The Yieldfi “Hyperliquid-HLP” proof-of-reserves PDF is a separate Ethereum-based asset and cannot be matched to native Hyperliquid HLP; it is excluded from the reserve figure. Contradiction / correction: The previously recorded 0xCBF400...E43d7b “Treasury Multisig” comes from HyperLend’s contract-address page and is not evidence of HLP custody or control.

It should not be attributed to Hyperliquid HLP absent an address-level linkage. Reserve policy: no independently documented minimum-reserve, segregation, or liquidity-buffer policy found. Attestations: none identified for native HLP.

Control: protocol documentation says community-owned; operational leader is displayed only in abbreviated form, and multisig threshold/signers are Not verifiable as of September 6, 2026.

Scope correction: HLP (Hyperliquidity Provider) is a Hyperliquid protocol vault, not a separately issued token protocol. It is community-owned, accepts deposits, provides market-making/liquidation liquidity, accrues part of trading fees, and has a four-day withdrawal lock. Therefore, HLP has no native token, ticker, token contract, supply, market cap, FDV, emissions, unlocks, allocations, or token-holder governance.

Related ecosystem asset — HYPE (not an HLP token): HYPE is Hyperliquid L1’s native asset. It is a native coin rather than an ERC-20 contract; the canonical HyperEVM wrapped version is WHYPE: 0x5555555555555555555555555555555555555555. HYPE is used for HyperEVM gas, delegated validator staking, staking-based trading-fee discounts, collateral, and ecosystem incentives.

Validators receive staking rewards; HLP depositors instead earn vault PnL, not HYPE staking rewards. HYPE’s published allocation is approximately: 31% genesis/community distribution; 38.9% future community emissions; 23.8% core contributors; 6% Hyper Foundation budget; 0.3% community grants; ~0.012% HIP-2. Contributor vesting began November 29, 2025, but a complete official future unlock calendar is not publicly verified.

Whether each announced unlock occurred on-chain is therefore Not verifiable as of September 4, 2026 without Dune/raw-chain validation. > Contradiction: HYPE supply and valuation figures materially diverge by methodology. A reported official-interface snapshot showed ~298.6M circulating and ~998.97M total supply, while CoinGecko-based figures cited ~222.4M circulating; DefiLlama reported approximately $18.85B market cap and $80.97B FDV.

The discrepancy is unresolved; exact market cap/FDV is Not verifiable as of September 4, 2026. HYPE revenue capture is indirect: fees are directed to HLP, the Assistance Fund, and deployers; the Assistance Fund converts fees into HYPE and burns its HYPE balance. No HLP-specific buyback, burn, mint, blacklist, or fee-switch function exists.

Exact top-holder concentration, insider-wallet attribution, and DEX order-book depth are Not verifiable as of September 4, 2026. Reported HYPE listings include Hyperliquid spot plus Binance US, Gate.io, and KuCoin.

A Bitcoin move below $10,000 would be a severe stress event for Hyperliquid HLP because Hyperliquid liquidations are triggered by mark-price moves against leveraged positions, and the HLP / liquidator vault is the backstop that takes over positions when the order book cannot fully absorb them. In that regime, HLP would likely face a spike in forced long liquidations, higher slippage, and possible inventory imbalance as it absorbs and unwinds positions, but the exact loss to HLP is Not verifiable as of 2026-09-04 because no on-chain or independently verified HLP balance/exposure data was available in the provided results. The key protocol point is the liquidation waterfall: first the position is closed by market-order liquidation, then the liquidator vault/HLP can take over at a liquidation price, and only if those layers fail does ADL socialize the residual risk.

Reports describing prior crash behavior suggest Hyperliquid’s backstop mechanism can absorb very large forced-sale volumes off-book during panic, which implies the system is designed to handle stress better than a pure order-book venue, but this does not establish how much a BTC sub-$10k event would cost HLP specifically. What can be said with confidence is that this scenario would probably be an extreme downside test for HLP’s NAV, especially if the crash is fast and liquidity thins out; the main uncertainty is whether HLP’s accumulated inventory and hedging could keep up before additional liquidations arrive.

For a 20% depeg of the largest collateral, the incremental loss to Hyperliquid HLP depends on how much of HLP’s assets and exposure are actually concentrated in that collateral. That concentration is not verifiable as of 2026-09-04 from the provided sources, so the protocol-level impact cannot be quantified precisely here. What *is* supported is that Hyperliquid’s margin system uses eligible collateral values in liquidation and borrowing logic, and the protocol has previously tightened requirements to reduce systemic impact from large positions.

Hyperliquid also states that liquidations are handled through the HLP vault/backstop process, with insurance fund and ADL as further layers if losses exceed the primary liquidation path. The stress implication is therefore:

• If the depegged asset is only a small slice of HLP collateral, the effect is likely a localized NAV drawdown.
• If it is the dominant collateral and is used broadly in leveraged positions, a 20% drop can trigger liquidations, forced deleveraging, and potential bad debt propagation into HLP/insurance-fund layers.
• If collateral withdrawals or liquidations are large and rapid, the loss can be amplified by the backstop-unwind mechanism rather than remaining a simple mark-to-market haircut. Because no on-chain exposure data is available in this run, the correct risk statement is: the loss under a 20% depeg is not quantifiable here; the key risk is correlated liquidation and backstop absorption, not just the direct haircut. Not verifiable as of 2026-09-04.

For Hyperliquid HLP, the “top counterparty insolvent” stress is best framed as major trader/default on the Hyperliquid perpetuals/spot venue whose risk is indirectly borne by HLP LPs via funding/PnL flows. On‑chain verification is Not verifiable as of 2026-09-04. ### 1. Setup: who is the “counterparty”?

Hyperliquid is a central-limit-orderbook perpetuals exchange on its own L1, where HLP is the main liquidity pool that effectively takes the other side of trader positions and earns fees/funding. Traders interact with the exchange; HLP LPs are the economic counterparty to aggregate trader risk, mediated by the matching engine and risk engine. ### 2. Stress: major trader / cluster of traders insolvent Trigger

• Large directional traders incur losses that exceed their margin because of extreme move, oracle failure, or risk-engine breakdown. Expected loss path
• Normally, losses are limited by forced liquidation; margin + insurance-type mechanisms cover PnL.
• In insolvency, the system could experience:
• Negative account equity not fully covered.
• Socialized loss or clawback mechanisms if implemented (not clearly documented; therefore Not verifiable as of 2026-09-04).
• If risk controls fail, HLP pool value can drop via realized PnL and adverse funding. ### 3. Who absorbs the loss?
• Immediate economic absorber: HLP LPs, via reduction in pool NAV when trader PnL is mismanaged or not fully collateralized.
• If Hyperliquid has an insurance fund / backstop (community notes mention risk fund but details are sparse; unverified marketing claim as of 2026-09-04), it would absorb losses first; residual losses hit HLP.
• If losses exceed both, ultimate absorber is LP capital in HLP. ### 4. Compensation and protections
• LPs are compensated ex ante via trading fees, funding income, and diversified exposure across markets.
• There is no credible, independent evidence of:
• Formal off-chain guarantees.
• External insurance.
• Governance-controlled bailout fund. Hence, any promise of protection beyond risk/funding economics is an unverified marketing claim as of 2026-09-04. ### 5. Smart-contract / infrastructure impact path
• Hyperliquid runs on a custom L1; order-matching and risk logic are largely off-chain engine + on-chain settlement, not simple AMM contracts.
• Counterparty insolvency manifests as:
• Bad debt in risk engine → changed settlement amounts to HLP pool.
• Potential parameter changes (fee, leverage, liquidation rules) via governance/contracts to stabilize the system.
• Smart contracts themselves are unlikely to “break”; instead, state updates to HLP balances reflect realized system-wide loss, directly impacting LP claims on the pool. Contradiction check: we cannot match marketing statements (e.g., “robust risk engine prevents clawbacks”) to independent technical/audit evidence. Gap is a risk finding.

There is no verifiable evidence that the Hyperliquid HLP DAO or owners committed fraud in the sense of an intentional theft, rug pull, or fraudulent misappropriation of user funds. The strongest available reporting instead describes market-manipulation attacks against HLP and an official Hyperliquid response that “There was no protocol exploit or hack” and that “HLP is not a risk-free strategy.” For this stress scenario, the relevant risk is governance/operational discretion under stress, not proven fraud. In the JELLY incident, Hyperliquid validators reportedly delisted the market and force-settled positions to protect the vault, which some observers characterized as centralized intervention, but that is not the same as a confirmed fraudulent act.

The available sources are also consistent that HLP is community-owned rather than owned by a private operator, which further weakens a “owners stole funds” theory, though it does not eliminate governance risk. Assessment:

• Fraud by DAO/owners: Not verifiable as of 2026-09-04.
• Confirmed incident type: third-party manipulation / liquidation stress events targeting HLP.
• Key residual risk: governance can intervene quickly in extreme cases, which may create fairness, censorship, or rule-change risk for users.

Hyperliquid HLP’s primary yield engine is not a fixed coupon; it is a mix of market-making spread capture, trading-fee share, funding-related gains, and liquidation revenue, so if the main source turns negative over a 30-day window the vault’s net yield can turn negative as well. In a stress scenario with negative 30d primary yield, the practical interpretation is that the vault is paying out more in adverse funding / inventory losses than it is earning from its normal carry and fee streams. Neutral Trade explicitly notes that funding rates can turn negative and that positions are reduced when net yield no longer justifies the cost.

Third-party analyses also state that HLP returns are variable and can be negative, with drawdowns occurring when market-making positions move against the vault during volatility spikes. For risk assessment, the key point is that HLP is a residual-claim strategy: it tends to perform best when market activity is high and liquidations are orderly, but it can suffer during toxic-flow or sharp directional regimes when spread capture and fees are insufficient to offset losses. That means a negative 30d primary yield is a credible stress signal for NAV drawdown, not just lower APY.

I cannot verify the current 30d on-chain yield for HLP as of 2026-09-04 in this run, because on-chain verification is unavailable here. Not verifiable as of 2026-09-04.

Assessment — centralized operational control; limited but real validator governance. HLP is documented as a “fully community-owned” protocol vault, but this describes depositor ownership of PnL exposure—not control over strategy, upgrades, frontend, or protocol funds. Deposits have a four-day withdrawal lock. Control map: Core development is led by Hyperliquid Labs; the Foundation supports governance/ecosystem functions. HYPE governance is validator-based: voting weight follows delegated stake, and protocol changes require validator approval.

Validators can also vote on jailing, slashing, and certain market/asset conditions. The documented process is HIP publication followed by validator voting; this is not a conventional token-holder DAO with proposals that automatically execute through a Governor/Timelock contract. DAO reality: Governance is substantive at the consensus/validator layer, but HLP depositors and ordinary HYPE holders do not appear to have direct, binding control over HLP strategy or upgrades. The validator set—and therefore voting power—may be materially influenced by Foundation/core-contributor holdings; public filings identify 23.8% of initial HYPE supply for core contributors and 6.0% for the Foundation. Contradiction: “Fully community-owned” HLP marketing is narrower than protocol-level control: community capital participates in vault PnL, while operational authority remains with strategy operators, Hyperliquid Labs/Foundation, and stake-weighted validators. Unverified / unavailable checks: Top HYPE holders, validator voting concentration, HLP fund-movement permissions, timelock implementation, multisig signers/threshold/independence, emergency bypasses, and whether an admin can drain HLP user funds: Not verifiable as of September 13, 2026.

Dune MCP was unavailable, and no reliable public source located in this review establishes these points. Hyperliquid Labs’ registration number, directors, and applicable frontend Terms of Service: Not verifiable as of September 13, 2026. A public filing describes the Hyper Foundation as Cayman Islands-registered but provides limited information on Hyperliquid Labs.

Hyperliquid is a centralized matching engine and custody layer on a custom Hyperliquid L1, offering perp trading and an HLP vault that provides liquidity. It looks economically like an exchange/broker running its own chain where users deposit assets and trade via an off‑chain engine, not a purely non‑custodial DeFi protocol. Entity & jurisdiction

• The app, docs and interface do not clearly state a registered corporate entity (no legal name, company number, or corporate address shown in ToS or footer).
• No independently verifiable registration data (e.g., SEC, Companies House, commercial registries) is visible in recent web results. Not verifiable as of 2026‑09‑04.
• Jurisdiction therefore cannot be reliably determined. Not verifiable as of 2026‑09‑04. Terms of service / user restrictions
• Interface shows blocking of U.S. users; public discussions and reviews describe Hyperliquid as “not available to U.S. persons” and other restricted jurisdictions, but the exact list and legal basis are not visible in a formal ToS page via public search.
• Without a clearly posted ToS, detailed contractual rights (dispute venue, governing law, liability caps) are not verifiable as of 2026‑09‑04. KYC / AML
• Users generally access via wallet; multiple sources describe no conventional KYC at sign‑up, which is typical of offshore crypto derivatives venues.
• Any internal AML controls, sanctions screening vendors, or policies are not publicly documented. Not verifiable as of 2026‑09‑04. Regulatory classification & risk Given it offers leveraged perpetual swaps with centralized custody and a proprietary matching engine, regulators could view it as:
• A crypto derivatives exchange or multilateral trading facility under securities/derivatives law.
• Potentially offering contracts referencing securities or large‑cap tokens that some regulators treat as securities, raising licensing and investor‑protection questions. Key practical risks for institutional users:
• Regulatory risk: venue may be unlicensed in major jurisdictions; sudden blocking of regions or users is possible.
• Legal recourse risk: unclear corporate entity and governing law make recovery in disputes difficult.
• Custody & segregation risk: assets held within Hyperliquid systems; bankruptcy, fraud or technical failure could be hard to pursue legally without a clear entity.
• Data protection: no public privacy policy or data‑processing disclosures found; Not verifiable as of 2026‑09‑04. Enforcement / sanctions / court cases
• No credible records of direct regulatory enforcement actions against Hyperliquid or a named Hyperliquid entity found. Not verifiable as of 2026‑09‑04.
• No listings on major sanctions lists or specific court cases identified. Not verifiable as of 2026‑09‑04.

No exact GLEIF LEI record for 'Hyperliquid HLP'. OFAC SDN screening of 'Hyperliquid HLP': no match. SEC litigation and administrative release feeds: no mention.

Hyperliquid HLP is a USDC-denominated vault and does not issue its own stablecoin, so own_stablecoin is false. I could not verify any historical depeg event for the stablecoin used by HLP from the available sources, so stable, depeg_count, max_depeg_pct, and last_depeg_date are Not verifiable as of 2026-09-06.

HLP is an actively managed protocol vault exposed to market-making inventory, liquidation backstop, oracle, and Hyperliquid L1 risks rather than a passive yield product. The JELLY incident demonstrates that thin-market manipulation can transfer toxic positions to HLP and may require validator intervention. Raw on-chain balances, exposures, and current loss-absorbing capacity are Not verifiable as of September 5, 2026 because Dune was unavailable in this run.

Top 5 strengths of Hyperliquid HLP are: (1) native protocol-backed liquidity, because HLP is the exchange’s own vault that provides market-making and liquidation backstop liquidity on Hyperliquid L1; (2) democratized access, because any user can deposit USDC into a strategy that was historically reserved for privileged market makers; (3) fee alignment, because the vault is described as passing PnL to depositors rather than charging a traditional active-manager style fee; (4) structural utility in stressed markets, because HLP is designed to absorb liquidations and support trading when market conditions worsen; and (5) transparent on-chain strategy exposure, because Hyperliquid’s on-chain design makes the vault’s role in perps, liquidations, and liquidity provision visible to users.