> For the complete documentation index, see [llms.txt](https://docs.paperstrategy.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paperstrategy.xyz/the-token/launch-window.md).

# The launch window

The tax opens at 99% and drops one point per minute, so sniping the launch is pointless.

For the first 89 minutes of trading the tax is not 10%.

* It opens at **99%** the moment the pool is created.
* It drops **one point every minute**.
* It reaches **10%** after 89 minutes and stays there for good.

| Minutes after opening | Tax |
| --------------------- | --- |
| 0                     | 99% |
| 15                    | 84% |
| 30                    | 69% |
| 60                    | 39% |
| 89 and after          | 10% |

## Why

Bots that buy in the first seconds of a launch take a large share of the supply for almost nothing, then sell it on everyone else. Here a buy in the first minute keeps 1% of the tokens. The other 99% are tax sold back into the pool to fund the treasury. The price returns near its starting point, and the treasury starts with the fair launch tax money.

## What you will see on the chart

The tax being set in the token's contract, after a buy the taxed amount is sold back into the pool to then be sent to the treasury. After each buy the price spikes and falls back as the keeper sells their tax. This is the design working, not a dump by the team.

## Fixed in the contract

The schedule is set before the pool exists and starts when the pool is registered. Nobody can pause, change or restart it. The trade panel on the website shows the tax of the moment and the time to the next step.


---

# 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://docs.paperstrategy.xyz/the-token/launch-window.md?ask=<question>&goal=<endgoal>
```

`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.