What Is HyperEVM? Hyperliquid's Smart-Contract Layer Explained

Most exchanges are applications; Hyperliquid is a blockchain whose flagship application is an exchange. HyperEVM opens that blockchain to arbitrary smart contracts — lending markets, DEX aggregators, liquid-staking protocols and consumer apps that settle on the same chain as the order books, rather than on a bridged sidechain.

For users, the practical consequence is a growing ecosystem of applications reachable with a normal EVM wallet, using HYPE for gas. For builders, it is an EVM target with something no other chain offers natively: direct programmatic access to a high-volume on-chain exchange's state.

How is HyperEVM different from HyperCore?

Hyperliquid's state is split between two execution environments secured by the same HyperBFT consensus. They are components of one blockchain — official docs are explicit that HyperEVM "is not a separate chain" — which means moving assets between them is a state transition, not a bridge with its own trust assumptions.

The two sides connect through native asset transfers between Core spot balances and EVM balances, and smart contracts on HyperEVM can read HyperCore state (prices, positions, balances) through read precompiles. Writing back to the exchange — submitting orders, transfers and staking operations from contracts via the CoreWriter system contract — is documented for testnet, but official docs state that write system contracts are not yet live on mainnet.

How does HyperEVM's dual-block architecture work?

HyperEVM produces two kinds of blocks in parallel, decoupling confirmation speed from capacity. Small blocks are produced every second with a 3M gas limit — enough for ordinary transfers and swaps to confirm fast. Large blocks are produced every minute with a 30M gas limit, giving heavyweight transactions such as big contract deployments the room they need.

Transactions go to small blocks by default. Developers who need a large block flag it explicitly with an account-level setting (the evmUserModify action with usingBigBlocks). Ordinary users never need to think about this — wallets and apps handle it.

Fees follow EIP-1559: every transaction pays a base fee and an optional priority fee, both denominated in HYPE — and both are burned, since HyperBFT consensus has no miner or sequencer to tip.

How do you add HyperEVM to a wallet?

HyperEVM works with any standard EVM wallet (MetaMask, Rabby, Rainbow and the like). Add it as a custom network with these parameters from the official docs:

What pays for gas on HyperEVM?

Like ETH on Ethereum, HYPE is required for every HyperEVM transaction — and it must be on the EVM side. A common first-time stumble is holding HYPE in your Core spot balance and finding you cannot pay gas on the EVM. Transfer a small amount across first; note that the transfer itself costs gas on the side it starts from (Core-side gas for spot→EVM, EVM-side gas for EVM→spot).

How do you move assets between HyperCore and HyperEVM?

What applications run on HyperEVM?

• DeFi built on exchange rails — lending markets, stablecoins and structured products that read Hyperliquid's own order-book prices instead of external oracles.
• Liquid staking — protocols that wrap staked HYPE into transferable tokens usable across the ecosystem.
• Trading tooling — vault frontends, automation and portfolio products. Once write system contracts go live on mainnet, contracts will be able to submit orders, transfers and staking operations to HyperCore directly.
• Token launches — ERC-20s can be deployed permissionlessly and linked to native HyperCore spot order books, so a token can trade on a real order book rather than only an AMM.
• Consumer apps — NFT platforms, payments and social experiments, as on any EVM chain.

For builders, the distinctive primitives are read precompiles — contracts can query perp positions, spot balances, vault equity, staking delegations and oracle prices directly from HyperCore state — and, in future, the CoreWriter system contract (0x3333…3333) for sending actions to HyperCore. CoreWriter is documented on testnet, but per official docs write system contracts are not yet live on mainnet; order actions submitted through it are intentionally delayed a few seconds to prevent latency games.

What are HyperEVM's risks and limitations?

• Application risk — HyperEVM apps are third-party smart contracts. The chain's security does not vouch for any app deployed on it; audit status and team reputation matter as on any EVM chain.
• Maturity — HyperEVM is younger than the exchange. Tooling, indexers and explorers have improved rapidly but remain younger than Ethereum equivalents.
• Linked-token caveats — when a Core spot asset is linked to an EVM contract, the protocol does not verify the contract is a well-behaved ERC-20. Deployer errors can strand or break a token; this mostly concerns builders, but users of obscure tokens inherit the risk.
• Wrong-network mistakes — the classic loss scenario is sending assets to an address on the wrong side, or to an exchange that doesn't support the HyperEVM network. Test transactions eliminate most of this.
• Evolving feature set — capabilities are enabled in stages; a tutorial written months ago may describe behaviour that has since changed.

Who is HyperEVM for?

HyperEVM turns Hyperliquid from a standalone exchange into a full ecosystem: one chain where the order books are the base layer and ordinary EVM applications build on top of them. If you already use Hyperliquid, trying HyperEVM costs little — add the network, move a few HYPE across for gas, and treat every new app with the same skepticism you would anywhere else on-chain.