> 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/1.-the-problem-the-bottleneck-of-web3-and-ai.md).

# 1. The Problem: The Bottleneck of Web3 and AI

Today’s decentralized networks are ironically reliant on centralized infrastructure.

* **Centralized RPCs:** Blockchain dApps rely on centralized RPC (Remote Procedure Call) nodes to read and write data to the blockchain. If these servers go down, the dApps stop working.
* **High Infrastructure Costs:** AI models and Web3 indexers require massive bandwidth to scrape and validate data, resulting in millions of dollars paid to corporate monopolies.
* **Hardware Barriers:** Traditional blockchain mining (Proof of Work) or validation (Proof of Stake) requires expensive GPUs or massive capital, shutting out the average user from participating in network consensus.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://lava-network.gitbook.io/lava-network-docs/1.-the-problem-the-bottleneck-of-web3-and-ai.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.