Skip to content
TradePerpetuals9 pages
What a perpetual future isFoundationA perpetual future is a contract on an asset's price that never expires, kept close to that price by an hourly payment between longs and shorts.Contract specificationsPractitionerEvery Hyperliquid perp is a linear contract on 1 unit of its asset, defined by size decimals, maximum leverage, a margin table and a margin mode.FundingPractitionerFunding is an hourly payment between longs and shorts, set by how far the perp trades from the oracle price, that ties a contract with no expiry to its index.Margin: cross, isolated and margin tiersPractitionerMargin is the collateral behind a perp: initial margin to open, maintenance margin to stay open, shared in cross mode or ring-fenced in isolated mode.Leverage and liquidationPractitionerBelow maintenance margin, positions go to the order book as market orders; below two thirds of it, the liquidator vault takes them over.Auto-deleveragingExpertWhen an account goes below zero, auto-deleveraging closes the most profitable, most leveraged opposing positions at the previous mark price, leaving no bad debt.Hyperps and index perpetualsPractitionerHyperps fund against a moving average of their own mark price until spot trading exists; index perps track a formula the validators publish.AMM-priced perpetualsExpertSome perps price off a Uniswap V2 or V3 pool instead of exchange spot prices, and are isolated only, with margin locked in until the position closes.DelistingPractitionerWhen validators vote to delist a perp, positions settle at the 1-hour time-weighted oracle price before the vote and no new orders are accepted.

Native tokens for traders

Foundation

A HIP-1 token is a capped-supply token native to HyperCore whose supply, genesis split, deployer and launch liquidity are public state a buyer can check.

Anyone can create a HyperCore token, so the checking falls on you. The deployer pays gas in an auction; nobody reviews the result.

The standard guarantees a supply capped at genesis that can only fall, balances on the HyperCore ledger and a spot order book from launch. It guarantees nothing about value, fair distribution or what backs a bridged asset (HIP-1).

After the auction, deployment fixes name and decimals, genesis balances, maximum supply, the first spot pair and, optionally, Hyperliquidity, a protocol-run launch ladder.

  • Supply. maxSupply is also the initial supply; trading fees and burns reduce it.
  • Genesis goes to named addresses and, pro rata, to holders of an existing “anchor” token above a threshold.
  • Fee share. The deployer takes its share of fees collected in the token, the buy side of each trade, and the rest is burned.

Say a buy pays a 1-token fee at a 40% deployer share: 0.4 goes to the deployer and 0.6 is burned.

What to check, and where it lives:

Check Field Why it matters
Identity tokenId (34-character hex), token index (spotMeta.tokens) Names are short, deployer-chosen and remapped by apps
Supply maxSupply, totalSupply, circulatingSupply (tokenDetails) Circulating supply against maximum shows what can still reach the market
Locked or future supply nonCirculatingUserBalances, futureEmissions Supply that is not trading today but may later
Who got the genesis genesis.userBalances, genesis.existingTokenBalances Concentration in a few addresses is sell pressure waiting
Deployer deployer, deployTime, deployGas Who launched it, when, and what they paid
Launch liquidity seededUsdc; the Hyperliquidity ladder on the book How much USDC sits under the price at launch
Smallest tradable size szDecimals, weiDecimals You cannot sell less than one lot
HyperEVM link evmContract (spotMeta.tokens) Whether the token can cross to the HyperEVM
Deployer fee share deployerTradingFeeShare (HyperEVM precompile 0x80C) How much of the buy-side fee the deployer keeps

Standard rules that shape these fields:

Rule Value
Name at most 6 characters
Decimals szDecimals + 5 <= weiDecimals; the official frontend allows szDecimals 0 to 2 and weiDecimals 0 to 8
Lot size 10 ** (weiDecimals - szDecimals) in the token’s smallest unit
Deploy auction Dutch auction over 31 hours, falling to a floor of 500 HYPE
Anchor genesis threshold 0.0001% of the anchor token’s maximum supply
Deployer fee share 0 to 100% of fees collected in the token; default 100%; can only decrease, except that tokens deployed before fee shares existed may raise theirs once, from zero

Work down the first table, identifying the token by tokenId or pair index, never by name. It misses three things:

  • The launch ladder is fixed and doesn’t react to news: look at the book beyond it.
  • A bridged token is only as good as its bridge and minting. The docs’ simplest setup puts the whole maximum supply, up to 2^64 - 1, in the token’s system address to flow in and out with the bridge, so circulating supply is what counts.
  • Descriptions, categories and display names are deployer annotations, changeable once per day: claims, not verification.
{ "type": "tokenDetails", "tokenId": "0x6d1e7cde53ba9467b783cb7c530ce054" }

Take the tokenId from spotMeta.tokens. From the HyperEVM, the tokenInfo precompile at 0x80C returns name, pairs, deployerTradingFeeShare, deployer, evmContract, szDecimals, weiDecimals and evmExtraWeiDecimals for a token index (precompiles).

  • The fees page lets spot deployers keep up to 50 per cent of their token’s fees; the HIP-1 page, up to 100 per cent of fees collected in the token. The bases differ, and the split is unmeasured here.
  • Genesis tokens carry an entry price of a 10,000 USDC market cap, so selling them books almost the whole sale as closed PnL (entry price and PnL).
  • Balances under one lot and worth at most $1 go to the daily dust conversion.

For the deployer’s side, see Deploying a spot token and Linking a token.