Data terms

Hyperliquid Data Dictionary

Choose a metric to understand its meaning and limits.

Product boundary
Live market data is context, not a trading signal. Verify the current venue state, order book, fees, funding, and risk limits before acting.

Related tools

Last updated: 2026-09-05Last reviewed: 2026-08-26
Risk notice
Crypto perpetuals and leveraged trading are high risk. You can lose money through liquidation, funding, slippage, oracle issues, protocol failures, and market volatility.

Sources

25 references · Expand
  • Supports: Core and HIP-3 perpetual DEX discovery, current market contexts including rolling dayNtlVlm, perpetual metadata, funding history, predicted funding, DEX and market limits, DEX status, configuration metadata, clearinghouse state, and open-interest cap fields.
  • Supports: HIP-3 builder-deployed perp mechanics, deployer responsibilities, 500,000 HYPE staking requirement, minimum stake duration, deployment rules, configurable fees, settlement, oracle duties, slashing risk, cross margin, and backstop liquidation.
  • Supports: Public info endpoint families used for market, book, candle, account, portfolio, native borrow/lend reserve, vaultDetails, userFees account-rate, and maxBuilderFee approval reads.
  • Supports: The pre-alpha status of portfolio margin, eligible quote-asset supplying and borrowing, utilization definition, hourly interest indexing, the documented pre-alpha stablecoin rate model, protocol interest buffer, LTV context, and liquidation mechanics.
  • Supports: Perpetual contract units, USDC margining, margin fractions, funding versus expiration, and order value limits.
  • Supports: Maintenance margin, mark price, partial liquidations, liquidation flow, backstop-liquidation thresholds, and HLP liquidator-vault exposure.
  • Hyperliquid Docs: FundingAccessed 2026-09-04
    Supports: Hourly funding, funding formula, interest-rate component, premium component, funding payment formula, and the direction of payments when funding is positive or negative.
  • Hyperliquid Docs: FeesAccessed 2026-08-26
    Supports: Rolling 14-day volume tiers, perps and spot fee schedules, HIP-3 deployer fee scale and growth mode, strict HYPE staking-tier thresholds and discounts, referral fee formula and limits, staking-account linking risks, fee-model caveats, fee distribution to HLP, the assistance fund, and deployers, the assistance fund system address, and burn recognition of assistance-fund HYPE.
  • Hyperliquid Docs: WebSocketAccessed 2026-08-25
    Supports: The official mainnet WebSocket endpoint, subscription messages, and reconnect guidance for live public-data clients.
  • Supports: The trades subscription and its coin, side, price, size, timestamp, and trade-ID fields.
  • Supports: Public leaderboard address rows, account-value fields, and day, week, month, and all-time PnL, ROI, and volume windows used for position-cohort selection and full-feed PnL extremes. Current positions come separately from clearinghouseState.
  • Supports: Public spot token and pair metadata, rolling dayNtlVlm market contexts, outcomeMeta request and response fields, asset-context price and supply fields, tokenDetails maximum-supply definitions, and spotClearinghouseState balances.
  • Supports: The manager's own description of its flagship strategy as market-neutral, cross-market arbitrage. It does not prove the purpose of any individual position.
  • Supports: Third-party attribution of two public Hyperliquid addresses and reported ETH withdrawals from Binance. Flow observations do not prove current balance, continuing control, hedge purpose, or complete net delta.
  • Supports: Third-party entity clustering used only as corroborating wallet-attribution evidence.
  • Supports: Primary validator endpoint discovery for timestamped validator rows and unavailable-state handling.
  • Supports: Current REST request-weight, WebSocket, and user-limit constraints for public-data tooling.
  • Supports: Documented third-party chain-indexed endpoints for current TWAP programs, including indexed parent size, side, duration, market asset ID, and schedule time used for transparent scheduled-pace calculations; plus recent transfers, deployments, auctions, fee observations, spot USDC observations, aliases, and public search.
  • Supports: HIP-4 outcome-market mechanics, deployment requirements, collateralization, settlement, identifiers, and risk framing.
  • Hyperliquid Docs: Asset IDsAccessed 2026-08-26
    Supports: Official outcome-side asset-id encoding used to map Yes and No side assets to public price and order-book endpoints.
  • Supports: Hyperliquid outcome metadata endpoint shape and technical interpretation boundaries.
  • Supports: Official public HyperCore transaction lookup by transaction hash for read-only explorer detail pages.