> For the complete documentation index, see [llms.txt](https://whitepaper.iskra.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.iskra.world/community-economics/token-economy.md). # Token Economy ### **Overview** The Iskra platform can be viewed as a "Hub" that is designed to support a variety of blockchain games. Many of our partner's games will be published on their own game chain(which will be a side chain of Iskra Hub chain), and all these game assets will be interconnected through the Iskra platform. As a Hub that connects multiple gaming ecosystems, Iskra helps its community members trade and exchange a wide array of in-game assets. There are three types of native tokens to support the Iskra ecosystem: * **ISK**: Native and Governance token of the Iskra ecosystem * **Settler NFT**: Non-fungible token which provides holders the right to participate in the Iskra ecosystem as a node operator --- # 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://whitepaper.iskra.world/community-economics/token-economy.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.