> For the complete documentation index, see [llms.txt](https://poolfans.gitbook.io/poolfans-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://poolfans.gitbook.io/poolfans-docs/poolfans/fans-token.md).
# $FANS
## $FANS Token
### Supply & Initial Distribution (launch via Clanker)
**100B total.**
* **70% Liquidity Pool (Uniswap v4).**
* **25% Creator Vault (30-day lock → 30-day vest).**
* **5% Community Airdrop (1-day lock → 7-day vest).**
* **0% Dev buy.**
### Utilities
**Access:** creators need 1,000,000 $FANS to launch pools (governance-modifiable).
**Staking:** multi-asset yield. Receives platform-level protocol share from all Fee Tokenizers (WETH + launched tokens + $FANS).
**Weekly Mining:** participation-weighted issuance drawn from Creator Vault once vesting starts.
**Power-ups:** spend $FANS for boosts; spending routes revenue back to stakers.
### System flywheel
**Spend $FANS → protocol revenue → staker rewards.**
**Stake $FANS → earn WETH + $FANS + long tail of launched tokens via Tokenized Fees.**
**Participate/Create → earn mining power → more $FANS.**
---
# 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://poolfans.gitbook.io/poolfans-docs/poolfans/fans-token.md?ask=&goal=
```
`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.