# Token distribution

**Token allocation**

| Category                | Allocation                | token #       | %       |
| ----------------------- | ------------------------- | ------------- | ------- |
| Community (51%)         | Community treasure        | 440,000,000   | 44.00%  |
|                         | Airdrop\*                 | 70,000,000    | 7.00%   |
| Ecosystem (19.5%)       | Ecosystem & Development   | 145,000,000   | 14.50%  |
|                         | Foundation reserve        | 50,000,000    | 5.00%   |
| Investors (13.5%)       | Pre-seed                  | 60,000,000    | 6.00%   |
|                         | Private round (SEED)      | 50,000,000    | 5.00%   |
|                         | Private round (Strategic) | 25,000,000    | 2.50%   |
| Public (2%)             | Public Sale\*\*           | 20,000,000    | 2.00%   |
| Core contributors (14%) | Core team & Advisors      | 140,000,000   | 14.00%  |
|                         |                           | 1,000,000,000 | 100.00% |

\*The airdrop pool is planned for several seasons to ensure systematic rewarding of GG3 users. This means that the release of this pool will be spread over time and will not cause a sudden supply pressure. Season 1 already started!\
\*\*It will take place via launchpads

### Release schedule

<figure><img src="/files/Ocz69s483320RBOuGPYA" alt=""><figcaption><p>*All rounds have linear unlock</p></figcaption></figure>

### Token release schedule

<figure><img src="/files/UMQGQzUWQkLeeXQBNtJd" alt=""><figcaption></figcaption></figure>

**GGX token address:** \
**0x7bedaA6e5f43e1d83d667CfE770252a32532369E**\
Beware of scams!


---

# Agent Instructions: 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:

```
GET https://docs.gg3.org/ggx-tokenomics/token-distribution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.