> For the complete documentation index, see [llms.txt](https://power-protocol.gitbook.io/power-protocol-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://power-protocol.gitbook.io/power-protocol-whitepaper/power-protocol.md).

# Power Protocol

**The Power Protocol is the infrastructure layer that makes blockchain entertainment scale**. More than a single title or studio, it’s an ecosystem that connects partners and players through consumer apps and data-driven live ops, all powered by $POWER.

<figure><img src="/files/J60fUHrg1LiNOk2ylmuQ" alt=""><figcaption></figcaption></figure>

Its purpose is to solve the hardest problems developers and IP holders face when launching crypto products:

* Managing live economies
* Designing sticky token-driven live ops
* Integrating fiat users seamlessly
* Capturing and recycling value on-chain

If Unity is a creation engine and Unreal is a rendering engine, **the Power Protocol is an economic engine**, the layer to make crypto entertainment sustainable and profitable. As adoption grows, every integration expands the $POWER economy, thereby compounding demand and strengthening the value of long-term holders.


---

# 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://power-protocol.gitbook.io/power-protocol-whitepaper/power-protocol.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.