> For the complete documentation index, see [llms.txt](https://spaceguild.gitbook.io/sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spaceguild.gitbook.io/sg/space-guild/space-guild-details/market-opportunities/web-3-potential.md). # Web 3 Potential **We are now moving into web3 !** Web1 was where we read the internet, web2 is now where we can read and write to the internet and web3 is different in two ways. Not only can we read and write, but now ***we can also own things on the internet (via NFT tech)*** and our experience of the internet will move from two dimensions to three dimensions. They call web3 the embodied internet. Everything we do online, be it working, shopping or playing will become a 3D experience. **Hence, the market opportunity is massive.** The migration of our 2D internet experience to 3D will take some years to get to critical mass and will involve a variety of technologies. ***Much of the innovation which will affect the mainstream will come from the gaming industry which is leading the way in both user experience and business model revolutions.*** --- # 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://spaceguild.gitbook.io/sg/space-guild/space-guild-details/market-opportunities/web-3-potential.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.