> For the complete documentation index, see [llms.txt](https://docs.tryflox.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryflox.xyz/token/flox.md).

# FLOX token

**1,000,000,000 total supply. Fair launch. Nothing reserved.**

## Allocation

| Allocation           | Amount        |
| -------------------- | ------------- |
| Public / fair launch | 1,000,000,000 |
| Team                 | 0             |
| Investors            | 0             |
| Treasury             | 0             |
| Vesting cliffs       | None          |

100% of supply is public. Nothing is held back.

## The contract

The `FloxToken` contract has:

* **No mint function** — supply is fixed at deployment. There is no path to more.
* **No owner** — nothing to renounce later, because nothing was ever privileged.
* **No pause or blacklist** — transfers cannot be frozen for any address.
* **No transfer tax** — what you send is what arrives.

## Why it has to be this way

Flox exists to measure hidden supply overhang in other people's tokens. Shipping one with a hidden mint would be self-refuting.

The guarantees above are not marketing — they are the *absence* of code, verifiable by reading the contract. The same supply overhang Flox flags in the assets it watches is structurally zero in its own token, because the functions that would create it do not exist.

## Contract address

The FLOX contract address is published on the site at launch and listed in [Contracts](/reference/contracts.md). Always verify the address against the official site before interacting with it.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tryflox.xyz/token/flox.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.