> For the complete documentation index, see [llms.txt](https://whitepaper.pethereum.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.pethereum.io/pethereum-ticket-generator/buyback-mechanism.md). # Buyback Mechanism There will be regular $PETH buyback periods with the profit of Pethereum game. $PETH token will be bought by Loop Games from the market with Pethereum’s profit and create a staking rewards pool. Rewards of the users will be distributed from this pool. The percentage of profit that will be used in the buyback periods will be proportional to the ratio of Circulated Supply of $PETH to Total Supply of $PETH For example: The Total Supply of $PETH is 10 billion. If Circulated Supply of $PETH is 5 billion, and the profit of Pethereum is 10 million dollars. 5 million dollars, which is %50 of profit, worth $PETH will be bought from the market and allocated into the $PETH stake pool. --- # 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://whitepaper.pethereum.io/pethereum-ticket-generator/buyback-mechanism.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.