> 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/decentralized-execution.md).

# Decentralized Execution

Unlike traditional L1s that rely on bloated validator sets and expensive gas, Kazar benefits from PWR’s **scalable, distributed consensus model** that ensures privacy and performance:

* ⚡ **Instant Finality**\
  Games don’t wait for blocks—PWR ensures sub-second confirmation and finality for transactions, even under high network load.
* 🔒 **Privacy via Parallel Execution**\
  Modular runtime and message separation ensure games can isolate execution while maintaining composability.
* 🧩 **Zero Bottlenecks in Game State**\
  Developers can sync game logic, asset ownership, and progression in real time—without relying on monolithic state machines.

Kazar effectively runs as a **decentralized gaming OS**, with PWR providing the foundational trust and throughput to support it at scale.


---

# 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/decentralized-execution.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.