> 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/about-ascend.md).

# About Ascend

![ASCEND](https://content.gitbook.com/content/kBhQL4KtgFMdu4nj8Hn0/blobs/XrlrcNZ6A23FWTlI6AKn/assets/ascend-banner.jpg)

## Token Launch and Lifecycle Infrastructure for Elysium

**HYPE rewarded holding. So do we.**

*Litepaper · September 2026*

*This document describes Ascend’s proposed protocol design. Selected economic parameters and implementation details remain under development.*

Ascend is building token launch and lifecycle infrastructure for Elysium that aligns builders, HYPE holders, and traders through a shared economic model.

**Our responsibility extends beyond launch day.**

Projects need a foundation for continued trading, visibility, and liquidity development. HYPE holders need a way to participate in emerging projects without allocating their underlying position to individual token purchases. Traders and community contributors need incentives that reward the activity they bring.

**Ascend brings these participants together.**

Builders launch through a standardized pool framework and receive a share of the fees generated by their token’s trading activity. Qualifying projects benefit from ecosystem buybacks and increased visibility. HYPE holders stake through Ascend, directing their staking yield toward ecosystem-token exposure while earning additional HYPE rewards funded by protocol revenue. Ecosystem-token airdrops to stakers are funded only by the yield from their own kHYPE staking positions, not by protocol fees.

The intended lifecycle extends from launch to Ascended status, then toward HyperCore spot markets and eligible HIP-3 perpetual markets.

Ascend also uses part of its revenue to build a protocol-owned HYPE staking position. Ecosystem tokens earned from the yield of that position are burned, creating a recurring purchase-and-burn mechanism alongside user rewards. Ecosystem tokens purchased through the separate 30% ecosystem-buyback allocation are retained in Ascend’s treasury, with a small portion burned and treasury-held tokens used to help support eligible HyperCore listings.

Elysium provides the foundation for this approach: an Ethereum-compatible Layer 2 developed by Kinetiq that settles to HyperEVM and uses HYPE as its native gas asset. Its documented architecture includes a route from Elysium token markets toward HyperCore.

{% hint style="info" %}
**Ascend will not launch a protocol token.** Its economics are organized around supporting builders, participating users, HYPE, KNTQ, and qualifying ecosystem projects.
{% endhint %}

***

<figure><img src="https://content.gitbook.com/content/kBhQL4KtgFMdu4nj8Hn0/blobs/A25vz0lV443DRGtBxVhh/assets/ascend-logo.png" alt="ASCEND" width="96"><figcaption></figcaption></figure>


---

# 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://ascendlaunch.gitbook.io/docs/about-ascend.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.
