| Document | Hyperliquid technical documentation (living documentation) |
|---|---|
| Author / maintainer | Official Hyperliquid documentation; no individual author is named on the linked overview |
| Publication date | No single publication year is stated for the current documentation |
| Project | Hyperliquid |
| License | Not stated on the linked documentation pages |
| Official source | Hyperliquid technical documentation |
This is an educational summary of Hyperliquid’s currently linked technical documentation, not a reproduction of a single dated whitepaper and not financial advice. Crypto Gloss does not claim authorship of the original material.
Hyperliquid is a Layer 1 blockchain built around two connected parts: HyperCore, which hosts the on-chain trading system, and HyperEVM, a general-purpose EVM environment. The official technical materials are maintained documentation rather than one fixed 2023 paper. This page summarizes the documentation as reviewed on 28 October 2026; protocol details and performance claims can change.
HyperCore: an on-chain order book
HyperCore contains spot and perpetual-futures markets. Its official documentation describes an order book for each asset, with orders matched by price and then time. Margin checks apply when an order is opened and when a resting order is matched. The project says order placement, cancellations, trades, and liquidations are reflected in HyperCore’s on-chain state. That design differs from systems that keep order matching off-chain and only settle selected results on a blockchain.
A central limit order book can offer familiar limit-order controls, but it does not guarantee a particular fill price or deep liquidity. Market depth, fees, funding payments, slippage, and the price used for margin and liquidation calculations still matter.
HyperBFT and validators
Hyperliquid describes HyperBFT as a custom consensus protocol inspired by HotStuff and later work. Validators secure the chain through delegated stake. The documentation reports about 200,000 orders per second for mainnet and, for a geographically co-located client, median end-to-end latency of 0.2 seconds and a 99th percentile of 0.9 seconds. These are project-reported figures, not independent benchmarks or a promise that every user will see the same performance.
Hyperliquid’s validator documentation says anyone can run a node, while the active validator set is selected by stake. Permissionless node operation therefore should not be confused with every node having equal consensus weight. How stake is distributed and how the validator set changes are relevant governance and security questions.
HyperEVM and connected applications
HyperEVM is documented as part of the Hyperliquid blockchain, using the same HyperBFT consensus rather than operating as a separate chain. Its purpose is to let EVM-style smart contracts interact with HyperCore liquidity and data. The official documentation currently labels HyperEVM as alpha and warns that some planned capabilities are not live. Treat roadmap language as a description of intended work, not proof that a feature is already available.
HYPE, HLP, and the old points program
HYPE is used for staking on HyperCore and as the gas token on HyperEVM. Hyperliquid’s documentation describes HLP (Hyperliquidity Provider) as a protocol vault that uses market-making strategies, participates in liquidations, supplies USDC in Earn, and accrues part of trading fees. Depositors share the vault’s profit and loss; the documentation lists a four-day withdrawal lock after a deposit. A vault is not a savings account, and returns or principal are not guaranteed.
The official points documentation records a program that began in November 2023 and ended in November 2024, with changing criteria across its phases. That history does not establish that a points campaign is currently active or that future rewards are promised. The current fee and staking rules should be checked in the live documentation before relying on them.
Trade-offs and risks
A specialized chain can devote its execution design to trading, but it also makes users depend on that chain’s consensus, software, validators, and connected bridge and application systems. On-chain order data improves public verifiability; it does not remove smart-contract, oracle, liquidity, or operational risk. Perpetual futures add leverage and funding risk, and positions can be liquidated when account equity falls below maintenance requirements. Hyperliquid’s current staking documentation describes a seven-day unstaking queue and says automatic slashing is not implemented. These details can change, so verify the live rules before depositing or trading.
In short, Hyperliquid’s distinguishing idea is to combine an on-chain order book with a purpose-built Layer 1 and an EVM environment. Its speed figures and project claims should be read alongside the stake-weighted validator model, liquidation mechanics, and the risks of leveraged trading.
Related Terms
See Also
- GMX: From GLP to GM Markets and GLV Vaults
- dYdX: A Standard for Decentralized Margin Trading and Derivatives
- Injective: An Interoperable Layer One for DeFi Applications
Sources
- Hyperliquid technical overview — Describes the L1 architecture, HyperBFT, HyperCore, HyperEVM, and the project’s current performance figures.
- HyperCore order-book documentation — Explains price-time priority, order types, and margin checks.
- HyperEVM documentation — Describes how HyperEVM shares HyperBFT with HyperCore and states its current rollout stage.
- Running a validator — Describes permissionless node operation and the stake-ranked active validator set.
- Staking documentation — Covers HYPE delegation, unstaking delays, validator rewards, and the current slashing design.
- Protocol vaults — Describes HLP’s functions, depositor profit-and-loss sharing, and withdrawal lock.
- Fee documentation — Explains fee routing, the assistance fund, and HYPE conversion and burns.
- Points documentation — Records the dates and phases of the historical points program.
- Liquidations documentation — Explains maintenance margin, liquidation handling, and backstop liquidations.
Last updated: 28 October 2026.