> 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 ## **WATCoin Contract Address** **Contract Address:** EQCEqz2x3-Ub\_EO4Y5798NNoqKw1tP\_tJ6b9y-X0C4uvs8Zf **View WatCoin on CoinGecko:** {% embed url="" %} **Total supply:** \ 69,696,969,696 $WAT

$WAT allocation

**Initial Allocation:** \ **60%** of the total supply will go to the community at TGE and 3 months afterwards. 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. 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. When this pre-claim decision closed on Friday September 20th, **88%** of $WAT claimants were **MoonClub** Members.
--- # 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://wiki.gamee.com/whitepaper/watcoin/allocation-and-release-schedule.md?ask=&goal= ``` `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.