Hyperliquid primary-source snapshot
Fetched: 2026-04-26 UTC
1) About page / current framing
Source: https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid
Selected excerpts from the official docs:
Hyperliquid is a performant blockchain built with the vision of a fully onchain open financial system.
Liquidity, user applications, and trading activity synergize on a unified platform that will ultimately house all of finance.
Additional signals from the about page:
- Hyperliquid frames itself as a full financial-system chain, not merely a single exchange app
- The docs, not the marketing site, are the clearest primary source for what the protocol actually is
- The architecture and operational details live directly in the documentation set
2) Core architecture / HyperBFT + HyperCore + HyperEVM
Source: https://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/overview.md Source: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm.md Source: https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid.md?ask=What%20does%20Hyperliquid%20say%20its%20core%20architecture%20is%2C%20including%20HyperBFT%2C%20HyperCore%2C%20and%20HyperEVM%3F
Selected excerpts from official docs:
Hyperliquid is secured by HyperBFT, a variant of HotStuff consensus.
The Hyperliquid state is comprised of HyperCore and the general purpose HyperEVM.
HyperCore does not rely on the crutch of off-chain order books.
Additional signals from the architecture materials:
- Hyperliquid’s differentiator is that native trading state and EVM execution share one chain and one consensus/security model
- The docs explicitly say HyperEVM is not a separate chain, which matters for categorization
- This is strong evidence that Hyperliquid should be cataloged as both blockchain infrastructure and onchain trading infrastructure
3) Performance claims / latency and throughput
Source: https://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/overview.md
Selected excerpts from the docs:
For an order placed from a geographically co-located client, end-to-end latency has a median 0.2 seconds and 99th percentile 0.9 seconds.
Mainnet currently supports approximately 200k orders/sec.
Additional signals from the performance section:
- Performance claims are central to the project’s identity and help explain why it built a custom consensus and execution stack
- These claims should be treated as project claims, but they are still important primary-source signals about intended use and design tradeoffs
- The docs suggest Hyperliquid is optimizing for serious trading workloads, not generic app-chain positioning alone
4) HyperEVM / builder surface / gas model
Source: https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm.md
Selected excerpts from the docs:
The HyperEVM consists of EVM blocks built as part of Hyperliquid’s execution, inheriting all security from HyperBFT consensus.
HYPE is the native gas token on the HyperEVM.
There are currently no official frontend components of the EVM … All interaction with the EVM happens through the JSON-RPC.
Additional signals from the HyperEVM docs:
- Hyperliquid now has a meaningful general-purpose builder surface beyond trading-only usage
- The lack of official frontend components is itself useful context; developers are expected to interact through RPC and custom frontends
- Burning of both base fees and priority fees is a notable design detail relative to more typical EVM chains
5) Token utility / staking / fees / rewards
Selected excerpts from the documentation answer:
HYPE is the native token. It powers HyperEVM gas, and it can also be staked on HyperCore.
Validators need 10k HYPE self-delegation to stay active.
Fees go to the community: HLP, the assistance fund, and deployers.
Additional signals from the token/staking materials:
- HYPE is both utility token and stake-bearing security anchor within the chain’s operating model
- The docs tie together trading incentives, staking rewards, fee discounts, and ecosystem-level value flow
- This is important for understanding Hyperliquid as economic infrastructure, not just a UI for perps trading
6) Funding / genesis / no-VC positioning
Selected excerpts from the documentation answer:
Hyperliquid Labs is self-funded and has not taken any external capital.
development is fully self-funded, with no VCs or external capital.
Additional signals from the funding/genesis materials:
- Hyperliquid makes self-funding and no-external-capital positioning part of its official narrative
- The docs expose genesis mechanics through HIP standards and deployment flow rather than through a classic tokenomics PDF
- This is a good example of a project where living docs are more important than the absence of a canonical whitepaper
Notes
- This pass did not locate a single canonical Hyperliquid whitepaper.
- The strongest primary materials were the GitBook overview pages and the project’s own queryable documentation answers.
- Hyperliquid appears best categorized as a high-performance L1 with native onchain order-book trading infrastructure plus a same-chain EVM execution layer.