Hyperliquid is a blockchain and an exchange
Hyperliquid is a layer-one blockchain built around an onchain financial system. Its best-known application is an order-book exchange for perpetual futures and spot assets, but the chain also supports staking, vaults, permissionless market deployment and EVM smart contracts.
Calling it only a decentralized exchange misses part of the architecture. Hyperliquid is the network; HyperCore contains native financial primitives; app.hyperliquid.xyz is one interface; and HyperEVM is the general-purpose smart-contract environment.
HyperCore, HyperBFT and HyperEVM
HyperCore executes native order books, orders, cancellations, margin, liquidations and settlement. HyperBFT is the consensus system securing the state. HyperEVM runs EVM-compatible smart contracts under the same consensus rather than operating as an unrelated sidechain.
The distinction affects users and developers. Native exchange actions use HyperCore account state and APIs. EVM applications use chain ID 999, HYPE gas and JSON-RPC. A product can interact with both, but the transaction formats and failure modes differ.
| Layer | Primary role | Typical interface |
|---|---|---|
| HyperCore | Spot, perps, margin and native order books | Exchange app and API |
| HyperBFT | Consensus and finality | Validators and nodes |
| HyperEVM | Smart contracts and DeFi applications | Wallets and JSON-RPC |
What users can do
Users can trade perpetuals and spot, delegate HYPE to validators, deposit into supported vaults, move assets between HyperCore and HyperEVM, and use independent applications built on the chain. Developers can consume public data, automate exchange actions and deploy EVM contracts.
Each product has separate economics. Perps add funding and liquidation risk. Spot has its own fee table. HyperEVM actions consume HYPE gas. Vault returns depend on strategy performance. A referral discount applies only to eligible trading fees.
What makes Hyperliquid different—and risky
The native order-book design gives traders a familiar execution model with public market data and self-directed signing. It also concentrates importance in the chain, validators, bridge, oracle construction, liquidity and the user’s operational security.
Self-custody is not principal protection. A wrong-chain transfer, compromised signer, leveraged liquidation, bridge failure or protocol event can still cause a total loss. Test the complete deposit, trade and withdrawal flow with small size before increasing exposure.