> 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/chain-level-infra-revenue.md).

# Chain-Level Infra Revenue

**📦 Dev-Funded Execution Layer**\
Each game integrated into Kazar contributes to the pool via:

* **Initial Game Bonding** (50,000 KZT per title)
* **Small % of live game revenue** (auto-routed)
* **Optional top-ups for higher-volume games**

***

**⚙️ Invisible UX = Retention Flywheel**\
Players never see gas prompts. Actions like login, mint, upgrades, and reward claims execute instantly. This smooth UX, Increases retention and Encourages more in-game transactions and making onboarding for non-crypto users effortless

***

**🚀 PWR Layer-0 Acceleration**\
All activity runs on **Kazar Chain**, secured by **PWR**:

* Modular Layer-1 scalability
* Sub-second finality
* Cross-game composability with shared wallet infra

***

**♻️ Self-Sustaining Infra Model**\
The pool is **constantly replenished** by growing game adoption:

* More games = more bonding
* More activity = more pooled rev
* No external dependency on public RPCs or manual gas payment logic


---

# 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/chain-level-infra-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.