> For the complete documentation index, see [llms.txt](https://ascendlaunch.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ascendlaunch.gitbook.io/docs/project-growth/hypercore-and-hip-3.md).

# HyperCore and HIP-3

Ascend supports a path from an Elysium token launch toward additional Hyperliquid markets. The intended progression considers a project's trading activity, liquidity, technical readiness, and ability to meet each venue's requirements.

## HyperCore spot markets

HyperCore supports native spot order books. Hyperliquid's HIP-1 documentation describes the token standard and deployment process, including the requirements for deploying an asset that already exists externally.

Ascend's role is to help qualifying projects prepare for an eligible spot deployment and coordinate the resources required for it. Treasury-held ecosystem assets may contribute to project support where designated for that purpose. Funding for deployment and both sides of initial liquidity must be identified for the particular project.

Ascended status does not reserve a spot deployment or cover every related cost. A project must still satisfy the applicable deployment, asset-linking, and liquidity requirements.

See [Hyperliquid's HIP-1 reference](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-1-native-token-standard) for the underlying process.

## HIP-3 perpetual markets

HIP-3 enables builder-deployed perpetual markets on Hyperliquid. The deployer is responsible for market specifications, oracle inputs, leverage settings, and ongoing market operation.

Ascend's intended support prioritizes an established spot-market foundation before a project pursues leveraged exposure. A future perpetual market requires agreement with the relevant venue and a suitable market design. The availability of a spot price alone does not establish that it is an appropriate oracle input.

See [Hyperliquid's HIP-3 reference](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-3-builder-deployed-perpetuals) for deployer responsibilities and requirements.

## What progression means

| Stage                    | Main focus                                                         |
| ------------------------ | ------------------------------------------------------------------ |
| Launch on Ascend         | Establish the token's initial market and creator-fee model         |
| Ascended status          | Qualify for additional visibility and ecosystem support            |
| HyperCore spot readiness | Prepare the asset, deployment, and liquidity requirements          |
| HIP-3 readiness          | Evaluate market design, oracle suitability, and venue requirements |

These are distinct stages of support. Progression is conditional, and individual projects may pursue different paths or remain at an earlier stage.

Fees on a subsequent HyperCore or HIP-3 venue are governed by that venue's rules. Ascend's launch-pool fee schedule should not be assumed to apply to every future market for the token.
