> For the complete documentation index, see [llms.txt](https://docs.hotspring.games/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotspring.games/introduction/pow2-proof-of-web2.md).

# PoW2 (Proof of Web2)

Before stepping into the on-chain ecosystem, Hot Spring was already validated in the Web2 landscape through strong user engagement and gameplay retention. As a cozy simulation IP, the game achieved:

* **Over 5 million organic downloads** across mobile platforms
* **Top-3 ranking** in simulation and lifestyle game categories in key Asian markets
* **Average session time of 18+ minutes per user**, indicating deep immersion
* **28-day D1 retention consistently above 40%**, highlighting habitual engagement
* A vibrant fan-driven content ecosystem, including UGC furniture packs, fan art, and room design competitions

These metrics not only reflect product-market fit, but also prove that Hot Spring resonates with a generation seeking comfort, expression, and emotional connection => values often overlooked in the broader gaming market.

This Web2 foundation provides both creative depth and operational stability as Hot Spring expands into a fully composable, AI-native simulation platform on-chain.

### **Proven Studio Execution in Traditional Markets**

Hot Spring is built by a game studio with over a decade of experience in the traditional gaming industry. The team has collectively launched multiple casual and simulation titles that have reached:

* **Over 100 million cumulative downloads**
* **High-performing user bases across Southeast Asia, Korea, and Japan**
* Partnerships with leading Web2 publishers, platforms, and art studios
* Successful monetization via IAP-driven economies with long-tail retention models
* Recognized IPs in simulation, idle RPG, and lifestyle genres

This operational maturity forms the backbone of Hot Spring’s ability to scale. Unlike experimental Web3-native teams, this studio brings battle-tested production pipelines, deep understanding of player psychology, and scalable infrastructure for managing both creative content and live operations.

### **The Mission: Onboard the Next 3 Billion Traditional Players**

The next evolution of Hot Spring is not just about Web3-native users. It is designed to **bridge the experience of traditional mobile and PC gamers into a new interoperable layer of digital life**.

To onboard the next 3 billion players, Hot Spring focuses on:

* **Familiar gameplay loops** powered by AI and social personalization
* **Frictionless onboarding** through account abstraction and invisible wallets
* **Optional on-chain layers** that add value, not complexity
* **Creator ecosystems** that empower players to become builders
* **Emotional continuity** that turns games into lifestyle anchors

*<mark style="background-color:green;">This is not a crypto game with players. This is a player-driven world => rebuilt from the comfort, trust, and creativity that traditional games got right, now composable and persistent by design.</mark>*


---

# 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://docs.hotspring.games/introduction/pow2-proof-of-web2.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.