> For the complete documentation index, see [llms.txt](https://cryptodee.gitbook.io/ausd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cryptodee.gitbook.io/ausd/token-section/token-allocation.md).

# Token allocation

Tokenomics, a portmanteau of "token" and "economics," refers to the economic principles and design of a cryptocurrency or token within a blockchain ecosystem. It encompasses the factors that affect a token's value and use, including its creation, distribution, supply, demand, utility, and incentive mechanisms. Essentially, Tokenomics is the blueprint for how a token is designed to function within its specific blockchain environment

### 📊 Typical Ecosystem Allocation

AMANTARA (AUSD) have a 7,600,000 token supply

{% content-ref url="/pages/X50Bou0ivwVoFhF9W1ZA" %}
[Tokenomics](/ausd/token-section/tokenomics.md)
{% endcontent-ref %}

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

#### 📊 Token Allocation

| Category             | Allocation (%) |
| -------------------- | -------------- |
| Staking              | 25%            |
| Team & Founders      | 5%             |
| Marketing            | 10%            |
| Liquidity            | 30%            |
| Liquidity Lock       | 10%            |
| Supply Lock          | 10%            |
| Burn (Reduce Supply) | 10%            |
| **Total**            | **100%**       |

## Token allocation

Token allocation refers to the process of distributing a cryptocurrency project's native tokens among various stakeholders. This distribution is a crucial aspect of tokenomics and involves deciding how many tokens are allocated to different groups, such as the team, investors, advisors, community members, and the project's treasury. The allocation strategy is often outlined in the project's whitepaper or tokenomics document and is designed to align with the project's goals and ensure fairness and sustainability. Here's a more detailed breakdown:

* **Stakeholders:**&#x54;oken allocation involves determining how tokens are distributed among different groups with a vested interest in the project.&#x20;
* **Purpose of Allocation:**&#x54;he allocation strategy dictates the distribution of tokens for various purposes, including:
  * **Team:** Rewarding the core team for their work and dedication.&#x20;
  * **Investors:** Allocating tokens to private and public investors who contribute capital.&#x20;
  * **Community:** Encouraging community engagement and participation by distributing tokens.&#x20;
  * **Treasury/Reserves:** Setting aside tokens for future development, operations, and other strategic initiatives.&#x20;
* **Vesting Schedules:**&#x54;oken allocation often includes vesting schedules, which define how tokens are released to recipients over time, preventing a sudden influx of tokens into the market and ensuring long-term commitment.&#x20;
* **Fairness and Transparency:**&#x41; well-defined token allocation strategy is essential for maintaining fairness and transparency in the project's token distribution.&#x20;
* **Impact on Tokenomics:**&#x54;he initial token allocation significantly impacts the project's tokenomics, including its price, supply, and overall value.&#x20;


---

# 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://cryptodee.gitbook.io/ausd/token-section/token-allocation.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.