# $FATTY TOKEN

{% hint style="success" %}

## Core $FATTY token Utilities: FatBot 50% Revenue Share + Ultimate Sniping 2.0 performance&#x20;

### **$FATTY: 50%** Revenue share token of FatBot

$FATTY token holders get a 50% Revenue share generated by FatBot (Eth, Sol, BNB)

### **$FATTY: Priority Voucher for Ultimate Sniping 2.0 Performance!**&#x20;

The more you hold, the faster the Speed of Sniping 2.0 (Strategy Copy Trading) you get!&#x20;
{% endhint %}

## $FATTY - your ticket for FatBot 50% Revenue share

$FATTY token holders receive a FatBot revenue share in ETH/SOL/BNB. This utility gives $FATTY holders a **direct revenue source, strongly supporting the $FATTY token demand** and long-term price value potential.&#x20;

{% hint style="success" %}

## **FatBot:** The Core $FATTY Token Product &#x20;

FatBot: **The greatest trading bot for Crypto**

Goal of the Product: **Generate revenues in ETH/SOL/BNB for $FATTY holders**&#x20;

FatBot Launch: **FatBot is LIVE!**&#x20;

Before the TGE: **Fatty AIRDROP (Shilling airdrop)**&#x20;

Alongside/After the TGE: **Fatty LEAGUES (Volume airdrops)**

Ticker: **$FATTY**&#x20;

Token Main Utility: **50% revenue share i ETH/SOL/BNB for $FATTY holders**<br>

VCs and institutional investors: **6 VCs signed and onboarded**

The biggest angel investor investment: **$140k**&#x20;

Matching listing criteria: **4 Tier 1 CEXs** **(Presale participants, VCs, Product)**&#x20;

Developer: **CleevioX - professional development studio (European Union)**&#x20;

Last update: **4th July 2025**
{% endhint %}

## THE OFFICIAL WEB:  &#x20;

{% embed url="<https://fatty.io>" %}
$FATTY official website
{% endembed %}


---

# 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.fatty.io/blockchain/usdfatty-token.md?ask=<question>
```

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.
