> For the complete documentation index, see [llms.txt](https://kazarhq.gitbook.io/kazarhq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kazarhq.gitbook.io/kazarhq-docs/problems/problem-statement/fragmented-userbase-and-limited-growth.md).

# Fragmented Userbase and Limited Growth

Web3 gaming continues to chase the same small pool of early adopters primarily crypto-native users. Despite years of development, **there’s been no real breakthrough in onboarding mainstream players.**

Each game builds its own wallet system, economy, and user loop forcing players to start from scratch every time. This **lack of interoperability** leads to fractured experiences, where progress, assets, and identity don't carry over. \
\ <mark style="color:red;">**The result? Low retention, shallow engagement, and no sense of ecosystem loyalty.**</mark>

Even with millions of wallets created, actual active users remain limited. According to DappRadar, **over 90% of Web3 games fail to maintain users beyond the first week**. \
\
***Studios aren’t growing the pie, they’re fighting over crumbs.***


---

# 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://kazarhq.gitbook.io/kazarhq-docs/problems/problem-statement/fragmented-userbase-and-limited-growth.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.