If you have ever deployed an ERC-20 on Ethereum or an SPL token on Solana, you already know the drill: write a contract, pay gas, register metadata, then beg a DEX for a liquidity pool. Hyperliquid threw that workflow out. HIP-1 is the native token standard on the Hyperliquid L1, and it bakes spot trading, an orderbook, and even auction-based deployment into the protocol itself. No smart contract required.
This guide explains what HIP-1 is, how it pairs with HIP-2 for bootstrapped liquidity, how spot tokens differ from perp markets, what the HYPE genesis event looked like, what it costs to deploy a token in 2026, and how the whole stack compares to ERC-20 and SPL. Specs sourced from hyperliquid.gitbook.io.
What is HIP-1?
HIP-1 (Hyperliquid Improvement Proposal 1) is the native fungible token standard on the Hyperliquid L1. Unlike ERC-20, HIP-1 tokens are not smart contracts. They are first-class objects in the L1 state, with built-in orderbook trading against USDC and a Dutch auction deployment mechanism. Every HIP-1 token has a ticker, decimals, total supply, and a deployer-defined genesis allocation.
How HIP-1 differs from ERC-20
ERC-20 is an interface, not a primitive. Anyone can deploy a contract that implements transfer, balanceOf, and approve, and the EVM does not care what is inside. HIP-1 inverts that. The Hyperliquid L1 owns the token logic, the supply, and the orderbook in protocol state. There is no contract to audit because there is no contract. The tradeoff: you cannot do arbitrary logic. No rebase tokens, no fee-on-transfer quirks, no governance hooks. Just transfers and trading.
What is HIP-2 and how does it bootstrap liquidity?
HIP-2 is the companion standard for automated market making. When a HIP-1 token launches, the deployer can opt into HIP-2, which seeds a protocol-managed liquidity strategy that quotes both sides of the book around an anchor price. The strategy uses the deployer's allocated USDC and tokens, rebalances on a fixed schedule, and removes the cold-start problem that kills most new ERC-20 launches. HIP-2 is opt-in, not mandatory, and the parameters (anchor price, spread, rebalance interval) are set at deploy time.
Spot tokens vs perp markets on Hyperliquid
Hyperliquid runs two parallel markets. Perps are the original product: cash-settled USDC contracts on BTC, ETH, SOL, and 150-plus other assets, with no underlying token on the L1. Spot is the newer surface, powered by HIP-1. A spot token like PURR or HYPE exists as real balance on the L1, can be transferred wallet to wallet, and trades on a native USDC orderbook. Perps cannot be transferred. Spot tokens can. That distinction matters for custody, taxes, and bridging.
The HYPE genesis: airdrop and tokenomics
HYPE is the Hyperliquid L1 gas and governance token, deployed as a HIP-1 asset. The genesis event in late 2024 airdropped 31% of the 1 billion supply to historical users based on a points program that ran for over a year. No VC allocation, no presale, no team unlocks for insiders ahead of users. 38.888% went to community rewards and future emissions, with the remainder split between core contributors and the Hyper Foundation. The launch is widely cited as one of the cleanest token distributions in DeFi history.
How much does it cost to deploy a HIP-1 token?
HIP-1 tokens are not free to deploy. Hyperliquid uses a Dutch auction for ticker registration. The auction starts at a high price (historically 500,000 USDC or more for premium tickers) and decays over 31 hours until someone bids. Winning bid mints the ticker. As of early 2026, auction clearing prices have ranged from a few hundred USDC for obscure tickers to six figures for short, brandable ones. The auction proceeds are burned, not paid to the team. After the ticker is won, the deployer sets supply, decimals, and genesis allocation, then optionally enables HIP-2.
HIP-1 vs ERC-20 vs SPL: feature comparison
Feature | HIP-1 (Hyperliquid) | ERC-20 (Ethereum) | SPL (Solana) |
Implementation | L1 protocol primitive | Smart contract | Token program account |
Custom logic | None (transfers + trading only) | Arbitrary (rebase, fees, hooks) | Limited (extensions via Token-2022) |
Built-in orderbook | Yes (USDC quote) | No (relies on external DEX) | No (relies on Serum/Raydium/Jupiter) |
Deployment cost | Dutch auction (variable USDC) | Gas to deploy contract | ~0.002 SOL plus rent |
Liquidity bootstrap | HIP-2 native market maker | Manual (Uniswap pool seeding) | Manual (Raydium pool seeding) |
Audit surface | Protocol audited once | Per-token audit needed | Token program audited, mints permissionless |
Transfer fees | L1 gas (HYPE) | ETH gas | SOL gas |
Can you bridge HIP-1 tokens to other chains?
Not directly. HIP-1 tokens live on the Hyperliquid L1 and have no canonical representation elsewhere. HYPE itself is bridgeable to HyperEVM, Hyperliquid's EVM execution layer, where it appears as a wrapped ERC-20. From HyperEVM, third-party bridges can move it further, but each hop adds wrapping risk. For most spot tokens, the orderbook is on Hyperliquid and exits route through HYPE or USDC withdrawals to Arbitrum.
What HIP-1 means for builders and traders
For builders, HIP-1 collapses the launch checklist. No Solidity audit, no Uniswap V3 tick math, no merkle airdrop contract. You win an auction, set supply, optionally enable HIP-2, and your token is trading against USDC the same day. For traders, it means the spot book is the protocol, not a third-party DEX. Slippage, fees, and finality are all governed by the L1 itself. The constraint is composability. You cannot write a HIP-1 token that yields, rebases, or hooks into governance, so DeFi-native tokens with rich behavior still belong on Ethereum or Solana.
Methodology and sources
Specifications drawn from hyperliquid.gitbook.io (HIP-1, HIP-2, deploying a native spot asset, genesis distribution sections). HYPE tokenomics cross-referenced with the official Hyper Foundation announcement and onchain genesis snapshot. Dutch auction clearing prices observed from public auction history. ERC-20 and SPL comparison data from ethereum.org and solana.com developer documentation. No third-party analyst reports were used.
Related reading
support/en/articles/15197987
support/en/articles/15197986

