> For the complete documentation index, see [llms.txt](https://plan-a-labs.gitbook.io/metawara/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plan-a-labs.gitbook.io/metawara/tokenomics/vesting-plan.md).

# Vesting Plan

Token vesting prevents dumping and ensures long-term trust in the project.

| Category  | Cliff Period | Vesting Period   |
| --------- | ------------ | ---------------- |
| Presale   | None         | None             |
| Team      | 6 months     | 18 months linear |
| Staking   | None         | 22 months        |
| Liquidity | None         | None             |
| ECO       | None         | 5 years          |
| Marketing | None         | None             |

**Key Principles**

* Designed to protect early participants while promoting long-term commitment
* Staking rewards are fixed and distributed by block emission
* Marketing budget is released strategically, not front-loaded
* **A separate lock-up program for staking allocations will be announced during the presale period**
* **The lock-up program is intended to reduce sell pressure while offering rewards such as NFTs**


---

# 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://plan-a-labs.gitbook.io/metawara/tokenomics/vesting-plan.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.