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

# Allocation & Release Schedule

The supply, allocation and distribution of $WAT

## **WATCoin Contract Address**

**Contract Address:** EQCEqz2x3-Ub\_EO4Y5798NNoqKw1tP\_tJ6b9y-X0C4uvs8Zf

**View WatCoin on CoinGecko:**

{% embed url="<https://www.coingecko.com/en/coins/watcoin>" %}

**Total supply:** \
69,696,969,696 $WAT

<figure><img src="https://2958752009-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MO2G2x2wM_1hfAYzSqY%2Fuploads%2FNCIYrkBAseH7uIiNY1bN%2FScreenshot%202024-09-20%20at%2017.42.19.png?alt=media&amp;token=3bbc4517-b4c7-41d1-9775-49b3f2b9d3da" alt=""><figcaption><p>$WAT allocation</p></figcaption></figure>

**Initial Allocation:** \
**60%** of the total supply will go to the community at TGE and 3 months afterwards.&#x20;

A further **12%** will go to the community as future rewards, meaning **72%** of the total supply (41,818,181,818 $WAT) is allocated to the community ecosystem.

The **40%** not distributed at TGE (or 3 months afterwards) is allocated as follows:

**Future rewards:** 12%

**Ecosystem Development:** 11%

I**ncubation pool (market making, launch pools, exchanges, etc.):** 9%

**Marketing:** 3%

**Advisory:** 5%

Note that not all of these are unlocked at TGE. See image above.

Prior to TGE, $WAT claimants were able to choose whether to receive $WAT in their connected wallet or to the Bitget exchange.&#x20;

Claimants could also choose between **SOLO FLYER (Claim Now)** and **MOONCLUB MEMBER** options, determining the amount of $WAT they would receive, as well as eligibility for additional perks.&#x20;

When this pre-claim decision closed on Friday September 20th, **88%** of $WAT claimants were **MoonClub** Members.

<figure><img src="https://2958752009-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MO2G2x2wM_1hfAYzSqY%2Fuploads%2FTNsDHsNJpCCtwiXwbxrm%2FScreenshot%202024-09-20%20at%2017.42.36.png?alt=media&amp;token=aa9ee97a-b769-4623-a86b-fb1163715bc1" alt=""><figcaption></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 by asking a question.

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

```
GET https://wiki.gamee.com/whitepaper/watcoin/allocation-and-release-schedule.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.