> 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/presale-vesting-and-round-multipliers.md).
# Presale Vesting & Round Multipliers
Presale tokens are delivered through the presale contract on a per‑round schedule. The rule is *discount buys time*: the cheaper the round, the slower its tokens reach the market.
Round
Unlocked at listing
Remainder
Fully unlocked
1
20%
Streams evenly over 120 days
Day 120
2
35%
Streams evenly over 90 days
Day 90
3
50%
Streams evenly over 60 days
Day 60
> Nothing is claimable before listing. Streams run continuously — there is no waiting for a monthly cliff.
**Value at listing.** With the presale fully subscribed, the pool opens at $0.00667. Measured against what each round paid:
| Round | Paid | Listing price | Value at listing |
| ----- | ------- | ------------- | ---------------- |
| 1 | $0.0010 | $0.00667 | 6.7× |
| 2 | $0.0030 | $0.00667 | 2.2× |
| 3 | $0.0040 | $0.00667 | 1.7× |
If the presale closes early with less raised, the pool is sized so the same pattern holds: at $400,000 raised, Round 1 lists at 4.0× and Round 2 at 1.33×; at $100,000, Round 1 lists at 1.25×.
**Why the schedule is fair to every round.** Round 3 buyers paid the most and get the fastest access: half their tokens the moment trading opens, the rest within two months, at a listing price 1.7× what they paid. Round 1 buyers paid the least and hold the largest paper gain, so their tokens arrive slowest — which is exactly what protects the price for Rounds 2 and 3. On listing day 130M of the 350M presale tokens are unlocked; the rest arrive over four months, cheapest last, at a combined pace of roughly 2.6M tokens a day — under 2% of the pool. Ordinary demand absorbs that. A single‑day free‑for‑all would not be absorbed by anything.
**If you buy in more than one round.** Each token keeps the schedule of the round it was bought in, so a multi‑round buyer's unlock is automatically the blend of those schedules — never the sum of them, and never the fastest one applied to everything. For buyers who take the full limit in each round:
| Rounds bought | Total $MTA | Unlocked at listing | Day 30 | Day 60 | Day 90 | Day 120 |
| ------------- | ---------- | ------------------- | ------ | ------ | ------ | ------- |
| 1 + 2 + 3 | 3,125,000 | 40% | 64% | 87% | 97% | 100% |
| 2 + 3 | 2,625,000 | 44% | 68% | 92% | 100% | — |
| 1 + 3 | 2,125,000 | 43% | 67% | 91% | 95% | 100% |
| 1 + 2 | 1,500,000 | 30% | 51% | 72% | 93% | 100% |
| 3 only | 1,625,000 | 50% | 75% | 100% | — | — |
| 2 only | 1,000,000 | 35% | 57% | 78% | 100% | — |
| 1 only | 500,000 | 20% | 40% | 60% | 80% | 100% |
The table shows the largest possible position at each step: the biggest buyer in the presale can have 40% of their tokens available on listing day and nothing more, and nobody's vesting is longer than 120 days.
> *Listing price is set by the pool ratio on listing day. Market price after listing is set by trading and is not guaranteed.*
---
# 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/presale-vesting-and-round-multipliers.md?ask=&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.