知識圖書館

This documentation describes vaults built on HyperEVM using CoreWriter and precompiles. Builders can create and tokenize vaults with customizable accounting, and may follow standards such as ERC-4626. The described design supports onchain read and write…

The document explains manual borrowing of USDC or USDT against supplied HYPE or BTC collateral for supported Hyperliquid account types. Borrow capacity is calculated from collateral quantity, oracle price, and the asset's loan-to-value ratio, with…

The document explains how Hyperliquid handles leveraged positions when account equity falls below maintenance margin. It first attempts to close positions with market orders on the book, allowing full or partial fills; any remaining collateral stays with the…

This document explains how Hyperliquid builder codes let an application builder charge a fee on fills from orders submitted on a user's behalf. Users first authorize a maximum fee for a builder; the authorization must come from the user's main wallet and can…

HIP-2 describes an on-chain strategy for bootstrapping liquidity in newly deployed spot tokens quoted against USDC on Hyperliquid. A deployment specifies an initial price, order count and size, and how many levels begin as bids. Prices form a recursively…

The document explains how Hyperliquid derives robust reference prices for perpetual futures to reduce exposure to market manipulation. Its oracle price is a weighted median of centralized-exchange prices and is used to calculate funding rates; because…

HyperCore provides native multisig account control, allowing several existing users to authorize actions for one account. A user converts an account by specifying its authorized signers and the minimum number of signatures required. After conversion, actions…

This documentation explains that Hyperliquid index perpetual contracts use a calculated index as the underlying reference instead of a spot asset price. Validators periodically publish index values to the chain, and the median of their reports substitutes…

This literature review explains time-series and cross-sectional momentum strategies applied to equity anomaly factors. The time-series approach buys factors with positive trailing returns and shorts those with negative returns; the cross-sectional approach…

HyperEVM divides transaction throughput across two interleaved block types: small blocks produced frequently and larger blocks produced less often. This design separates confirmation speed from block capacity, aiming to let users benefit from faster…

This document explains the conditions for enabling a token as a spot quote asset on Hyperliquid. Requirements include specified token precision, no deployer fee share, a USD peg mechanism, and liquidity thresholds across the quote token’s USDC and HYPE…

This documentation explains how Hyperliquid's time-weighted average price order divides a total order into smaller submissions at intervals based on order size and duration. It gives examples of how a one-hour order and a multi-day order are divided, and…

Hyperliquidity Provider (HLP) is described as a community-owned protocol vault that supplies liquidity to Hyperliquid. It uses multiple market-making strategies, carries out liquidations, and supplies USDC to the platform’s Earn product. In return, the vault…

This technical reference describes how deployers configure and operate builder-deployed perpetual markets on Hyperliquid. It covers market and asset registration, oracle updates, funding parameters, margin tables and modes, fee settings, open-interest caps,…

The document explains the maximum drawdown figure shown on Hyperliquid’s portfolio page and clarifies that it is a convenience metric displayed by the frontend. It does not affect margin requirements or other platform calculations. To reproduce the displayed…

The document explains how delisting works for validator-operated perpetual contracts. Validators vote on whether an asset should be removed; if they approve delisting, the contract settles at the one-hour time-weighted spot oracle price from before the…

This document describes the API workflow for deploying HIP-1 and HIP-2 assets on Hyperliquid. The core process sends five actions in order: register the token specification, distribute initial balances and blacklist settings as needed, finalize genesis using…

This API reference describes actions available to deployers of builder-deployed perpetual markets. It covers registering a DEX and assets, updating oracle inputs, setting funding parameters and margin tables, configuring open-interest caps, assigning fee…

This reference describes Hyperliquid’s information endpoint for retrieving market and account data across perpetual and spot markets. It covers mid prices, order book snapshots, candles, open and historical orders, fills, order status, user portfolios, fees,…

This documentation explains how to send requests through Hyperliquid’s WebSocket API when those requests would normally use the HTTP API. It distinguishes informational requests from signed actions and describes a common wrapper with a method, request…

The document explains a specific pricing and margin arrangement for some Hyperliquid perpetual contracts. Their underlying spot reference comes from Uniswap V2 or V3 automated market maker prices. These contracts are isolated-margin only: traders cannot use…

The document explains why closing a perpetual futures position may increase Available Balance by less than the margin shown for that position. It focuses on cross margin, where open positions share a common pool of collateral. If other positions have losses…

The document explains why an action such as placing an order can fail with an expiration message: the exchange’s L1 has not accepted it within the stated 15-second window. This delay protection is intended to prevent an action from executing much later when…

This documentation explains how authorized deployers create and manage template-based outcome markets on Hyperliquid. Validators approve templates that define market wording, side names, and typed keywords; deployers instantiate those templates with…