Community Docs
  • 🏠Home
  • Getting Started
  • Introduction
    • What is Hyperliquid?
    • Hyperliquid Labs
    • Roadmap
      • Incident
        • 2025-26-03
      • On-Chain Activity
  • Architecture
    • Overview
    • HyperBFT
      • Staking
      • Validator
      • API Servers
    • HyperCore
      • Dex
        • Clearinghouse
          • Margin Management
          • Liquidations
          • Funding
          • Fees
        • Order Book
        • Oracle
      • Vault
      • HIPs
        • Spot Deployments (HIP-1/HIP-2)
        • Perp Deployments (HIP-3)
      • Bridge
    • HyperEVM
    • Hyperliquid.
      • Unit
  • Guide
    • User Guide
      • Onboarding
      • Spot Deployments
      • Airdrop
    • Builder Guide
      • HyperCore
        • Trading Bot
        • Builder Codes
          • Install Template
          • Update
        • Endpoints
          • Info
            • Spot
            • Perpetuals
          • Exchange
      • HyperEVM
        • EVM Basics
          • dApp Setup
        • Specificities
      • Node Operators
      • Historical Data
  • Ecosystem
    • The Hyper Liquidated
      • Community Map
    • Projects
      • Tools
      • HyperEVM
        • Felix
      • HyperCore
      • MemeCoin
Powered by GitBook
On this page
  • Incident History
  • Platform Evolution
  1. Introduction
  2. Roadmap

Incident

PreviousRoadmapNext2025-26-03

Last updated 8 days ago

Hyperliquid maintains transparency about platform incidents and their resolution. When technical issues or system irregularities occur that impact users, the platform has established protocols to address affected parties fairly.

The Assurance Fund (previously called Insurance Fund) serves as Hyperliquid's primary mechanism for compensating users affected by platform-related incidents. This governance-controlled fund reimburses users when issues stem from technical problems, system congestion, or other platform-specific challenges rather than normal market conditions.

While Hyperliquid carries , the fund operates on the principle that users should not bear losses caused by platform malfunctions or design limitations during the protocol's development phase. For detailed information about how the fund operates, see the page and the for real-time risk metrics.


Incident History

  • Description: Attack on JELLY perps involving self-trading 4M USDC position at low price, then pumping spot price 400%+ to force HLP backstop liquidation of toxic short position, with potential coordination from major CEXs

  • Response: JELLY long traders refunded by Foundation at advantageous settlement price (0.037555). HLP Liquidator vault capped to small percentage of total balance, refined OI caps based on market cap, onchain validator voting for delistings implemented

  • Outcome: HLP significant losses contained, platform solvency maintained through enhanced risk management.

  • Description: Trader opened $271M ETH long position with 50x leverage using $6M collateral, then strategically withdrew funds to force liquidation while hedging short on external exchange, exploiting liquidation mechanics rather than technical vulnerabilities

  • Response: Max leverage reduced to 40x (BTC) and 25x (ETH). Additional 20% margin ratio requirement on margin transfers to directly address the withdrawal-based liquidation strategy

  • Outcome: $4M HLP loss (approximately one month's profit), no Assurance Fund compensation as system operated as designed - mechanism exploit rather than platform malfunction

  • Description: ZRO-USD hyperp settlement used erroneous mark price, causing incorrect negative P&L for short position holders

  • Response: Automatic refunds issued from Assurance Fund to all affected users, calculated as position value before erroneous update minus account value after update, plus 2% buffer to account for different valuation methodologies

  • Outcome: Complete compensation for impacted traders with conservative buffer applied

  • Description: Record $3B+ daily volume caused extreme network congestion during sharp price movement (17:26-17:32 UTC), preventing normal trading for users and HLP, leading to mark price volatility and unusual liquidations

  • Response: Individual ticket review process initiated, affected users compensated from Assurance Fund according to fair policy framework

  • Outcome: Platform scaling improvements implemented, consensus rewrite initiated, mark price formula enhanced for congestion resistance

  • Description: User accidentally placed >$6M market order in wrong denomination (BTC instead of USD), experiencing high slippage

  • Response: $15.4K refund from Assurance Fund, calculated by capping maximum slippage at 2%

  • Outcome: Maximum notional value limits implemented for future orders based on asset liquidity

  • Description: During YGG volatility period, profitable liquidation transfer from Liquidator vault to HLP caused uneven P&L distribution (Liquidator -160K, HLP +200K), affecting early vault depositors

  • Response: Platform operated as designed, but voluntary compensation provided for net losses through Assurance Fund to support unfamiliar users and early supporters

  • Outcome: HLP integrated liquidation functionality, Liquidator vault retired, user protection enhanced

  • Description: FRIEND-USD oracle vulnerability discovered by whitehats - TVL-based index was exploitable, allowing attackers to artificially inflate price by creating new subjects and buying shares atomically

  • Response: Immediate oracle change to median price of 20 top subjects without advance notice to prevent exploit, maintenance margin refunds provided for liquidations during 01:48-14:00 UTC transition period

  • Outcome: More secure oracle implementation, continued trading with isolated margin restrictions due to illiquid nature

  • Description: YGG extreme volatility caused 50%+ divergence between oracle and mark prices, affecting liquidation fairness despite platform operating as designed with oracle-based liquidations

  • Response: Compensation provided for YGG short maintenance margins liquidated during 12:00-16:00 UTC price divergence period, plus coverage for net Liquidator/HLP losses

  • Outcome: Mark price liquidation system evaluation initiated, insurance fund formalized with fee allocation structure


Platform Evolution

These incidents have driven continuous improvements to Hyperliquid's infrastructure, including enhanced network capacity, refined liquidation mechanisms, and stronger user protections. The Assurance Fund represents the platform's commitment to supporting users during the protocol's growth and development phases.

For current incident reports or compensation inquiries, users should open support tickets through official channels.

March 1, 2024
December 9, 2023
November 14, 2023
August 22, 2023
August 8, 2023
inherent risks
Risk Dashboard
March 26, 2025
Full incident analysis
March 12, 2025
implemented
June 21, 2024
Vault