HyperCore

Hyperliquid's on-chain order book and matching engine, the component that runs spot and perpetual trading. HyperEVM smart contracts can read its state directly.

Definition

HyperCore is where orders live and trades happen on Hyperliquid. Rather than running matching on private servers and settling results on-chain afterwards, the order book itself is part of the chain’s state, maintained by the validator set.

Why that design choice matters

Most exchanges that call themselves decentralised still match orders off-chain, because an order book is demanding: it changes constantly, and every placement and cancellation is a state update.

Putting the book on-chain means the state is verifiable rather than reported. What the exchange says is resting at a price is what the network’s own state says, and execution follows consensus rules rather than an operator’s discretion.

The cost is that the chain has to be built around that workload, which is why it is a purpose-built system rather than a contract deployed on a general network.

What it means for you as a trader

Orders, fills, positions and liquidations are chain state, so they can be independently verified rather than taken on trust from an interface.

It does not remove the risks that come from the design elsewhere: the validator set is still a trust assumption, deposits still arrive through a bridge contract, and being on-chain says nothing about whether the market you are trading has liquidity.

Its relationship to HyperEVM

HyperCore holds the trading state; HyperEVM is the smart contract layer that shares the same chain and can read it. That pairing is what lets an application react to live order book data without an external oracle or an off-chain relay.

Where you will run into it

In Hyperliquid’s own documentation, in explanations of why its order book is described as on-chain, and in anything built on HyperEVM that consumes trading data.