HIP-1
HIP-1 was one of the earliest major infrastructure upgrades inside the Hyperliquid ecosystem. The proposal focused on introducing native spot assets and token support directly within HyperCore.
Before HIP-1, Hyperliquid mainly focused on perpetual futures trading. The proposal expanded the platform by allowing assets themselves to exist natively inside the ecosystem instead of supporting only derivative products.
This upgrade introduced Hyperliquid’s token standard and spot trading infrastructure. Developers and projects could launch tokens that operate directly inside HyperCore’s trading environment.
HIP-1 also helped establish the foundation for later ecosystem expansion. Once native assets could exist on Hyperliquid, the platform could begin building liquidity systems, builder-deployed markets, and more advanced financial products on top of them.
The proposal integrated spot assets into the same trading architecture already used for perpetual futures. This meant spot trading inherited HyperCore’s order books, matching engine, and account systems instead of operating in isolated infrastructure.
One important goal behind HIP-1 was composability. Traders could hold spot assets, perpetual positions, and later outcome contracts within the same ecosystem account instead of moving funds across separate protocols.
HIP-1 also became a critical prerequisite for HIP-2. After introducing native assets, Hyperliquid needed mechanisms to support liquidity and healthy trading conditions for newly launched tokens. HIP-2 later addressed this through Hyperliquidity.
As Hyperliquid evolved into a broader financial infrastructure platform, HIP-1 remained one of the core proposals that enabled ecosystem-level market expansion.
Without native assets and spot infrastructure, later upgrades like builder-deployed perpetuals and outcome markets would have been much harder to integrate into one unified execution layer.
Why It Matters
HIP-1 established the foundation for native asset creation and spot trading on Hyperliquid. It transformed the ecosystem from a perpetual-focused exchange into a broader on-chain financial infrastructure platform.
The proposal also enabled later upgrades like Hyperliquidity, builder-deployed markets, and outcome contracts.
What did HIP-1 introduce to Hyperliquid?
HIP-1 introduced Hyperliquid’s native token and spot asset infrastructure. This allowed assets to exist and trade directly inside HyperCore instead of supporting only perpetual derivatives.
The proposal created the technical framework for spot trading markets using Hyperliquid’s existing order book and matching engine systems.
It also laid the groundwork for future ecosystem expansion by enabling native market creation and composable trading environments.
Why was HIP-1 important for later Hyperliquid upgrades?
HIP-1 created the asset infrastructure required for future ecosystem growth. Once native assets existed on Hyperliquid, later proposals could focus on liquidity systems and advanced market creation.
HIP-2 later introduced Hyperliquidity to support newly launched markets. HIP-3 expanded into builder-deployed perpetual futures, while HIP-4 introduced outcome contracts and event markets.
All of these later systems depended on the core infrastructure established by HIP-1.
How does HIP-1 support composability on Hyperliquid?
HIP-1 integrated spot assets directly into HyperCore’s shared trading infrastructure. Traders could manage spot balances alongside perpetual positions within the same account system.
This composability became a major design principle across the ecosystem. Instead of splitting products into separate protocols, Hyperliquid combined them into one execution environment.
The result is a more unified trading experience where collateral, liquidity, and positions interact more efficiently across market types.