> For the complete documentation index, see [llms.txt](https://wfctoken.gitbook.io/wfcwhitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wfctoken.gitbook.io/wfcwhitepaper/4.-tokenomics.md).

# 4. Tokenomics

WFC has a fixed supply of **1,000,000,000 tokens**, hard-capped at the contract level — no minting function, no inflation, ever. This is verifiable on-chain and is one of WFC's core trust guarantees.

**Contract address:** `0x974733a3f37208647577bB925D8EE854c7337E29`

## Allocation at launch

| Allocation                                              |            Tokens |    Share |
| ------------------------------------------------------- | ----------------: | -------: |
| Founding allocation — locked, 4-year linear vest (UNCX) |       600,000,000 |    60.0% |
| Team — vested 12 months                                 |        35,000,000 |     3.5% |
| Team — liquid                                           |        34,000,000 |     3.4% |
| Initial liquidity (Uniswap)                             |       330,000,000 |    33.0% |
| Burned                                                  |         1,000,000 |     0.1% |
| **Total**                                               | **1,000,000,000** | **100%** |

## Current state (June 2026)

As the market has bought from the pool, the distribution has shifted toward the community:

| Category                                         |          Tokens |
| ------------------------------------------------ | --------------: |
| Locked / vesting (founding 600M + team 35M)      |     635,000,000 |
| Community-held (acquired from the pool)          |     314,000,000 |
| Team — liquid                                    |      34,000,000 |
| In liquidity pool                                |      16,000,000 |
| Burned                                           |       1,000,000 |
| **Circulating** (community + liquid team + pool) | **364,000,000** |

**Circulating supply** reflects tokens actually in the market — community-held, liquid team, and the liquidity pool. The 635,000,000 that is locked or vesting is excluded; this is the same way major trackers calculate circulating supply, and it's deliberate: a large locked share means no surprise unlocks hanging over holders.

**No cliffs, no surprise unlocks.** The founding allocation vests linearly over four years — there is no future date where a giant tranche suddenly hits the market. This is the structural protection against the "team dump" that kills most projects.

**Zero marketing / influencer tokens.** Not a single token has been given away for marketing, influencers, or team activities. There is no hidden overhead of free tokens waiting to be sold into the community's buying.

**Deflation built in.** 1,000,000 tokens were burned in the first week, and the structure allows for future buy-and-burn from operations, which can reduce supply over time.

**Liquidity.** The pool uses a 1% fee tier, so community members who provide liquidity share in the trading fees that pool activity generates.


---

# 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://wfctoken.gitbook.io/wfcwhitepaper/4.-tokenomics.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.