# Tokenomics

Every token launched on CGPT DotFun follows a standard tokenomics model:

| Component              | Allocation          | Description                                                             |
| ---------------------- | ------------------- | ----------------------------------------------------------------------- |
| **Total Supply**       | 1,000,000,000 (1B)  | Fixed, immutable per token                                              |
| **Bonding Curve Sale** | 87.5% (875M tokens) | Sold until raise target hit ($5k/$10k/$20k)                             |
| **DEX LP**             | 12.5% (125M tokens) | Paired with raised capital for PancakeSwap v2 liquidity (locked 1 year) |

## Graduation Event

* **5% service fee** deducted from the raise
* Remaining funds + 125M tokens → liquidity pool
* LP locked for **1 year**

## Pre-Purchase Option

* Creators may **pre-buy up to 10%** of total supply (100M tokens)
* Shown transparently on the holders list

## Fair Launch Principles

* No pre-mines
* No insider/team/VC allocations
* No hidden taxes or transfer limits

## Cost per Token on DEX After Graduation

The cost per token on PancakeSwap after liquidity migration depends on the raise target and deducted service fee:

| Raise Target | Service Fee | Net Liquidity | Tokens in LP | Cost Per Token |
| ------------ | ----------- | ------------- | ------------ | -------------- |
| $5,000       | $250        | $4,750        | 125M         | **$0.000038**  |
| $10,000      | $500        | $9,500        | 125M         | **$0.000076**  |
| $20,000      | $1,000      | $19,000       | 125M         | **$0.000152**  |

## Initial Market Cap (IMC)

Calculated using 87.5% of tokens (875M) multiplied by the post-graduation token price:

| Raise Target | Token Price | IMC          |
| ------------ | ----------- | ------------ |
| $5,000       | $0.000038   | **$33,250**  |
| $10,000      | $0.000076   | **$66,500**  |
| $20,000      | $0.000152   | **$133,000** |

## Fully Diluted Valuation (FDV)

Based on the full 1B token supply:

| Raise Target | Token Price | FDV          |
| ------------ | ----------- | ------------ |
| $5,000       | $0.000038   | **$38,000**  |
| $10,000      | $0.000076   | **$76,000**  |
| $20,000      | $0.000152   | **$152,000** |

## Supply Cost Table: Estimated Cost to Buy X% of Supply

| Threshold = $5K | Threshold = $10K | Threshold = $20K | % Supply Purchased | Token Quantity |
| --------------- | ---------------- | ---------------- | ------------------ | -------------- |
| $571            | $1,143           | $2,286           | 10% (Max Pre-buy)  | 100M           |
| $1,714          | $3,429           | $6,857           | 30%                | 300M           |
| $2,286          | $4,571           | $9,143           | 40%                | 400M           |
| $2,857          | $5,714           | $11,429          | 50%                | 500M           |
| $3,429          | $6,857           | $13,714          | 60%                | 600M           |
| $4,000          | $8,000           | $16,000          | 70%                | 700M           |
| $4,571          | $9,143           | $18,286          | 80%                | 800M           |
| $5,000          | $10,000          | $20,000          | 87.5% (Graduation) | 875M           |
| N/A             | N/A              | N/A              | Remaining 12.5%    | 125M (LP)      |

These values are for illustration and assume uniform curve progression without gas fees or trade slippage.


---

# 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.chaingpt.org/our-ecosystem/cgpt.fun/tokenomics.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.