Curious about a word? Tap a dotted term for its meaning.

Application chain / NETWORK PROFILE

Hyperliquid

HYPE CMC #9 in the snapshot

A finance-focused layer 1 combining native order books with an EVM application environment.

Profile checked Asset ranks captured 14 Nov 2026Snapshot & methodology ↗

01 / THE PURPOSE

What is Hyperliquid for?

Hyperliquid makes trading infrastructure part of its shared chain. HyperCore handles spot and perpetual order books; HyperEVM lets developers build general-purpose contracts beside it.

02 / THE ARCHITECTURE

Three questions about the machinery.

01

How does it agree?

Consensus & security

HyperBFT is the chain’s consensus system. HyperCore and HyperEVM use that same consensus; HyperEVM is not a separate Ethereum rollup.

02

Where do instructions run?

Execution model

Native trading operations and EVM contract execution have different interfaces but belong to one chain. Application access to trading state is subject to the deployed integration features.

03

What is the token for?

HYPE in the system

HYPE supports consensus staking and pays HyperEVM gas. A leveraged trading balance is a separate position with collateral, margin and liquidation rules.

03 / THE DESIGN CHOICES

What comes with the design?

Each architecture makes choices about security, performance, coordination, and who can participate.

04 / IN PRACTICE

Follow one use.

Illustrative: a contract can read market information from the chain’s trading environment. That market price still needs interpretation before it is used to value collateral.

05 / CHECK THE EXPLANATION

Sources & snapshot.

Network descriptions use the references below. The CoinMarketCap snapshot determines which assets are in scope and their captured rank; it does not assess the quality of a network.

Profile checked 14 Nov 2026. Network designs and ranked positions can change.