> For the complete documentation index, see [llms.txt](https://web3-encyclopedia.gitbook.io/web3-encyclopedia/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://web3-encyclopedia.gitbook.io/web3-encyclopedia/evolution-from-web-1.0-to-web-3.0/current-limitations.md).

# Current Limitations

Despite the many benefits of Web3 in its current form, there are still many limitations that need to be addressed in order to allow this ecosystem to fully flourish.

#### Accessibility <a href="#accessibility" id="accessibility"></a>

Important features of Web3, such as logging in with Ethereum, are already available to use for free. However, the relative cost of **transactions is still too high** for many users. Web3 is less likely to be used in poorer developing countries due to high transaction fees. In Ethereum, these challenges are being addressed through [network upgrades](https://ethereum.org/uk/upgrades/) and [layer-2 scaling solutions](https://ethereum.org/uk/developers/docs/scaling/). The technology is ready, but we need higher levels of implementation at Layer 2 to make Web3 accessible to everyone.

#### Interaction with the user <a href="#user-experience" id="user-experience"></a>

The **technical barrier** to accessing Web3 is currently too high. Users must be aware of security issues, understand complex technical documentation and navigate complex interfaces. In particular, [wallet providers](/web3-encyclopedia/wallet/what-is-a-blockchain-wallet.md) are working on solving this problem, but better results are needed for the mass adoption of Web3.

#### Teaching <a href="#education" id="education"></a>

**Web3 introduces new paradigms** that require the study of other mental models than those used in Web2. A similar teaching procedure was necessary when Web1 gained popularity in the late 1990s: World Wide Web proponents used a variety of educational methods to educate the public, from simple metaphors (information traffic, browsers, Internet searches) to [television broadcasts](https://www.youtube.com/watch?v=SzQLI7BxfYI). The Web3 network is not complex, but it is different. Therefore, educational initiatives to teach Web2 users about Web3 paradigms are vital to its success.

#### Centralized infrastructure <a href="#centralized-infrastructure" id="centralized-infrastructure"></a>

The Web3 ecosystem is young and growing rapidly. As a result, it currently depends mostly on centralized infrastructure (GitHub, Twitter, Discord, etc.). Many Web3 companies are rushing to fill these gaps with decentralized alternatives, but **building quality and reliable infrastructure takes time**.


---

# 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://web3-encyclopedia.gitbook.io/web3-encyclopedia/evolution-from-web-1.0-to-web-3.0/current-limitations.md?ask=<question>&goal=<endgoal>
```

`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.