> For the complete documentation index, see [llms.txt](https://whitepaper.memetheftauto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.memetheftauto.com/usdmta-token/tokenomics/vesting-schedule-at-a-glance.md).

# Vesting Schedule at a Glance

Maximum tokens that can be in circulation, assuming a fully subscribed presale and every claim tranche fully taken and released. Real circulation will be lower.

<table><thead><tr><th width="198"></th><th>Listing</th><th>Month 1</th><th>Month 3</th><th>Month 6</th><th>Month 12</th><th>Month 24</th></tr></thead><tbody><tr><td>Presale</td><td>130M</td><td>209M</td><td>330M</td><td>350M</td><td>350M</td><td>350M</td></tr><tr><td>Trading Pool</td><td>150M</td><td>150M</td><td>150M</td><td>150M</td><td>150M</td><td>150M</td></tr><tr><td>Community Claim</td><td>0</td><td>33M</td><td>100M</td><td>200M</td><td>200M</td><td>200M</td></tr><tr><td>Marketplace Reserve</td><td>0</td><td>0</td><td>25M</td><td>63M</td><td>138M</td><td>150M</td></tr><tr><td>Treasury</td><td>0</td><td>0</td><td>0</td><td>13M</td><td>38M</td><td>50M</td></tr><tr><td>Team</td><td>5M</td><td>11M</td><td>24M</td><td>43M</td><td>50M</td><td>50M</td></tr><tr><td>Marketing</td><td>5M</td><td>9M</td><td>16M</td><td>28M</td><td>50M</td><td>50M</td></tr><tr><td><strong>Total</strong></td><td><strong>290M (29%)</strong></td><td><strong>413M (41%)</strong></td><td><strong>645M (65%)</strong></td><td><strong>845M (85%)</strong></td><td><strong>975M (98%)</strong></td><td><strong>1B (100%)</strong></td></tr></tbody></table>

What the table shows: on listing day, 97% of what can circulate is either presale buyers or the permanently locked pool — the project's own allocations are 1% of supply. The two allocations spent on the project (Marketplace Reserve and Treasury) are the slowest to arrive, and the Treasury can't be touched for a quarter. Burns from unsold presale tokens, unused pool tokens, unclaimed rewards and marketplace sales reduce every number above permanently.

## What this means for you

**If you're in the presale:** you know your price, your limit, your unlock schedule and the listing price formula before you deposit. You know the pool can't be pulled. You know the community's free tokens arrive one‑sixth at a time, and no allocation the project controls can be sold faster than a tenth of weekly volume.

**If you're claiming:** your rate and price are fixed, you can verify whenever you're ready during the six months, your claim unlocks at the same pace as everyone else's, and the tokens you claim can only get scarcer — unclaimed tokens are burned, not redistributed.

**If you're buying on the market:** every schedule above is on‑chain and verifiable, the trading pool is permanent, and the marketplace turns every purchase into demand or a burn.

Short‑term, the design keeps listing day orderly. Long‑term, it keeps supply predictable, keeps the pool deep and permanent, and makes every burn — unsold, unused, unclaimed, and every marketplace sale — one‑way.

<table><thead><tr><th>Allocation</th><th width="488">Wallet</th></tr></thead><tbody><tr><td>Liquidity</td><td>A47SAfy8XbvVbHnUuuYkokLCqFHnZPAYXhMW6LKzmTA</td></tr><tr><td>Community Claim</td><td>WwD7JKU5iAAy557bF7qjkucphwZQhvsefVDUjfyFmTA</td></tr><tr><td>Marketplace Reserve</td><td>m3bbJCXvuGq2GCxtZVW6yDciBQfi81dWUzehWhmymTA</td></tr><tr><td>Treasury</td><td>WU6wBeL7U42KGChb2dHfC5KE6PKcbGpeUPfyz2xPmTA</td></tr><tr><td>Team</td><td>UWy6ybp8bVrL1AtPWkw5aLohZxyf2V3XtGodaPSEmTA</td></tr><tr><td>Marketing</td><td>kBvcShCcwJZKbqCf12obhSizPb8NkQpqcJUqGNQQmTA</td></tr></tbody></table>

Vesting contracts, the presale vault addresses and the pool address will be linked here as each goes live.

> *This document describes token mechanics. It is not investment advice, and nothing here is a promise of price or return.*


---

# 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://whitepaper.memetheftauto.com/usdmta-token/tokenomics/vesting-schedule-at-a-glance.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.