> For the complete documentation index, see [llms.txt](https://docs.trendex.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trendex.gg/1-vision-and-ecosystem/1.1-why-trendex-vision.md).

# 1.1 Why Trendex (Vision)

Trendex turns sports from attention into ownership. Fans and players finally share the value they create. It’s not about watching stars, it’s about owning the digital layer built around them.

We are moving from an attention economy to an ownership economy.\
For decades, sports fans have created the value, attention, engagement, culture, but 0% of the upside flows back to them.\
All the value extracted from the image of stars, fantasy games, advertising, licensing, goes to centralized platforms.

**Trendex exists to reverse that flow.**\
We believe the next frontier of value creation in sport is not watching stars, it’s *predicting* and *owning* the digital layer built around them.

***

**The Problem Today**

* Fans generate demand
* Platforms capture the money
* Stars are the IP
* But fans have no upside
* And stars don’t participate in the value they create\
  → billions of dollars of value → centralized

***

**The Opportunity**

Blockchain enables a new kind of prediction market, one built around real players.\
With verified athlete agreements, Trendex lets fans turn their football knowledge into positions, *on-chain*.\
Each token becomes a stake in your prediction of real-world performance.

You’re not predicting randomly, you’re positioning with conviction.\
When players perform, your squad’s value and rewards move accordingly.

And because it’s on-chain:

* fans can enter
* fans can own
* fans can earn

Trendex Phase 1 is the first step in this new sports prediction economy.

***

#### The Long-Term Vision (Roadmap Logic)

| Phase   | Description                                            | Status                            |
| ------- | ------------------------------------------------------ | --------------------------------- |
| Phase 0 | build the world’s greatest stars roster in Web3        | ✅ done (230+ official agreements) |
| Phase 1 | build the rewarding on-chain game using these Tokens   | 🔥 current phase                  |
| Phase 2 | unlock community IP & value participation around stars | ⏳ coming soon                     |

Phase 2 is where ownership extends beyond gameplay, into monetization and culture creation.

***

#### **Why This Matters**

Trendex is building a *star-powered prediction market,* a place where conviction, skill, and data converge.\
Phase 1 rewards your football IQ with on-chain outcomes.\
Phase 2 expands ownership to culture, content, and IP creation.

This is not just another fantasy game.\
This is the shift from **spectator → stakeholder → market participant**. ⚡️<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trendex.gg/1-vision-and-ecosystem/1.1-why-trendex-vision.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.