> 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/supply.md).

# Supply and fair launch

One billion PSTR, minted once, all of it in the pool at launch.

|              |                                                            |
| ------------ | ---------------------------------------------------------- |
| Name, ticker | PaperStrategy, PSTR                                        |
| Chain        | HyperEVM (chain id 999)                                    |
| Supply       | 1,000,000,000, minted once at deployment. No mint function |
| Market       | HyperSwap v2, PSTR / HYPE                                  |

## Fair launch

* The whole supply goes into the pool, paired with HYPE, in the same transaction that creates the token. The token's address does not exist before the pool is funded, so nobody can front-run it.
* No presale, no team allocation, no airdrop, no vesting. The team buys like everyone else.

## A supply that only goes down

The buyback contract burns every PSTR it buys. Nothing can mint. The current supply is readable on-chain (`totalSupply()`) and shown on the website; the difference from one billion is what has been burned.


---

# 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/supply.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.