> 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/incentives-for-early-participants.md).

# Incentives for Early Participants

The earlier you join, the more you earn—with both impact and upside.

To accelerate ecosystem growth and reward the earliest contributors, Kazar has built a system of incentives for both **developers** and **players** participating in Initial Game Offerings (IGOs).

**For Developers:**

* 🏗️ **Grants from Ecosystem Pool**: Discounts in **KZT per game** can be granted from the DAO-governed Ecosystem Pool (40% of total supply), helping developers offset bonding costs.
* 🔁 **Low-Risk Entry**: Grants + bonding ensures developers have capital efficiency while still committing long-term.

**For Players:**

* 🎁 **Exclusive Rewards**: Early adopters of new games receive **airdrops, whitelists, or in-game assets** as part of launch campaigns.
* 💎 **First-Mover Advantage**: Engage early with IGO games to earn scarce rewards and early access to staking opportunities or rare NFTs.

By supporting early-stage innovation and rewarding early belief, Kazar creates a vibrant, **community-aligned launch environment**.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://kazarhq.gitbook.io/kazarhq-docs/initial-game-offering/incentives-for-early-participants.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.