> For the complete documentation index, see [llms.txt](https://docs.roxin.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roxin.network/what-is-roxin.md). # What is Roxin About Roxin Roxin is building infrastructure for transferring value between video games. Players create value inside games through time, skill, participation, purchases, and achievements. Today, most of that value remains locked inside one game. Roxin's goal is to let participating games recognize value created elsewhere while keeping control of their own economies. The **ROXIN token** is the value-transfer and governance asset of the Roxin ecosystem. ## Quick Facts * **Project:** Roxin * **Token:** ROXIN * **Network:** BNB Smart Chain * **Maximum Supply:** 200,000,000,000 ROXIN * **Stage:** Discovery / concept validation * **Website:** * **GitHub:** ## Documentation * [What is Roxin?](https://github.com/Roxin-network/docs/tree/main/what-is-it.md) * [How Roxin Works](/how-it-works.md) * [ROXIN Token](https://github.com/Roxin-network/docs/tree/main/roxin-token/README.md) * [Token Allocation](https://github.com/Roxin-network/docs/tree/main/roxin-token/token-allocation.md) * [Current Stage](/project/current-stage.md) * [Roadmap](/project/roadmap.md) * [Team](/project/team.md) * [Official Links](/official-links.md) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.roxin.network/what-is-roxin.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.