> For the complete documentation index, see [llms.txt](https://hyperquant.gitbook.io/hyperquant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperquant.gitbook.io/hyperquant/toolbox/deploying-with-hyperquant/hip-assets.md).

# HIP Assets

The deployment of assets within the HyperLiquid network have many technical hurdles, resulting in possible invalid configurations and thus wasted gas, development time, and possible setbacks for cohorts advertising their unique product or use of the protocol. A key feature of HyperQuant's ToolBox is seamless HIP asset (effectively, a bridged token) deployment, which alleviates mistakes and oversights before they occur, directing HIP assets towards their appropriate HIP standard.

HyperLiquid effectively uses two token standards, HIP-1 and HIP-2. While HIP-1 is generally adequate as a permissionless token standard, liquidity bootstrapping approaches tend to be essential for a new market. HIP-2, inspired by Uniswap, is improved upon, utilizing a trustless on-chain order book, secured by network consensus.

To this effect, HIP-1 and HIP-2 assets under the Hyperliquid protocol have unique distinctions for unique roles in deployment:

HIP-1 Assets:

1. Represents a standard for tokens that can be created and traded without needing permission.
2. These tokens are often in the early stages of price discovery, meaning their market value is still being established and may be volatile.
3. To be effectively traded, HIP-1 tokens require strategies to bootstrap liquidity since they may not have established markets or deep liquidity pools.

HIP-2 Assets:

1. Refers to a fully decentralized strategy embedded within the HyperLiquid ecosystem.
2. Provides liquidity but incorporates sophisticated on-chain order book functionality.
3. Operates without centralized oversight, relies on blockchain consensus to secure and execute its logic.
4. Allows for more advanced and user-driven liquidity provisioning and trading strategies.

Simply stated, HIP-1 assets are early-stage tokens needing liquidity support, while HIP-2 assets benefit from a decentralized, sophisticated liquidity provision strategy integrated into the HyperLiquid protocol’s core infrastructure.

*HyperQuant's ToolBox allows users to choose which HIP asset class best suits their current and future goals/strategies without understanding the intricacy or pros and cons, and deploy them correctly in a timely manner.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hyperquant.gitbook.io/hyperquant/toolbox/deploying-with-hyperquant/hip-assets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.