> 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-e.md).

# Part E

## <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 offer to the public of crypto-assets or their admission to trading

E.1 Public Offering or Admission to trading: ATTR

E.2 Reasons for Public Offer or Admission to trading: To provide utility and liquidity for token holders in the Sweat ecosystem.

E.3 Fundraising Target: Not applicable

E.4 Minimum Subscription Goals: Not applicable

E.5 Maximum Subscription Goal: Not applicable

E.6 Oversubscription Acceptance: false

E.7 Oversubscription Allocation: Not applicable

E.8 Issue Price: Determined by market conditions at launch

E.9 Currency for Issue Price: USDT

E.10 Subscription fee: 0

E.11 Offer Price Determination Method: Market-based pricing

E.12 Total Number of Offered/Traded Crypto-assets: 21,000,000,000 (initial supply)

E.13 Targeted Holders: ALL

E.14 Holder restrictions: None beyond compliance with applicable local regulations

E.15 Reimbursement Notice: Purchasers may be reimbursed if the offer fails or is canceled

E.16 Refund Mechanism: Not applicable (market-traded)

E.17 Refund Timeline: Not applicable

E.18 Offer Phases: Completed (token generation and initial sale in 2022)

E.19 Early Purchase Discount: DAO Maker participants received discounted allocations

E.20 Time-limited offer: false

E.21 Subscription Start: Not applicable

E.22 Subscription End: Not applicable

E.23 Safeguarding Arrangements: Sweat Wallet is a non-custodial onchain mobile wallet that uses NEAR blockchain security and account architecture with smart contracts being subject to security audits as well as ongoing bounty program using Immunifi service.

E.24 Payment Methods: Crypto only (e.g. USDT) via CEX/DEX

E.25 Value Transfer for Reimbursement: Not applicable

E.26 Right of Withdrawal: Not applicable for secondary market tokens

E.27 Transfer Method: Via blockchain transaction to the user’s wallet

E.28 Transfer Time: Immediate (on-chain confirmation)

E.29 Technical Requirements: Compatible wallet (Sweat Wallet, NEAR wallet, MetaMask)

E.30 CASP Name: KuCoin, Bitfinex, OKX, etc.

E.31 CASP Identifier: Not available

E.32 Placement Form: NTAV

E.33 Trading Platforms: KuCoin, Bitfinex, OKX, Uniswap, others

E.34 Market Identifier Codes: Not available

E.35 Access Conditions: Public, via exchange accounts

E.36 Involved Costs: Standard trading fees (platform-dependent)

E.37 Offer Expenses: Covered by treasury at launch

E.38 Conflicts of Interest: None declared

E.39 Applicable Law: BVI (issuer); Ireland (MiCA home Member State)

E.40 Competent Court: British Virgin Islands and/or EU competent courts


---

# 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-e.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.