# Part D ## Information about the crypto-asset project D.1 Crypto-asset project name: Sweat D.2 Crypto-assets name: SWEAT D.3 Abbreviation: SWEAT D.4 Crypto-asset project description: Sweat captures the value of users’ physical movement into a proof-of-movement utility token ($SWEAT) using movement verification algorithms and offers utility of being able to access exclusive raffles, offers, services, staking rewards linked to the level of user’s physical activity, governance as well as ability to cover any blockchain fees on any supported blockchain making $SWEAT into the universal gas token and allowing users to “pay their fees with their feet”. D.5 Details of persons involved: Oleg Fomenko, Co-Founder & CEO D.6 Utility Token Classification: true D.7 Key Features of Goods/Services: Universal gas token, access to raffles, offers, services, trading, bridging, swapping and DAO governance. D.8 Plans for the token: Expand support for all the major blockchains (Bitcoin, Solana, Sui, Avalanche, Polygon, TON, etc. and enabling ability of $SWEAT to be universal gas token on those chains, add premium subscription service, launch fiat off-ramp (SweatPay), enable advanced AI multichain services, add support for Ledger and WalletConnect, expand the list of movement oracles enabling conversion of other types of physical activity (e.g. cycling, swimming, HIT, etc.) into $SWEAT, create of a data union giving token holders right to monetize their data. D.9 Resource Allocation: Foundation treasury \~27.7% of token supply reserved for future development D.10 Planned Use of Collected Funds or Crypto-Assets: Product and ecosystem development, marketing, partnerships, operations --- # Agent Instructions: 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: ``` GET https://whitepaper.swe.at/mica-compliant-white-paper/part-d.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.