> For the complete documentation index, see [llms.txt](https://docs.takadao.io/takadao-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.takadao.io/takadao-docs/taka-tokenomics-litepaper-v1/taka-tokenomics-in-brief/lock-up-and-vesting-schedules-team-and-investors.md).

# Lock-up and Vesting Schedules (Team and Investors)

Vesting period: 3 years | 36 months

Cliff: 1 year

| Time           | % of total allocation vested |
| -------------- | ---------------------------- |
| 0 - 11 months  | 0                            |
| 12 months      | 25% after 12 months          |
| 13 - 36 months | 3.125% per month             |

Team and investors will vest over the period of 3 years with a 1 year cliff. In other words, the team and investors will get nothing in the first year after initial supply issuance. After year 1, the team and investors will receive 25% of their total allocated tokens. Subsequently, each month, they will receive an additional proportional amount of allocated tokens up until the vesting period of 3 years or 36 months is completed.


---

# 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.takadao.io/takadao-docs/taka-tokenomics-litepaper-v1/taka-tokenomics-in-brief/lock-up-and-vesting-schedules-team-and-investors.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.