> For the complete documentation index, see [llms.txt](https://whitepaper.swe.at/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.swe.at/usdsweat-whitepaper/2.-the-movement-economy/2.6-consumer-crypto-leading-next-wave-of-web3-adoption.md).

# 2.6 Consumer Crypto: Leading Next Wave of Web3 Adoption

**Web3 was built to empower users, but users were missing—until now.** The blockchain world spent years perfecting its pipes, but forgot the people. That’s where $SWEAT steps in. With **20 million users**, **3 million monthly actives**, and **1.7 million monthly on-chain participants**, $SWEAT is leading the Consumer Crypto shift.

This isn’t about hype or speculation. It’s about real people using blockchain to unlock value from their daily lives. You’re not just a user, you’re a pioneer in an era where your habits turn into wealth. While most projects scramble for thousands, $SWEAT has millions already on board**, becoming Web3’s first truly mass-market consumer mobile product.**


---

# 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.swe.at/usdsweat-whitepaper/2.-the-movement-economy/2.6-consumer-crypto-leading-next-wave-of-web3-adoption.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.