> 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/community-claim-20.md).

# Community Claim 20%

200,000,000 $MTA

The Community Claim is the rewards pool for members who verify their Rockstar profiles. It is how the community that built Meme Theft Auto gets its share without buying in. Verification is an onboarding process, not a snapshot — members can verify at any point during the claim period and take part from the month they verify.

**How much:** $1.00 of $MTA for every 2,000,000 of your verified in-game cash earned (online only), converted at the official listing price fixed on listing day (at a $0.00667 listing, 2,000,000 cash earned = 150 $MTA). A typical member holding 35–70 million cash earned claims $17.50–$35 of $MTA. Maximum claim per verified profile: $1,000 of $MTA.. 

### **How It's Released:**

**Six monthly tranches, first come, first served.** The 200M pool is split into six equal tranches of 33.3M. The first opens 30 days after listing; one opens each month after that. Claims are instant: verify, claim, receive.

* When a month's tranche is used up, every verified member who hasn't yet been paid is placed in a queue in the order they verified, and is paid automatically the moment the next tranche opens. Verifying late never changes your rate — only the month you receive it.
* Whatever is left in a tranche rolls into the next month. **Whatever is left after month six is burned.**
* No more than one‑sixth of the pool can ever be released in a single month

**How each claim unlocks — the same for everyone, in dollars.** Every claim releases up to **$150 of $MTA (22,500 $MTA at a $0.00667 claim price) immediately, and another $150 every 30 days** until it's fully released.

| Claim size    | Day 0     | Day 30 | Day 60 | Day 90 | ...                       |
| ------------- | --------- | ------ | ------ | ------ | ------------------------- |
| $25 (typical) | all of it | —      | —      | —      |                           |
| $150          | all of it | —      | —      | —      |                           |
| $300          | $150      | $150   | —      | —      |                           |
| $6000         | $150      | $150   | $150   | $150   |                           |
| $1,000        | $150      | $150   | $150   | $150   | fully released by day 180 |

Most members' claims are fully liquid the day they receive them. Larger claims unlock at the same pace as everyone else's, so a member with a $1,000 claim can sell about the same dollar amount per month as a member with a $150 claim — nobody's position lets them move the market more than anyone else's.

#### **Why it's built this way.** 

Free tokens next to the trading pool are the largest single risk to the price of $MTA in year one. Three limits work together here: the monthly tranche caps how many claim tokens can exist each month (33.3M, about a fifth of the pool's tokens), the $150 step caps how many any one member can sell on a given day, and burning the remainder means the claim can only ever shrink supply. Each tranche is worth about $222,000 and covers roughly 6,000–12,000 claims at typical sizes, so in a busy month the queue is the safety valve: you keep your full rate and wait for the next tranche rather than being scaled down. Presale buyers can read every one of these limits before they deposit; claimers get the same rate, the same unlock pace and the same locked price regardless of when in the six months they verify.

#### Wallet: WwD7JKU5iAAy557bF7qjkucphwZQhvsefVDUjfyFmTA <https://solscan.io/account/WwD7JKU5iAAy557bF7qjkucphwZQhvsefVDUjfyFmTA><br>


---

# 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/community-claim-20.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.