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

# Part G

## <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 on the rights and obligations attached to the crypto-assets

G.1 Ownership: Controlled via user wallets

G.2 Access Rights: Enables product access, staking, raffles

G.3 Governance: 1-token holder–1-vote via DAO in-app

G.4 Liquidity: Traded on CEXs/DEXs globally

G.5–G.7 Termination, Redemption, Dividends: Not applicable

G.8 Buyback/Burn: DAO voted for token burn in the past, which were executed in line with community wishes.

G.9 Voting: SWEAT DAO on-chain voting

G.10 Rights Changes: Subject to DAO approval

G.11 Recovery: Not possible if keys are lost

G.12 AML/KYC: Required for fiat off-ramp and regulated exchange usage

G.13 Restrictions: Based on user location and law

G.14 Dispute Mechanism: Based on BVI law and DAO decisions

G.15 Termination Events: None defined

G.16 Legal Nature: Not a security, defined as utility token

G.17–G.19 Insurance, Security Claim, Risk: No guarantees; token value may fluctuate

<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-g.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.