> For the complete documentation index, see [llms.txt](https://fomo100.gitbook.io/fomo100-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fomo100.gitbook.io/fomo100-whitepaper/prologue-what-we-are-building.md).

# Prologue: What We Are Building

FOMO100 is a next-generation **GameFi aggregation ecosystem** designed to be **trustworthy, scalable, and sustainable**.

In the current GameFi market, most projects face short lifespans, excessive inflation, and rapid user churn. FOMO100 aims to break this cycle through mechanisms of **fair mining, extreme burning, and multi-game aggregation**, forming a **long-term value loop in a decentralized entertainment economy**.

* **For users**: Not just “Play-to-Earn” but a long-term blend of value and entertainment.
* **For developers**: A supportive ecosystem offering incubation, traffic, and value feedback.
* **For the platform**: A value hub that ties revenue growth with token scarcity.

FOMO100 is not just a token or a platform — it is a **new narrative experiment**:\
a combination of **entertainment, finance, and community consensus**, spinning a self-reinforcing economic flywheel.


---

# 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:

```
GET https://fomo100.gitbook.io/fomo100-whitepaper/prologue-what-we-are-building.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.