> For the complete documentation index, see [llms.txt](https://thealtitudeproject.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://thealtitudeproject.gitbook.io/docs/altitude-project/history.md). # Altitude History Altitude was originally created from frustration with other ecosystems where investors had seen projects abandoned or rugged. The earliest Altitude drafts go back to December 2022. The project was originally planned and tested for Binance Smart Chain, but Base became the home of Altitude's fair launch presale in February 2024. Altitude hit the market at `$0.00002015`, which remains the lowest price in the project's history. ## Original Token Model Altitude originally launched as a reflection token with a 10% tax. These taxes were split between: * Reflection rewards for holders. * Funding revenue streams. * Supporting early project growth. This model served the project well in the early days. However, after year one, the older tax-and-reflection model gradually faded away. ## Evolution After Year One Although the original reflection model was largely removed, Altitude kept its deflationary identity. The project moved toward a more up-to-date reward model, including USDC reward campaigns through Merkl. The combination of reduced supply, buybacks, burns, and ongoing development helped Altitude reach its all-time high of `$0.0008782` in August 2025, ending an 18-month uptrend. ## Challenges Along the Way Altitude has faced challenges, including issues with BaseSwap, OMNI DEX, and Merkl integration. These slowed momentum at times, but did not stop the project from continuing its journey. Altitude has continued to build from within, with the token supported by falling supply, project-owned activity, and a focus on developing native ecosystem products. --- # 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://thealtitudeproject.gitbook.io/docs/altitude-project/history.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.