> 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/vision.md). # Vision Ascend is being built around a straightforward commitment: the activity a project generates should help fund its continued growth. * Builders share in the revenue generated by their token’s activity. * Qualifying projects receive buybacks and visibility. * HYPE holders gain ecosystem exposure through airdrops funded only by their own staking yield and participate in a separate HYPE reward pool funded by protocol revenue. * Traders and community contributors can earn referral rewards by bringing activity to the platform. The protocol retains an operating budget while building a staked HYPE position that generates yield for recurring ecosystem buybacks for burning. Ecosystem tokens purchased through the separate 30% ecosystem-buyback allocation are retained in treasury, with a small portion burned and treasury-held tokens used to help support eligible HyperCore listings. Together, these mechanisms establish a framework for launching, supporting, and developing token markets within Elysium and the broader Hyperliquid ecosystem. **Our responsibility extends beyond launch day.** --- # 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/vision.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.