> For the complete documentation index, see [llms.txt](https://creoengine.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://creoengine.gitbook.io/whitepaper/creo-engine-token-creo/burning-mechanism.md).

# Burning Mechanism

1. Token burning will be implemented using the revenue generated from CreoPlay, a strategy that has proven successful in the past. This approach not only reduces our token supply but also fosters the expansion of our gaming ecosystem.
2. Our token supply reduction plan is characterized by a gradual approach, aimed at upholding a maximum total supply of 600 million tokens. This reduction strategy encompasses various methods, including burns from revenue, controlled team holdings, and well-planned buyback and burn initiatives. These measures are meticulously crafted to ensure the sustainability and controlled evolution of our token ecosystem.


---

# 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://creoengine.gitbook.io/whitepaper/creo-engine-token-creo/burning-mechanism.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.
