> 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/design-principles.md). # Design Principles ## Support should continue after launch Launch activity can generate significant trading volume and revenue, but that value often does not translate into continued support for the projects behind it. Sustained liquidity, development, and participation require mechanisms that extend beyond the initial launch. Ascend creates that mechanism by directing transaction fees toward defined uses: creator payments, ecosystem token purchases, protocol-owned staking, participant rewards, KNTQ purchases, and operations. This ensures that continued project support is built into the protocol’s economics. ## Ecosystem participation should not require selling a HYPE position Ascend’s staking model preserves exposure to HYPE through kHYPE while directing the staking yield into qualifying ecosystem tokens. The objective is to give HYPE holders a way to participate in ecosystem growth without requiring separate purchases of each project’s token. ## Incentives should have identifiable funding sources Creator payments come from the token’s trading fees. Referral rewards are paid from separate swap fees. Ecosystem token distributions to stakers are funded exclusively by the yield from users’ own kHYPE staking positions, not by protocol revenue. Direct HYPE rewards are allocated from HYPE purchased with protocol revenue. Ascend points program rewards come from the KNTQ purchased with protocol revenue. Every source is accounted for separately. ## No competing Ascend token A launchpad token introduces another asset competing for capital and attention. It also competes for the protocol’s own resources: revenue used to support that token is revenue that cannot be directed toward the broader ecosystem. Instead, Ascend directs value toward HYPE, KNTQ, qualifying ecosystem projects, and their participants. A dedicated operating allocation supports the team and infrastructure without requiring an Ascend token. --- # 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/design-principles.md?ask=&goal= ``` `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.