> For the complete documentation index, see [llms.txt](https://docs.sopdap.com/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sopdap.com/whitepaper/overview/3.0-token-details/3.1-token-supply-and-distribution.md).

# 3.1 Token Supply and Distribution:

The total supply of Sopdap AI Tokens is 3 Billion, which will be distributed as follows:

* 1.5% Presale Sale&#x20;
* 48.5% EcoSyestem & CEX Listing&#x20;
* 25% Treasury Locked&#x20;
* 8% Team & Future Employee&#x20;
* 5% Investors&#x20;
* 2% Advisor & Legal&#x20;
* 5% Marketing and Partnership
* 5% Utility Platform Dev & Research

| Items                           | Percentage | Remark               | Amount        |
| ------------------------------- | ---------- | -------------------- | ------------- |
| Public Sale & Exchange Listing  | 48.5%      | Vested for 5 years   | 1.455 Billion |
| Team and future employee        | 8%         | Vested for 5 years   | 240 Million   |
| Presale sale                    | 1.5%       | Introduce to Market  | 45 Million    |
| Advisor                         | 2%         | Vested for 5 years   | 60 Million    |
| Investors                       | 5%         | Vested for 5years    | 150 Million   |
| Utility Platform Dev & Research | 5%         | Vested for 5years    | 150 Million   |
| Marketing and Partnership       | 5%         | Vested for 5years    | 150 Million   |
| Treasury/Reserved               | 25%        | FixedLock for 5years | 750 Million   |

*Table: 3.1.1 Tokenomics and Distribution*

#### Overall Tokenomics Chart

<figure><img src="/files/PFa31nHjxhPTJZFBhXqg" alt=""><figcaption><p><strong>Figure 3.1.1 : Tokenomics Chart</strong></p></figcaption></figure>

#### 3.1.1 Sub Distribution of 47% Allocated to Ecosystem and Exchange Listing

| <p> 48.5% of the Ecosystem and Exchange Listing (1.410 Billion)</p><p> </p> | <p> </p><p>Percentage </p><p> </p> |
| --------------------------------------------------------------------------- | ---------------------------------- |
| <p> </p><p><em>Liquidity pool</em> </p><p> </p>                             | <p> </p><p>5.5%</p><p> </p>        |
| <p> </p><p><em>Staking pool</em> </p><p> </p>                               | <p> </p><p>15%</p><p> </p>         |
| <p> </p><p><em>CEXs listing</em> </p><p> </p>                               | <p> </p><p>20%</p><p> </p>         |
| <p> </p><p><em>Dexs listing</em></p><p> </p>                                | <p> </p><p>3%</p><p> </p>          |
| <p> </p><p><em>Community Building</em></p><p> </p>                          | <p> </p><p>5%</p><p> </p>          |
| <p> </p><p><em>CEXs Competition</em></p><p> </p>                            | <p> </p><p>3%</p><p> </p>          |
| <p> </p><p><em>TOTAL</em></p><p> </p>                                       | 47%                                |

<figure><img src="/files/ZapT12NAAX7C8AMuOCdP" alt=""><figcaption><p><strong>Figure: 3.1.2 Sub distribution of community token</strong></p></figcaption></figure>


---

# 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.sopdap.com/whitepaper/overview/3.0-token-details/3.1-token-supply-and-distribution.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.
