Hyperliquid runs as two coupled execution environments on a single chain. The original Hyperliquid L1 is a perp-DEX-specialized state machine that hosts a fully onchain orderbook. HyperEVM, launched February 2025, adds a general-purpose EVM that lets Solidity developers deploy dApps on the same network and read directly from the orderbook's state. Together they form a chain with $1.5B TVL and a unified HYPE token, but the two halves answer very different design questions.
​

This guide separates the two layers, explains how they interact, and lays out which side you should care about as a trader, builder, or LP.
​

Hyperliquid L1 is the perp orderbook chain — a HyperBFT-consensus state machine where every order, fill, and liquidation is a native protocol action. HyperEVM is a second execution environment on the same consensus, running a standard Ethereum Virtual Machine for Solidity smart contracts. HyperEVM contracts can read L1 orderbook state through precompiles. One chain, two execution lanes, one token (HYPE).
​

Both lanes share consensus, validators, and finality. Think Solana (one monolithic runtime) versus Polkadot (separate execution environments under one consensus): Hyperliquid sits closer to the Polkadot model, with the orderbook and EVM as distinct execution lanes.
​

Hyperliquid L1 is an app-specific chain whose state machine includes the orderbook itself. There is no smart contract for "the perp DEX" — placing an order, matching a fill, and triggering a liquidation are protocol-level transactions. HyperBFT consensus finalizes blocks in under a second, which is why traders can submit limit orders and see them rest, fill, or cancel without the latency of a contract-based DEX.
​

The L1 currently lists 100+ perpetual markets and a growing spot book. According to DeFiLlama, Hyperliquid L1 holds $1.5B TVL, the largest of any non-Ethereum-aligned trading-specific chain in 2026. Funding payments, vaults, and the HLP market-making pool all run as native L1 logic.
​

Source: hyperliquid.gitbook.io/hyperliquid-docs
​

HyperEVM is a second execution environment that sits on the same HyperBFT consensus. Developers deploy standard Solidity contracts using the tools they already know (Foundry, Hardhat, viem, wagmi). What makes HyperEVM distinct from any other EVM chain is that contracts can call precompiles to read live L1 state — current oracle prices, perp positions, vault balances — without an offchain relayer or a price feed contract.
​

That tight coupling unlocks designs that aren't easy elsewhere: a lending market that liquidates against the L1 oracle in the same block, a structured product that mirrors an HLP vault position, or a stablecoin whose collateral is a hedged perp leg. The EVM runs in a fast lane (small, frequent blocks) and a slow lane (larger, less frequent blocks) so heavy contract calls don't block latency-sensitive trades.
​

Source: hyperfoundation.org announcement, February 2025.
​

HYPE is the native token for the entire Hyperliquid network — L1 and HyperEVM share it. It pays gas on HyperEVM, secures HyperBFT through staking, and functions as the protocol's governance unit. Trading fees on the L1 orderbook accrue to the assistance fund and HLP, with a buyback-and-burn mechanism that has retired a meaningful share of supply since the November 2024 token generation event.
​

Because HYPE is a single asset across both lanes, an EVM contract that holds HYPE can be staked, used as gas, or posted as L1 collateral without bridging.
​

Two mechanisms. First, precompiles: predefined contract addresses on HyperEVM that, when called, return live L1 state — for example, the current mid price of a perp market or a user's open position. Second, system contracts that can submit L1 actions (place an order, transfer collateral, withdraw) on behalf of an EVM-side smart contract.
​

The result is composability that reaches across the lane boundary. A vault contract on HyperEVM can read the BTC-PERP oracle, calculate a hedge size, and submit the hedging order to L1 in a way that settles atomically with the user's deposit. dYdX's app-chain doesn't expose this surface; an EVM L2 doesn't either, since neither has a native orderbook to read from.
​

L1-native applications include the perp and spot books themselves, the HLP market-making vault, native staking, and the bridge to Arbitrum that handles USDC deposits. These aren't "deployed" — they're part of the protocol.
​

HyperEVM hosts the dApp ecosystem that grew through 2025: lending markets (HypurrFi, HyperLend), liquid staking for HYPE (StakedHYPE, Kinetiq), perp-collateral structured products, and the first wave of stablecoins issued natively on the chain. Token launches that need ERC-20 standards (DEX trading on AMMs, governance, airdrops) live on HyperEVM rather than the L1 spot book.
​

For the full live list, see defillama.com/chain/Hyperliquid.
​

Use the L1 directly if your job is trading or market-making. The orderbook, vaults, and HLP live there, fees are paid in HYPE, and latency is the lowest the chain can offer. Use HyperEVM if you're building or using DeFi primitives — lending, AMMs, structured products, liquid staking, stablecoin issuance. Most users end up touching both: depositing USDC through the L1 bridge, then routing some of it into a HyperEVM lending market between trades.
​

Hyperliquid's bet is that one chain can host both an app-specific orderbook and a general EVM without forcing users to bridge between them. Compare against:

For where Hyperliquid sits in the broader stablecoin-L1 landscape, see our roundup of the best stablecoin L1 chains in 2026.
​

The split lanes add real complexity. Developers have to reason about two execution environments, two block cadences, and the precompile interface between them. Wallet UX is still catching up — some EVM wallets show only HyperEVM balances and miss L1 positions. The bridge from Arbitrum is the main USDC on-ramp, and outages there have historically been the chain's biggest point of fragility. None of this is fatal, but the "two lanes, one chain" model is genuinely newer than the monolithic-EVM playbook most teams have shipped against.
​

TVL, chain rankings, and dApp lists from DeFiLlama's Hyperliquid chain page, snapshot 2026-05-04. Protocol mechanics and precompile descriptions from the official Hyperliquid documentation. HyperEVM launch details from the Hyper Foundation February 2025 announcement. HYPE token data from CoinGecko. We did not pull onchain analytics directly; figures reflect public dashboards as of the snapshot date.
​