> 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/mica-compliant-white-paper/2025-white-paper-superseded/part-f.md).

# Part F

## <mark style="color:$primary;">Historical version</mark>

<mark style="color:$primary;">Historical version — no longer valid. This page forms part of the SWEAT white paper dated 20 August 2025, superseded by the modified white paper published on 13 October 2026. It is retained for historic</mark>

## Information about the crypto-assets

F.1 Crypto-asset Name: SWEAT

F.2 Symbol: SWEAT

F.3 Token Type: Utility Token

F.4 Blockchain: NEAR Protocol (native); bridged to Ethereum, BSC, Polygon, Arbitrum, and more

F.5 Contract Address: token.sweat (native to NEAR Protocol - <https://nearblocks.io/address/token.sweat>)

F.6 Fungibility: true

F.7 Supply Cap: No hard cap; increasing mint difficulty over time

F.8 Total Supply (as of July 2025): \~11.8 billion

F.9 Allocation Breakdown:

Lockdrop: 25%

Foundation Treasury: 27.7%

SweatCo: 22%

Team: 10.92%

Ecosystem: 7.02%

Private Sale: 3.33%

Seed Sale: 2.68%

Public Sale: 1.33%

F.10 Rights Attached: App rewards, staking, governance, redeemable for services

F.11 Redemption Right: Not applicable

F.12 Voting Rights: One-token holder–one-vote via SWEAT DAO

F.13 Profit Sharing: None

F.14 Transfer Restrictions: None, except jurisdictional compliance

F.15 Interoperability: Bridges to Ethereum, BSC, Arbitrum, Base, and more

F.16 Smart Contract Audits: Yes, externally audited

<br>


---

# 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/mica-compliant-white-paper/2025-white-paper-superseded/part-f.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.