> 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/overview.md).

# Project Overview

Altitude is a project built on Base. The Altitude token is the core of The Altitude Project.

From day one, the central idea has been to generate external revenue that supports the project, reduces supply, and rewards holders for their loyalty.

Altitude's long-term focus is built around:

* Reducing the circulating token supply through externally funded buybacks and burns.
* Building project-owned and Mountain-owned liquidity.
* Generating external revenue from ecosystem products and yield strategies.
* Rewarding loyal users through USDC reward flows and future ecosystem utilities.
* Continuing to build from within rather than relying only on third-party protocols.

After year one, most taxes were removed from the project. However, the core idea stayed the same: reduce supply with externally funded buybacks and burns while rewarding users for their loyalty.

This documentation covers Altitude's history, current token model, treasury approach, reward systems, Mountain Miner, the Everest Vault, security, and the future roadmap.


---

# 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/overview.md?ask=<question>&goal=<endgoal>
```

`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.