What Is HyperCore?

HyperCore is the native high-performance trading engine at the heart of the Hyperliquid layer 1 blockchain. HyperCore handles order book matching, perpetual future settlement, funding rate payments, liquidations, vault operations, and spot trading — all on its own optimised consensus (HyperBFT) rather than the EVM.

HyperCore runs as a logically separate chain (chain ID 9999) from HyperEVM (chain ID 999), but both share the same validator set and consensus. HyperCore processes over 100,000 orders per second with sub-second finality, achieving centralised-exchange-grade performance while remaining fully onchain.

How HyperCore differs from EVM chains

HyperCore is not an EVM environment. It does not execute Solidity smart contracts or use gas-based transaction pricing. Instead, users interact with HyperCore through:

  • The Hyperliquid exchange API (REST/WebSocket) for placing orders, managing positions, and querying state

  • HyperEVM smart contracts that write to HyperCore via the HyperCore Writer system contract

  • Precompile reads on HyperEVM that expose HyperCore state (vault equity, clearinghouse state, etc.)

Asynchronous execution model

Write actions sent from HyperEVM to HyperCore through the HyperCore Writer are not atomic. When sendRawAction() succeeds on HyperEVM, it only means the action was queued. HyperCore validators process queued actions with a few seconds’ delay. An action can succeed on EVM but later fail on HyperCore, with no revert propagation back to EVM.

This asynchronous model means:

  • Deposits can partially fail (USDC bridged but vault deposit rejected)

  • Precompile reads in the same block as a write action return stale data

  • Funds may briefly “disappear” from both EVM and HyperCore balances during bridging

Native vaults

HyperCore supports native vaults where users can deposit USDC to participate in automated trading strategies. The Hyperliquid Provider Vault (HLP) is the protocol’s flagship vault for market making and liquidations. User-created vaults have a 1-day lock-up period; protocol vaults (HLP) have a 4-day lock-up. Vault deposits require a minimum of 5 USDC.

Account activation

Smart contract addresses (such as Safe multisigs on HyperEVM) must be explicitly activated on HyperCore before bridged USDC deposits will clear. Activation uses CoreDepositWallet.depositFor() and incurs a ~1 USDC account creation fee. Without activation, deposited USDC gets permanently stuck in EVM escrow.

See also