> For the complete documentation index, see [llms.txt](https://stepgo-whitepaper.gitbook.io/stepgo-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stepgo-whitepaper.gitbook.io/stepgo-whitepaper/whitepaper.md). # 📄 Whitepaper In the StepGO universe, you are a digital explorer on the quest for incredible creatures. These creatures can be found in specific real-world locations, marked as "Tracks." Every step you take in real life translates into progress within the game, encouraging an active and healthy lifestyle. The blockchain technology breathes life into StepGO's unique token, StepGO (GO), initially based on the BEP-20 network with plans for future expansion to ERC-20. Players have the opportunity to collect NFTs (Non-Fungible Tokens) while exploring, and these NFTs can be utilized in exciting ways within the game. From creating unique NFTs to participating in challenges in our Arena, the fun and possibilities are limitless with StepGO's NFTs. Get ready for a one-of-a-kind experience where real-world exploration meets the innovation of cryptocurrencies. Join the StepGO explorer community and commence your journey right away! Website: Telegram Group: --- # 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://stepgo-whitepaper.gitbook.io/stepgo-whitepaper/whitepaper.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.