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

# Tokenomics

This section is dedicated to the $RKT token. It is REKT Games' native token and plays an essential role in guaranteeing the functionality and longevity of the ecosystem. This utility token is the only form of accepted payment within REKT Games and will be used to make transactions on the marketplace and the official store. Further, holders of $RKT will have a hand in governance of the ecosystem.  

$RKT token has the following use-cases: 

* Transacting on the marketplace 
* Minting NFTs 
* Purchasing Battle Pass 
* Play-and-earn  
* Participating in Governance 

The total supply of $RKT is fixed at 1,000,000,000 tokens. Initially, only a fraction of this supply will be available on the market with the rest set to unlock over a calculated period to guarantee the $RKT’s value.

Token Allocation & Vesting Schedule: 

| Pool           | Allocation | TGE  | Cliff (months) | Total Vesting(months) |
| -------------- | :--------: | ---- | -------------- | --------------------- |
| Foundation     |    12.5%   | 100% | N/A            | N/A                   |
| Seed Investors |    7.5%    | N/A  | N/A            | 36                    |
| Shareholders   |     20%    | N/A  | 6              | 36                    |
| Liquidity      |     10%    | 100% | N/A            | N/A                   |
| Treasury       |     40%    | N/A  | N/A            | 36                    |
| Team           |     10%    | N/A  | N/A            | 36                    |

After the complete timeline is elapsed, the total supply of $RKT will be in circulation. 


---

# 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.rektgames.io/whitepaper/platform-economy/tokenomics.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.