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

# FAQ

Short answers to the questions people ask.

**Is PaperStrategy part of Papertrade?** No. It is an independent project built on it, not affiliated with Papertrade or Hyperliquid.

**Does the team get tokens?** No. The team gets one tenth of the tax and 10% of the yield, in HYPE, never in PSTR.

**Can the tax go up?** No. It can only be lowered. The launch window is the only time it is above 10%, and it follows a fixed schedule.

**Why is the price falling right after launch?** Snipers who buy in the first minutes leave up to 99% of their purchase as tax. The keeper sells that tax back into the pool for the treasury, which brings the price back near its starting point. That is the anti-snipe design working.

**Do I earn anything by holding?** Not directly. The yield is not distributed; it buys PSTR on the market and burns it. Holding PSTR is holding a token whose supply shrinks.

**Can I deposit into the treasury?** No. The treasury is funded only by the tax.

**Where can I see the numbers?** On the website's dashboard, and on-chain: [Verify the numbers](/transparency/verify.md).

**What if an account on Papertrade stops working?** The treasury fills the next account in its list. Funds already inside Papertrade stay under the team's control and can be moved to another account.

**Is there a timelock?** Not at launch. The team's multisig controls the settings directly, so it can react fast in the first days; every action is a public transaction. A 48-hour timelock is planned once the system has run without incident.

**Why 10% tax?** Because the treasury is the whole point: the tax is what turns trading volume into a growing PAPER position, and the buyback brings the value back to the token.


---

# 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/reference/faq.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.