> For the complete documentation index, see [llms.txt](https://whitepaper.gemmest.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.gemmest.com/tokenomic-and-roadmap/gem-token-allocation.md).

# GEM Token allocation

### $GEM Allocation

***

| Token Allocation               | Token Amount | Percentage |
| ------------------------------ | ------------ | ---------- |
| **Angel & Ventures Investors** | 4.350.000    | 8.7%       |
| **Private Sale**               | 6.250.000    | 12.5%      |
| **Marketing**                  | 5.150.000    | 10.3%      |
| **CEX/DEX Listings**           | 10.000.000   | 20%        |
| **Team**                       | 2.500.000    | 5%         |
| **Ecosystem Fund**             | 7.500.000    | 15%        |
| **Staking Rewards**            | 10.000.000   | 20%        |
| **Strategic Partnerships**     | 3.000.000    | 6%         |
| **Airdrop**                    | 1.250.000    | 2.5%       |

### $GEM Vesting Schedule

***

| Token Allocation               | Token Release Schedule                                                 |
| ------------------------------ | ---------------------------------------------------------------------- |
| **Angel & Ventures Investors** | Unclock 30% cliff 6 month, vesting linear 10%/ month.                  |
| **Private Sale**               | 100% Unclock.                                                          |
| **Marketing**                  | During market growth base on the marketing strategy after cex listing. |
| **CEX/DEX Listings**           | 100% Unclock.                                                          |
| **Team**                       | 12 Months cliff followed by a 36-months linear unlock period.          |
| **Ecosystem Fund**             | 10% Unclock, monthly unclock 12 months.                                |
| **Staking Rewards**            | 15% Per month starting 1 months after listing.                         |
| **Strategic Partnerships**     | 12% Per month starting 6 months after listing.                         |
| **Airdrop**                    | 20% Unclock, monthly unclock 12 months.                                |

***

{% hint style="info" %}
NOTE
{% endhint %}

**Angle & Ventures Investors** -  Investment funds and individual investors providing capital for the early-stage project GEMMEST.

**Private Sale** - Private sale is a sale of coins or tokens to a limited number of early investors.

**Marketing/Ecosystem** - Supports Marketing and ecosystem growth through grants and projects.

**CEX/DEX Listings** - For Crypto trading, we normally get into the exchange market, in which people do coin exchanges with each other. 

**Team** - Part of motivation as well as maintaining team development.

**DAO Treasury** - Manages investments, legal costs, and financial necessities.

**Staking Rewards** - Staking is a way to earn $GEM rewards.

**Strategic Parnerships** - Alliances for Success. The Power of Strategic Partnerships in Business Strategy.

**Airdrop** - Distributes tokens to stimulate network participation and engagement.


---

# 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://whitepaper.gemmest.com/tokenomic-and-roadmap/gem-token-allocation.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.