> For the complete documentation index, see [llms.txt](https://kazarhq.gitbook.io/kazarhq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kazarhq.gitbook.io/kazarhq-docs/initial-game-offering/revenue-for-buyback-and-burn.md).

# Revenue for Buyback and Burn

Kazar’s ecosystem is designed to **recycle value back into the token economy**. A portion of all IGO activity—along with marketplace transactions—is directed toward **KZT buyback and burn mechanisms**.

Key flows:

* 💸 **Marketplace Fees (2%)**: 50% of every fee is used to **buy back KZT and burn it**, while the other 50% is redistributed to stakers.
* 🔁 **Game Bonding Burns**: Each IGO permanently burns 10% of the bonded KZT, reducing overall supply.
* 📈 **Long-Term Deflation**: With over **5M KZT projected to be burned** through bonding and marketplace volume over four years, the circulating supply is capped at **800M KZT**, down from the original 1B.

These mechanisms **tie ecosystem activity directly to token value**, rewarding early participants and long-term holders.


---

# 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://kazarhq.gitbook.io/kazarhq-docs/initial-game-offering/revenue-for-buyback-and-burn.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.