> For the complete documentation index, see [llms.txt](https://docs.auralaunch.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.auralaunch.org/usdaura/aura-tokenomics.md).

# AURA Tokenomics

The total supply of AURA tokens is strictly capped, with the maximum issuance fixed permanently at 500 million units. This finite supply model is maintained to ensure the long-term scarcity of the asset, providing a predictable economic foundation for all participants and protecting the integrity of the token's valuation within the broader ecosystem.

<figure><img src="/files/vyx5iiVxcj2qIUTNTgXD" alt=""><figcaption></figcaption></figure>

## AURA Supply Allocation

### Community (35%)

The AURA community allocation is strategically structured to fulfill several core ecosystem objectives.

This allocation is primarily dedicated to the implementation of retroactive programs designed to formally recognize and reward early contributors, as well as to provide equitable compensation to creators who dedicate their efforts toward developing valuable content or technical tools that enhance the network.

Central to this initiative is the [AURA Airdrop ZERO program](/usdaura/aura-airdrop-zero.md), which serves as a comprehensive rewards mechanism for early adopters and participants of the incentivized Testnet. Furthermore, a portion of this allocation is reserved to provide necessary liquidity for staking rewards, ensuring the ongoing health and sustainability of the staking program for all active participants.

### **Foundation & Ecosystem Growth (27.8%)**

The foundation allocation of AURA is reserved to be held and managed by the foundation, specifically to provide the necessary resources for the ongoing development, operational maintenance, and long-term sustainability of the Aura Protocol. Parallel to this, the ecosystem allocation is strategically aimed at scaling the breadth and reach of the Aura ecosystem, primarily by funding and supporting vital community and growth initiatives. This includes the provision of bounties to drive innovation, the formation of strategic partnerships to expand network influence, and the continued investment in high-impact research and development efforts to advance the protocol's capabilities.

### **Investors (20.2%)**

The investor allocation accounts for 20.2% of the total token supply, reserved for early supporters who are subject to a structured 18-month vesting schedule. Under these terms, 10% of the allocated tokens are released at TGE, with the remaining balance distributed incrementally across the following 18 months.

### **Contributors (17%)**

The contributor allocation, representing 17% of the total supply, is dedicated to core contributors who operate under a 6-month vesting period. This distribution framework entails an initial release of 40% at TGE, followed by the systematic release of the remaining tokens over the course of the 6 subsequent months, ensuring alignment between long-term contributor commitment and the protocol's development trajectory.


---

# 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.auralaunch.org/usdaura/aura-tokenomics.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.
