Deploying HIP-1 and HIP-2 Tokens and Spot Pairs on Hyperliquid
Summary
This document describes the API workflow for deploying HIP-1 and HIP-2 assets on Hyperliquid. The core process sends five actions in order: register the token specification, distribute initial balances and blacklist settings as needed, finalize genesis using a supply checksum, register a spot pair, and configure hyperliquidity. It also covers deploying pairs between already existing assets, which use a separate Dutch auction whose status can be queried independently.
Optional actions allow deployers to set a trading-fee share, add token display information, and assign a deployer label. The documentation gives field definitions and constraints, including when actions may be used and limits on changing some settings. It is an implementation reference, not an evaluation of token economics, liquidity quality, or trading performance. Deployers must follow the specified action order and account for optional fields and restrictions when integrating the API.
Key ideas
- Asset deployment follows an ordered sequence of registration, genesis, spot-pair setup, and hyperliquidity configuration actions.
- User genesis allocations can be submitted in multiple calls and can include blacklist updates.
- A checksum supplied at genesis confirms the maximum supply after allocation calls.
- Pairs made from existing assets follow a separate Dutch auction process.
- Fee sharing, token annotations, and deployer labels are optional settings with documented restrictions.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.