> 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/architecture-and-workflow/high-level-architecture.md).

# High-Level Architecture

Kazar's architecture is designed to offer **maximum flexibility for game developers** while keeping Web3 complexity completely invisible to the end user. Built on top of the **PWR Layer‑0 network**, Kazar inherits modular scalability, ultra-fast throughput, and low latency by design.

Core components include:

* 🧠 **Kazar Abstraction Layer**\
  A unified layer that abstracts wallets, gas, contract calls, and token interactions—making the user experience as seamless as Web2.
* 🔗 **Kazar Chain (EVM Layer-1 on PWR)**\
  The execution layer where games live. It offers smart contract compatibility, composable tooling, and blazing-fast throughput powered by PWR.
* 🚇 **PWR Layer‑0 Infrastructure**\
  Offers modular execution, cross-chain messaging, and up to **300,000 TPS**, making Kazar infinitely scalable for real-time gameplay.
* 🛡 **Security Core (MHBS + Proof of Power)**\
  All transactions benefit from **quantum-resistant multi-hash signature (MHBS)** and **Proof of Power consensus**, ensuring low overhead with high security.


---

# 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/architecture-and-workflow/high-level-architecture.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.