> For the complete documentation index, see [llms.txt](https://minepro-1.gitbook.io/untitled-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://minepro-1.gitbook.io/untitled-1/further-information/long-term-vision.md). # Long term vision MinePro's goal is to continue building out our hosting arm and main platform in cohesion with each other. As we build out our hosting arm, the amount of ASIC's the DAO is earning from will continue to increase, while the total supply of $MINE will continue to decrease. Creating an economic enigma in doing so. Our goal at MinePro is to not only create synergy within the Bitcoin mining space, but the RWA space, and Web3 as a whole. Having a viable RWA platform on ICP will potentially open a world of adoption in defi to ICP. We would require the launching of all mining data infrastructure on the ICP network, which will in turn cross pollinate these project communities with the ICP ecosystem. In the next 2 years we plan to onboard a minimum of 50 hosting clients to the ecosystem. That’s 20% of rewards from 50 clients shared back to $MINE stakers every month. --- # 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://minepro-1.gitbook.io/untitled-1/further-information/long-term-vision.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.