# 4 First Path Validation
The Capybobo game is the first scenario where the protocol is put into practice.
We chose to validate the complete path of "extended lifecycle → deepened character relationships → IP accumulation" on our own game first.
***
#### 4.1 Real Users and Sustained Revenue
The game is live and continuously operating. Key metrics:
* Over 2.33 million registered users
* Over 36,000 paying users, \~1.6% conversion rate
* Daily active users (DAU) of approximately 23,000
* Cumulative revenue exceeding $3.59 million
These numbers mean: users are willing to pay consistently for characters and gameplay, the project is self-sustaining, and every protocol capability has a real business scenario to plug into.
***
#### 4.2 Future Development Path
Building on the existing operational foundation, the game will integrate protocol capabilities in phases:
* **AI Soul Engine** — Giving characters memory. Inject independent memory and personality evolution into Capybobo characters, enabling each player to build a one-of-a-kind relationship with their character.
* **On-chain Assets & Transparent Distribution** — Making the economy sustainable. Bring game assets on-chain, pair user deposits with assets to form LP; distribute revenue transparently via smart contracts to build long-term trust.
* **Physical Extension** — Taking characters beyond the screen. Extend characters into AI-chip-embedded designer toys and wearable devices — from being remembered in the game to being carried outside of it.
---
# 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://doc.capybobo.io/4-first-path-validation.md?ask=
```
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.