Hyperliquid Architecture · Ecosystem & Tokens · 7/8
HYPE Token and HIP-1 to HIP-3
The HYPE Token
HYPE is the native token of the Hyperliquid ecosystem, serving multiple functions:
Utility
- Staking — Secure the network by staking with validators; validator votes are weighted by stake
- Gas on HyperEVM — HYPE is the gas token for HyperEVM transactions
- Deployment gas and stakes — HIP-1 token deployments are paid in HYPE, and HIP-3 perp deployers must stake HYPE
- Fee Discounts — Staking HYPE (not just holding it) reduces trading fees, from 5% to 40% depending on the amount staked (fees)
Trading fees go to the community rather than a company: to HLP, to the Assistance Fund, and to deployers of spot and HIP-3 assets. The Assistance Fund converts its fees to HYPE automatically and that HYPE is burned.
Tokenomics
HYPE launched at its genesis event on November 29, 2024, with 310 million HYPE (31% of the 1 billion max supply) distributed to early users based on points. The distribution was notable for having no allocation to private investors, centralized exchanges, or market makers; the rest is reserved for future emissions and community rewards, core contributors, the Hyper Foundation, and grants (as reported at genesis, e.g. The Defiant).
HIP-1, HIP-2 and HIP-3
Hyperliquid Improvement Proposals (HIPs) define standards for the ecosystem:
HIP-1: Native Token Standard
HIP-1 defines the standard for deploying capped-supply native tokens on HyperCore. Unlike ERC-20 tokens, HIP-1 tokens are:
- First-class citizens of HyperCore state (not smart contracts)
- Listed with a native spot order book against USDC as soon as deployment completes
- Deployed after winning a Dutch auction: a 31-hour auction for deployment gas, paid in HYPE
A HIP-1 token can also be linked to an ERC-20 contract on HyperEVM so the same token can move between the two environments.
HIP-2: Hyperliquidity
HIP-2 provides optional protocol-native liquidity for a new HIP-1 token's USDC spot pair. It is an on-chain strategy that runs as part of block execution, with no operator.
The mechanism works by:
- Funding the strategy with a portion of the token's supply (and optionally USDC for bid levels) at deployment
- Placing orders across a price range with levels 0.3% apart
- Updating at most every 3 seconds, so that filled levels are replaced on the other side
This gives a new token a baseline market (a 0.3% spread refreshed every 3 seconds), while other market makers can quote alongside it on the same book. Deployers of bridged or existing assets often turn Hyperliquidity off.
HIP-3: Builder-Deployed Perpetuals
HIP-3 lets anyone who stakes 500,000 HYPE deploy and operate their own perpetual futures DEX on HyperCore. The deployer defines each market — including its oracle, contract specs, collateral asset, and leverage limits — sets oracle prices, and can settle markets. Each HIP-3 DEX has its own order books and margining but uses the same HyperCore engine and API. Validators can slash a deployer's stake by stake-weighted vote for malicious or irregular market operation (HIP-3 docs). As of October 2026, the info API's perpDexs endpoint listed ten HIP-3 DEXes on mainnet, not all of which still had active markets.
Builder Codes (not an improvement proposal)
Builder codes are a separate feature: front-ends, bots, and other integrators can charge a fee on the orders they submit for a user, up to a maximum the user approves (capped at 0.1% on perps and 1% on spot) (builder codes).
Token Launches
Launching a token on Hyperliquid follows a distinctive process:
- Win the HIP-1 deployment auction and configure the token
- Optionally enable HIP-2 Hyperliquidity for initial liquidity
- The token trades on its native spot order book against USDC
- Perpetual markets are separate: they are listed by validators or deployed by a HIP-3 deployer, not created automatically