> For the complete documentation index, see [llms.txt](https://guide.mochipool.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.mochipool.com/introduction.md).
# Introduction
In this guide, we'll begin by exploring the current landscape of the internet - Web2 - its pain points, and how the next generation - Web3 - intendeds to solve them. From there, we'll discuss the technologies enabling this movement, and how users can interact with them.
The concepts introduced in this section will be of fundamental importance as it touches upon the cornerstone values that we as a society value, moving increasingly towards digital dependence.
TL;DR
Web3 and its technologies are transforming the way we interact with money, data and digital assets. It’s the next generation of the internet that promises to be more decentralized, transparent, and secure than the current web. It introduces concepts of self-custody and digital ownership, which put you - the user - in control of your data and online interactions, instead of relying on centralized entities. In this guide, you will explore the fundamentals of Web3 and learn how it can unlock new opportunities in the digital era.
---
# 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://guide.mochipool.com/introduction.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.