> For the complete documentation index, see [llms.txt](https://remittix-organization.gitbook.io/remittix-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://remittix-organization.gitbook.io/remittix-whitepaper/22.1-team-vesting.md).

# 22.1 Team Vesting

The team allocation represents 9% of the maximum RTX supply, equal to 135 million tokens.

These tokens are subject to an initial two-year vesting period. No team tokens become available during this period.

After the initial two years, the allocation is released gradually over the following four years.

The release schedule is structured as follows:

| **Period**    | **Team Allocation Available** | **Cumulative Availability** |
| ------------- | ----------------------------: | --------------------------: |
| First 2 Years |                            0% |                          0% |
| Year 3        |                           25% |                         25% |
| Year 4        |                           25% |                         50% |
| Year 5        |                           25% |                         75% |
| Year 6        |                           25% |                        100% |

This means the complete team allocation becomes available over a six-year period rather than being released immediately.

The purpose of the schedule is to maintain long-term alignment between the team and the development of the Remittix ecosystem.

The commencement date of the vesting period is defined within the official token documentation.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://remittix-organization.gitbook.io/remittix-whitepaper/22.1-team-vesting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.