> For the complete documentation index, see [llms.txt](https://knowledge.shimanest.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.shimanest.com/readme.md).
# White Paper
Welcome to the world of Shima. Explore the official White Paper and discover the vision behind the Shima Protocol.
## **World Of SHIMANEST**
Shima is not just another blockchain project, it is a bridge between gaming, technology, and digital finance. In Shima, users embark on thrilling missions, invite friends, join competitive games, and interact with a dynamic ecosystem where play and profit go hand in hand. Powered by the SHIM token and its gamified counterpart GSHIM, every action in the platform can lead to real rewards, making the experience both entertaining and empowering.
Our vision is to build a unified digital universe where players are not only gamers, but stakeholders and decision-makers. From decentralized voting and staking, to token presales, leaderboard competitions, and a powerful asset dashboard, every feature is crafted with the user at the center. This whitepaper is your gateway to the full roadmap of Shima, so dive in and be part of the movement that is reshaping blockchain gaming.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://knowledge.shimanest.com/readme.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 `build a script that syncs our docs to a CMS` 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.
