# Problem Statement

The sharp drop in **Gaming UAWs (Unique Active Wallets)** throughout 2025 is not just a temporary dip. It’s part of a worrying multi-year trend. Despite the hype around Web3 gaming, fewer users are engaging, fewer games are launching, and studios are struggling to retain attention. 

**The data tells us:** 

*<mark style="color:red;">**We are not onboarding new users! We’re recycling the same ones, and even they are starting to leave!**</mark>*

But, This is not a user problem. It’s a system problem creating a flow where users do not want to stay long. Without radical shifts in experience, accessibility, and cross-game value, Web3 gaming risks fading into irrelevance. **The time to rebuild the foundation is now.**

<figure><img src="/files/mZNZlGm1jEq9yLBTy7Um" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://kazarhq.gitbook.io/kazarhq-docs/problems/problem-statement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.