> 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/6.-partnerships-a-movement-powered-by-strategic-collaboration/6.1-near-protocol-the-engine-behind-sweats-scale.md). # 6.1 NEAR Protocol: The Engine Behind SWEAT’s Scale NEAR serves the foundational infrastructure of the Movement Economy. A high-performance engine that delivers the speed, scalability, and security SWEAT needs to serve tens of millions of users with seamless, low-cost transactions. Through NEAR’s **Chain Abstraction technology**, pioneered in its consumer facing implementation by Sweat Wallet, $SWEAT now operates as a true **multichain asset**, usable across Ethereum, BNB Chain, Arbitrum, and Base from a single NEAR account. Users can pay gas fees and interact across blockchains without friction, complexity, or a sense of insecurity. This positions $SWEAT as one of the most versatile, interoperable tokens in Web3, with **Bitcoin, Solana, TON, TRON** and more chain integrations on the horizon, that reach will only expand. NEAR’s infrastructure makes it all possible, delivering Web3 performance at Web2 speed and simplicity. --- # 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/6.-partnerships-a-movement-powered-by-strategic-collaboration/6.1-near-protocol-the-engine-behind-sweats-scale.md?ask=&goal= ``` `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.