> For the complete documentation index, see [llms.txt](https://shiro.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shiro.gitbook.io/docs/the-vision-and-mission.md). # The Vision and Mission ### Vision Our vision is to merge the fun and accessible nature of video games with the burgeoning world of cryptocurrency, creating a platform that is both entertaining and lucrative. We aim to foster a robust ecosystem where gaming can be a source of income, and where the concepts of finance and fun coexist harmoniously. ### Mission Our mission is to provide a secure, enjoyable, and rewarding gaming experience, governed by the principles of fairness, transparency, and community participation. By leveraging blockchain technology, we are dedicated to introducing an economic model within Shiro that is sustainable, equitable, and incentivizes all stakeholders — from casual players to serious investors and developers. At the heart of our mission is the belief that the future of gaming is one where players are stakeholders in the ecosystems they contribute to, and where their time and skill are valued as real economic assets. --- # 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://shiro.gitbook.io/docs/the-vision-and-mission.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.