> 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/why.md). # Why this mechanism PAPER cannot be bought. PaperStrategy is a way to own a growing share of it through a token that trades. ## PAPER is earned, not bought Papertrade's PAPER is minted only from trading losses. There is no pool to buy it from and no way to deposit into the LP. The only path to PAPER is to lose money on Papertrade, deliberately or not. Staked PAPER earns a share of the protocol's revenue in USDC. That makes it an income-producing asset that most people will never hold, because acquiring it takes capital, time and a method. ## A treasury that does it for the token PaperStrategy turns that into something tradeable: * **Capital** comes from the trade tax. Every trade of PSTR, in either direction, feeds the treasury. * **Method** is the strategy that runs the Papertrade accounts: it loses USDC in a controlled way to acquire PAPER at the lowest cost it can, and stakes everything. * **Return** goes to the token, not to the treasury: the yield buys PSTR on the market and burns it. There is nothing to claim and nothing to lock. Holding PSTR is holding a token whose supply shrinks as the treasury's PAPER earns. ## What it is not PSTR is not a share of the treasury and gives no claim on its PAPER or its yield. The only link between the two is the buyback. The treasury is not a vault you can deposit into. And the team holds no PSTR: it is paid in HYPE, from the tax and from the yield. --- # 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://docs.paperstrategy.xyz/why.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.