> For the complete documentation index, see [llms.txt](https://what-ai.gitbook.io/what-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://what-ai.gitbook.io/what-ai/getting-started/about-what-ai/problem-statement.md).

# Problem statement

The Web3 revolution promised a decentralized digital future, yet its adoption faces a critical roadblock: **ACCESSIBILITY**. This challenge manifests in several key areas:

1. Complexity Barrier: The technical intricacies of blockchain and DeFi protocols create a significant entry barrier for the average user. Complex wallet management, understanding gas fees, and navigating decentralized exchanges require a steep learning curve.
2. Multi-Platform Accessibility: One key challenge faced by many Web3 and DeFi solutions is their limited accessibility, which results from being confined to a single platform or interface. This can exclude a significant portion of potential users who may not be comfortable or familiar with that platform.
3. User Interface Challenges: Many DeFi platforms have unintuitive interfaces, making it difficult for non-technical users to navigate and utilize their services.
4. High Risk of User Error: The technical nature of blockchain transactions increases the risk of costly mistakes, such as sending funds to incorrect addresses or setting improper gas fees.
5. Limited Accessibility: Current DeFi interfaces often require specialized software or websites, limiting access for users in regions with restricted internet access or those who primarily use mobile devices.
6. Lack of Integration: DeFi services are typically isolated from users' daily digital experiences, requiring them to actively seek out and engage with separate platforms.
7. Complexity of Cross-Chain Operations: As the blockchain ecosystem expands, managing assets across multiple chains becomes increasingly complex for average users.
8. Global Accessibility Issues: Language barriers and varying levels of technological infrastructure worldwide limit the reach of existing Web3 solutions.
9. Security Concerns: The irreversible nature of blockchain transactions, combined with complex interfaces, increases the risk of costly user errors.
10. Adoption Bottleneck: These collective challenges create a significant bottleneck in the widespread adoption of Web3 technologies, limiting their transformative potential.

These challenges collectively hinder the mass adoption of DeFi and Web3 technologies, preventing a large portion of potential users from benefiting from decentralized financial services. There is a pressing need for a solution that can bridge the gap between the complex world of DeFi and the average user's daily digital experience, making blockchain-based financial services as accessible and user-friendly as traditional mobile banking apps.

In the next section, we will delve into our innovative solution, exploring how What AI tackles these challenges head-on to revolutionize the way users interact with Web3 technologies.

{% content-ref url="/spaces/EIt7r21dAbcPuYB2I286/pages/U4pxrBSIjE1nP0JL1Dps" %}
[Solution overview](/what-ai/getting-started/about-what-ai/solution-overview.md)
{% endcontent-ref %}


---

# 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://what-ai.gitbook.io/what-ai/getting-started/about-what-ai/problem-statement.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.