> For the complete documentation index, see [llms.txt](https://docs.hypertrend.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hypertrend.xyz/the-problems-we-solve.md). # The Problems We Solve At HyperTrend we have identified and addressed the key issues that plague traditional crypto tokenomics: ### Traditional Token Failures: * Airdrop farming by users who immediately dump at launch * Insider manipulation creating post-airdrop crashes * VC selling pressure from staked locked tokens * DAO theater where insiders vote themselves benefits * Misaligned team incentives leading to early exits * Value extraction benefiting insiders over holders ### Our Approach Instead of relying on VC funding, we are community bootstrapped, just like Hyperliquid itself. ### Number-go-up Tokenomics To qualify as true "number-go-up" tokenomics, we need… 1. Real revenues flowing directly to token holders. 2. Hard currency rewards (USDC) not inflationary token emissions. 3. Deflationary supply by design. 4. Aligned team incentives through performance vesting. --- # 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://docs.hypertrend.xyz/the-problems-we-solve.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.