> 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/5.-growth-opportunity/5.5.-revenue-streams-fueling-growth-funding-sustainability.md).

# 5.5. Revenue Streams: Fueling Growth, Funding Sustainability

The Movement Economy is built on more than token activity, it generates real, scalable revenue across multiple pillars:

* **Commercial Partnerships**\
  Global brands sponsor in-app commerce and rewards. In 2024 alone, users completed over **750,000 lessons** through partner campaigns, driving meaningful engagement and conversion.
* **Advertising Channels**\
  The Sweat Wallet’s ad network connects brands with one of the world’s largest health-focused audiences. In 2024, users watched **over 40 million rewarded video ads**, creating consistent and growing ad revenue.
* **Blockchain Fee Collection**\
  $SWEAT operates across chains, capturing fees from swaps, staking, and wallet interactions. As of Q1 2025, **hundreds of millions of on-chain transactions** have contributed to protocol-level revenue—fueling $SWEAT’s cross-network utility.
* **Blockchain Foundation Partnerships**\
  The Sweat Wallet has onboarded **tens of** **millions of verified on-chain users** in collaboration with top blockchain foundations—bringing unmatched scale and real human activity to Web3.

Each of these streams flows back into the ecosystem: powering product expansion, funding Foundation-led buybacks and burns (see Section 4.4), and reinforcing the utility of $SWEAT.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://whitepaper.swe.at/usdsweat-whitepaper/5.-growth-opportunity/5.5.-revenue-streams-fueling-growth-funding-sustainability.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.