> 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/team-and-distribution.md). # Team and Distribution Our team includes graduates of UC Berkeley (MSDS, MSCS, MFE) and Cornell (M.Eng. CS), with leadership experience across Cornell Blockchain and Blockchain at Berkeley. Team members bring professional experience across Alliance, YZi Labs, and Sigma Prime, alongside contributions to Olympus DAO and broader work across DeFi and onchain infrastructure. The team has also built and operated private trading communities for seven- to nine-figure traders, and maintain relationships across established trading communities and significant HYPE holders. These relationships support builder sourcing, launch coordination, and community distribution. This combination of technical and market experience at Ascend informs the product’s focus on liquidity, trading behavior, incentive design, and continued participation after launch. The objective is to provide builders with practical support while giving participants a clear understanding of how the system operates. --- # 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/team-and-distribution.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.