> 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/6.-roadmap.md).

# 6. Roadmap

WFC is built in stages, each laying the foundation for the next. Timelines are goals, not guarantees.

**Stage 1 — Foundation (now).** Secure, fully operational on-chain setup; liquidity established; transparent on-chain stats; website and whitepaper live; community channels active; hard-capped, verifiable supply.

**Stage 2 — Growth.** Exchange listings; economic build-out; a transparent, on-chain, verifiable performance vault; broader token utility and ecosystem integrations through partnerships; deeper community engagement — announced as they materialize.

**Stage 3 — Ecosystem.** A WFC-branded perpetuals venue driven by real fee volume; a one-stop crypto economy where people hold the blue chips for stability and look to WFC for crypto education, community, and participation. Community events and partnerships to follow.

The long-term vision is a self-sustaining ecosystem of apps and integrations, walled off from the scams that define so much of crypto. As WFC grows, the predatory side of the space loses ground.


---

# 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/6.-roadmap.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.