> 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/kazar-revenue-model/bonding-based-protocol-revenue.md).

# Bonding-Based Protocol Revenue

To launch any game on the Kazar ecosystem, developers are required to **bond 50,000 KZT tokens**. This isn’t just a fee, it’s a **skin-in-the-game mechanism** that filters out low-effort spam, ensures economic alignment, and kickstarts a long-term commitment to the ecosystem.

#### How It Works:

* Developers must **lock (bond)** 50,000 $KZT to register their game on-chain.
* This bonded amount is **non-transferable** while the game remains active and serves as:
  * **Access pass** to the Kazar SDK, AI tooling, and monetization engine.
  * **Gas pool** that subsidizes player interactions (claims, upgrades, purchases).
  * **Quality signal**—only committed devs deploy on Kazar.

#### Why It Matters:

* **No upfront cash required**, only token commitment → aligned with early-stage teams.
* **Deflationary Impact:** On exit or delisting, a percentage (e.g. 10–20%) of the bond is **burned or redirected** to the treasury, ensuring long-term value flow.
* **Predictable Token Demand:** As more games onboard, more KZT is locked → creating sustained buying pressure.

<figure><img src="/files/0VQskkujUZEpZc7bzpZE" alt="" width="563"><figcaption></figcaption></figure>

#### 💡 Example:

If 500 games launch in Year 1:\
`50,000 KZT * 500 = 25,000,000 KZT bonded`\
Even a 10% burn on exit leads to `2.5M KZT` permanently removed from supply.


---

# 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/kazar-revenue-model/bonding-based-protocol-revenue.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.