> For the complete documentation index, see [llms.txt](https://docs.playstoken.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playstoken.com/tokenomics/usdplays/token-burns.md).

# Token Burns

We are implementing various mechanisms to burn tokens strategically, thereby reducing the overall token supply and enhancing scarcity. Token burning will occur through several channels, including a percentage of the real revenue generated, platform usage fees, NFT sales, and community-driven initiatives. Additionally, a portion of tokens allocated to reserves may be periodically burned.

{% hint style="info" %}
We plan to implement token burning as buybacks, where a portion of project revenue will be allocated to repurchasing and subsequently burning tokens from the market. 
{% endhint %}

*By implementing a multifaceted approach to token burning, we strive to create a deflationary ecosystem that rewards long-term token holders, enhances scarcity, and contributes to sustainable value appreciation over time.*


---

# 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.playstoken.com/tokenomics/usdplays/token-burns.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.