# Welcome to Fanbase

## The Future of Creator Monetization

Fanbase is rebuilding the creator economy on blockchain—eliminating the 20-30% fees, delayed payouts, and privacy concerns that plague traditional platforms.

**Core Benefits:**

* **Creators:** Keep 100% of earnings (zero fees when staking $FAN)
* **Fans:** Private crypto payments + staking rewards
* **Token Holders:** Governance rights + up to 105% APY staking

{% hint style="success" %}
**Fanbase is a working platform with real creators and revenue—now getting tokenized.**
{% endhint %}

***

## The Opportunity

The creator economy is **$100 billion annually**, but traditional platforms extract massive value:

* OnlyFans charges 20% fees
* Payouts take 7-30 days
* Privacy risks with fiat payments
* Geographic restrictions exclude billions

**Blockchain solves these problems. Fanbase delivers the solution.**

***

## Token Launch Highlights

| Metric                | Value                      |
| --------------------- | -------------------------- |
| **Total Supply**      | 1,000,000,000 $FAN (fixed) |
| **ICO/Presale Price** | $0.10 per token            |
| **FDV**               | $100M                      |
| **ICO/Presale Raise** | $5M                        |
| **Day 1 Circulating** | 25%                        |
| **Staking APY**       | Up to 105% Year 1          |
| **Team Vesting**      | 5 years (12-month cliff)   |
| **LP Strategy**       | Burned (permanent)         |

***

## What Makes Fanbase Different

### 1. Zero Fees for Stakers

Stake $FAN tokens to eliminate all platform fees. Creator earning $10K/month saves $24K/year compared to traditional platforms.

### 2. Instant Blockchain Payments

Crypto payments settle in seconds. No banks, no delays, no intermediaries.

### 3. Working Product

Unlike projects launching tokens before product, Fanbase already operates with real creators and revenue.

### 4. Community-Owned

60/40 community/insider split with governance voting on protocol changes and treasury allocation.

### 5. LP Burned

Liquidity permanently locked—rug pull mathematically impossible.

***

## For Creators

**Maximize Earnings:**

* Keep 100% of revenue (0% fees when staking)
* Instant crypto payouts
* Set your own pricing
* Multi-chain support (Ethereum + Base)

***

## For Token Holders

**Staking Rewards:**

* Up to 105% APY Year 1
* 5-year rewards program (350M tokens)
* Zero platform fees when staking

**Governance Rights:**

* Vote on protocol changes
* Direct treasury spending
* Shape platform evolution

**Strong Fundamentals:**

* 12-month team cliff + 5-year vesting
* LP burn = no rug pull
* 25% Day 1 float (healthy)
* Working product with revenue

***

## Getting Started

### 1. Learn About Fanbase

Explore this whitepaper to understand the platform and vision.

### 2. Participate in ICO/Presale

$0.10 per token—early access pricing before DEX launch.

### 3. Stake Your Tokens

Earn rewards and unlock zero-fee platform access.

### 4. Join the Community

Connect with creators, fans, and token holders building Web3 creator economy.

***

## Next Steps

* [**The Problem →**](/introduction/the-creator-economy-problem.md) Why traditional platforms fail
* [**The Solution →**](/introduction/the-fanbase-solution.md) How Fanbase fixes it
* [**Tokenomics →**](/tokenomics/overview.md) Deep dive into $FAN economics
* [**ICO/Presale →**](/ico-presale/ico-presale-details.md) How to participate

***

*Built by creators, for creators. Powered by blockchain. Owned by the community.*


---

# 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://docs.fanbase.com/introduction/readme.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.