HyperEVM is the Ethereum-compatible execution layer that runs inside the Hyperliquid chain. It lets Solidity developers deploy standard smart contracts that can read from, and trade against, the same on-chain orderbook that powers the Hyperliquid perpetuals exchange. HyperEVM went live on mainnet in February 2025, and by early 2026 it hosts lending markets, liquid-staking tokens, money markets, and the canonical USDT0 deployment on Hyperliquid.
​

If you have used Hyperliquid only as a perps venue, HyperEVM is the part that turns the chain into a general-purpose DeFi environment. This guide explains the dual-block architecture, the apps that matter, how HYPE works as gas, and how HyperEVM stacks up against other app-chain EVMs like Berachain, Monad, and MegaETH.
​

HyperEVM is a permissionless EVM environment embedded in the Hyperliquid L1. Instead of bridging to a separate rollup, contracts execute on the same validator set that runs the orderbook, and they can interact with native L1 state, including spot balances and perp positions, through precompiles. The result is composability between a CLOB exchange and on-chain smart contracts without a cross-chain bridge.
​

HyperEVM uses two block cadences sharing one consensus. Small EVM blocks process Solidity transactions at a fast cadence, while larger L1 blocks settle orderbook actions roughly every second. Both are produced by the same HyperBFT validators, so an EVM contract and an L1 trade can reference each other within the same chain history.
​

According to the Hyperliquid documentation, the EVM layer ships with read precompiles that expose oracle prices, perp positions, spot balances, and validator data, plus a CoreWriter system that lets contracts send actions back to the L1 core. That two-way bridge is the feature that separates HyperEVM from a bolt-on sidechain: a vault contract can place a perp hedge, or a lending market can liquidate collateral directly against the CLOB.
​

In practice this matters because cross-contract composability with an orderbook is rare in DeFi. AMM-based chains can quote prices on-chain but cannot match resting limit orders. By giving Solidity contracts direct read and write access to the CLOB, HyperEVM enables strategies that previously lived inside centralized exchange APIs: delta-hedged LP vaults, on-chain market makers, automated basis trades, and structured products that rebalance against the live book. These are the strategies that drove Hyperliquid's first wave of EVM TVL, and they explain why HyperEVM looks less like Arbitrum and more like a smart-contract layer for a CEX.
​

One consequence of the dual-block design is that EVM transactions and L1 actions are not strictly ordered in the same queue. Developers writing latency-sensitive contracts read oracle and book data through the precompiles inside the EVM block, then commit L1 actions that settle on the next L1 block. The Hyperliquid docs spell out the exact ordering guarantees and the fee model for CoreWriter actions, which is required reading before launching anything that hedges automatically.
​

HYPE is the native token of the Hyperliquid chain. On HyperEVM, HYPE pays gas the same way ETH does on Ethereum. Wallets like MetaMask connect to HyperEVM by adding the chain ID and an RPC endpoint, and standard ERC-20 deployments work without modification. HYPE also accrues fees from the perps and spot venues through the Assistance Fund, which buys HYPE on the open market with protocol revenue.
​

The same HYPE balance is visible on both the L1 and the EVM side. A user can transfer HYPE between the two contexts using the system contract, which is the mechanism most wallets and front-ends abstract behind a single "deposit to EVM" button.
​

By Q2 2026 HyperEVM's TVL is concentrated in a small set of native protocols. DeFiLlama tracks HyperEVM as a top-20 chain by stablecoin supply, with the bulk of liquidity sitting in lending and LST primitives.

These four categories, lending, launchpads with vault strategies, CDP stablecoins, and LSTs, define HyperEVM's early product surface. Spot DEXs are deliberately thin because the L1 CLOB is the canonical spot venue for major pairs.
​

USDT0 is Tether's omnichain USDT, built on the LayerZero OFT standard. Hyperliquid's docs and Tether's launch announcement designate HyperEVM as a canonical USDT0 deployment, which means USDT on Hyperliquid is the OFT version that can be moved across supported chains without a third-party bridge wrapper.
​

For builders, that matters because HyperLend, Felix, and most HyperEVM money markets quote stablecoin liquidity in USDT0 rather than a bridged USDC.e or generic wrapped USDT. For users coming from another chain, the practical effect is that the same USDT0 balance is recognized on Ethereum, Arbitrum, Hyperliquid, and other OFT-enabled chains. See the USDT0 deep dive at support/en/articles/15192015 for the full mechanics.
​

HyperEVM is often grouped with Berachain, Monad, and MegaETH as the "app-chain EVM" cohort that launched in 2024-2025. The four diverge sharply on what the chain is optimized for.

The key contrast: Monad and MegaETH chase raw EVM performance, Berachain redesigns token incentives, and HyperEVM is the only one of the four with a native L1 CLOB that contracts can call into. That is also why HyperEVM TVL skews toward orderbook-aware strategies rather than generic AMM clones.
​

For users, any EVM wallet works once you add the Hyperliquid network. Most flows assume you already hold a balance on Hyperliquid L1 from a USDC deposit (covered in support/en/articles/15191997); you then move funds from the L1 spot account to the EVM side via the front-end's transfer flow. From there you interact with HyperLend, Felix, or Hypurr the same way you would on any EVM chain.
​

For developers, HyperEVM is byte-compatible with the EVM. Hardhat, Foundry, and standard Solidity tooling work out of the box. The Hyperliquid docs publish the chain ID, public RPC, and the precompile addresses for reading L1 state. Gas is paid in HYPE, so deployment scripts need a small HYPE balance on the EVM side.
​

HyperEVM inherits the security of HyperBFT consensus, the same validator set that secures the L1 perps exchange. There is no separate bridge to compromise: the EVM is part of the same chain. The honest answer on risk is that early HyperEVM apps are unaudited or lightly audited, and the LST and CDP protocols layer on top of validator slashing risk. Read each protocol's documentation before depositing. For background on related questions, see how withdrawals work at support/en/articles/15191996, the fee structure at support/en/articles/15191998, and the stablecoin layer at support/en/articles/15191999.
​

Architecture and precompile details verified against the Hyperliquid documentation (hyperliquid.gitbook.io). TVL and stablecoin supply figures cross-checked against DeFiLlama's HyperEVM chain page. Application-level claims sourced from each protocol's own documentation: HyperLend docs, Felix Protocol docs, Hypurr documentation, and the Kinetiq staking docs. USDT0 mechanics verified against Tether's USDT0 launch post and the LayerZero OFT specification. Comparison table figures for Berachain, Monad, and MegaETH come from each project's official documentation and mainnet announcements as of Q2 2026.
​