> 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-loop/staking.md). # Staking and yield All PAPER is staked. Staked PAPER earns USDC from Papertrade. Every PAPER an account receives is staked on Papertrade. Nothing is held unstaked and nothing is sold. ## Where the yield comes from Papertrade pays stakers in USDC from the LP's revenue: a continuous share of what the LP earns, plus the LP's excess above its cap. The user pays nothing extra. How much it pays depends on Papertrade's activity, not on PaperStrategy. ## What happens to it The accounts claim the USDC and send it back to HyperEVM, into the dividend converter, which swaps it to HYPE and hands it to the buyback contract. The converter has no other exit, apart from a safety valve reserved to the owner for the case where the swap route breaks. See [Buyback and burn](/the-loop/buyback.md). ## What you can check Each account's staked PAPER and claimable yield are readable on Papertrade's contracts and interface, by address. The accounts are listed in the treasury contract. --- # 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-loop/staking.md?ask=&goal= ``` `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.