> 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/fableborne-proof-of-success/onchain-value-capture.md). # Onchain Value Capture **Fableborne is designed to feed directly into the Power Protocol’s systemic value loop:** * A % of net in-app purchase revenue is automatically converted into $POWER via buybacks. So even traditional mobile players who never touch crypto can drive token demand. * A % of $POWER spent in the webshop (Diamonds, bundles, guilds, chests) flows into the treasury, gets burned, or is recycled into staking rewards, creating sustainable sinks that scale with activity. * Guild leaders and power users (whales) lock up large amounts of $POWER to create, expand, and compete. These long-term lockups reduce circulating supply, slow velocity, and amplify scarcity. * Secondary NFT trades (skins, items, Kingdoms) carry protocol fees, with a portion converted back into $POWER, adding incremental buy pressure every time assets are traded. Together, every player type, crypto-native, guilds, whales, or fiat casual, contributes to recurring $POWER demand. --- # 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/fableborne-proof-of-success/onchain-value-capture.md?ask=&goal= ``` `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.