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

# Vesting Schedule

To protect the ecosystem from sudden sell pressure and to ensure long-term alignment, $AMARA allocations are released under structured vesting schedules. Each category has rules tailored to its role in the protocol’s growth.

**Partnerships**

* **Initial Release**: 1% unlocked at TGE (Token Generation Event).
* **Vesting**: Remaining tokens vest linearly over 24 months.

**Team**

* **Cliff**: Tokens are locked for the first 12 months.
* **Vesting**: Linear vesting over the following 36 months.

**Treasury / Operations Reserve**

* **Vesting**: Linear release over 36 months.

**Ecosystem Incentives**

* **Initial Release**: 3% unlocked at TGE.
* **Vesting**: Remaining tokens vest linearly over 24 months.

**Liquidity Allocations**

* **Release**: The majority of initial liquidity tokens (70% of supply) are unlocked at launch.


---

# 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.amara.exchange/tokenomics/vesting-schedule.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.