> For the complete documentation index, see [llms.txt](https://lava-network.gitbook.io/lava-network-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lava-network.gitbook.io/lava-network-docs/introduction.md). # INTRODUCTION ## LAVA NETWORK: The Decentralized Data Access & RPC Layer for the Web3 Economy ### **Executive Summary** The rapid expansion of Artificial Intelligence (AI) and the Web3 ecosystem demands an unprecedented amount of data validation, transaction routing, and computational resources. However, the current infrastructure relies heavily on centralized data centers (AWS, AWS, Google Cloud), leading to high costs, single points of failure, and censorship risks. **Lava Network** introduces a paradigm shift. Built on the principles of **DePIN (Decentralized Physical Infrastructure Network)**, Lava Network democratizes infrastructure by allowing anyone with an internet connection to turn their idle PC into a validator node. By leveraging a distributed network of everyday devices, Lava provides enterprise-grade, lightning-fast, and secure transaction routing while fairly rewarding its community in **$LAVA tokens**. --- # 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://lava-network.gitbook.io/lava-network-docs/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.