> For the complete documentation index, see [llms.txt](https://whitepaper-chi.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper-chi.gitbook.io/docs/welcome/problem.md).

# Problem

Most Web3 games fail to deliver the essentials: **lasting fun, a healthy economy, and a sense of belonging**.

Over 70% of Web3 games lose 90% of their volume within six months. The pattern is clear:

* Exclusive focus on “making money,” with little fun.
* **Inflationary economies**: infinite supply, lacking burning mechanisms or consistent utility.
* **Lack of identity and community**: players extract value and abandon the project.

The result? **Players join, extract value, and disappear.** Projects collapse.

Moreover, these games struggle to attract the mainstream Web2 audience, accustomed to **fast, intuitive, and integrated experiences**. While creating an account and playing is instant on traditional platforms, Web3 onboarding remains **bureaucratic and technical**, requiring wallet creation, private key management, and processes that cause insecurity.

This scenario discourages billions of potential users seeking **usability, security, and fun**, preventing Web3 games from evolving beyond a niche bubble and hindering **mass adoption** and sustainable growth.


---

# 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://whitepaper-chi.gitbook.io/docs/welcome/problem.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.