> 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.3-global-reach-infrastructure-built-for-inclusion.md).

# 5.3 Global Reach: Infrastructure Built for Inclusion

The Movement Economy was designed to transcend borders, languages, and cultures, ensuring that anyone, anywhere can participate. Through **Chain Abstraction**, $SWEAT operates seamlessly across NEAR, Ethereum, BNB Chain, Arbitrum, and Base, with plans to expand to Bitcoin, Solana, TON, and TRON in the near future. This multichain infrastructure makes $SWEAT a truly borderless asset, accessible to users regardless of their preferred blockchain.

Our **localization strategies**, **regional rewards**, and **global sports partnerships**, like RunGP powered by Global Running League further amplify our reach. Whether you’re a runner in Tokyo, a walker in Nairobi, or a hiker in the Alps, the Movement Economy meets you where you are, offering tailored experiences that resonate with your culture and lifestyle.

**This global footprint positions $SWEAT as a universal currency for movement, ready to onboard the next billion users into Web3.**


---

# 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.3-global-reach-infrastructure-built-for-inclusion.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.
