> 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/project/current-stage.md). # Current Stage Where we are now Roxin is currently in the discovery stage. We have defined the initial product thesis and are validating it with game developers, potential partners, and early investors. The core question we are testing is whether game developers are willing to recognize value created in another game under rules they control. Our next milestone is a controlled pilot between a small number of games. Roxin is raising a pre-seed round to support this validation and the development of the first pilot. ### What Exists Today Current work includes: * the [$ROXIN](https://bscscan.com/token/0x9fAA7d1E5722209e1bEa5A857261F0e01aA79096) token on BNB Smart Chain * the official [Roxin website](http://localhost:5173/) * public project documentation * token purchase infrastructure * [smart contracts](https://bscscan.com/address/0xA2881B63D8a6cE1d6fdA985aEFCAbA8509F9895f) * early ecosystem and product design * developer and partner discovery ### What We Are Building The next major objective is to demonstrate real value transfer between participating games. The first useful implementation should be intentionally small: * a small number of games * one clearly defined value route * explicit limits * measurable player usage * developer-controlled rules ### Why Start Small? Cross-game value affects game economies. It should therefore be introduced carefully. Before expanding the network, Roxin needs evidence that portable value: * is useful to players * creates value for game developers * does not damage game balance * can be integrated reliably * can operate economically at scale The current priority is proving these assumptions. --- # 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://docs.roxin.network/project/current-stage.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.