> 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.3-ecosystem-roadmap-phase-0-phase-2.md).
# 1.3 Ecosystem Roadmap (Phase 0 → Phase 2)
**Trendex is not just a game.**
Trendex is a progressive ownership stack, built in phases, where value becomes more open, more shared, and more composable over time.
Each phase unlocks a new layer.
***
**Phase 0 — Build the Star Layer (2021 → 2025)**
Catalogue de stars.
Before anything else, Trendex built the most strategic asset:\
direct relationships & signed agreements with real athletes.
* 230+ official agreements
* tier-1 football + basketball stars
* unique legitimacy in the space
This is what makes Trendex different from “crypto sports imitators.”\
We don’t reference stars.\
We have real contracts.
***
**Phase 1 — The Game (Now)**
The rewarding on-chain fantasy layer.
This documentation explains Phase 1.
Phase 1 = the first activation layer of ownership:
* Tokens (Official + Community)
* Scoring tied to real performances
* Twice-a-week tournaments
* SOL rewards
* Multipliers for Official Tokens
Phase 1 connects fandom → on-chain performance → payout.
***
**Phase 2 — IP Platform (coming soon)**
The value layer around the stars.
Phase 2 is where ownership extends beyond gameplay.
Here, the star IP layer becomes composable:
* community-driven formats
* new digital objects
* IP-based experiments
* shared upside models
Phase 2 is where token holders participate in the value created around stars, not only inside the game.
***
**Summary**
| Phase | Focus | Status |
| ------- | ------------------------- | ----------- |
| Phase 0 | star catalogue | ✅ done |
| Phase 1 | rewarding game | 🔥 live |
| Phase 2 | IP-powered value platform | coming soon |
***
Trendex is building the rails for the next decade of sports ownership.
---
# 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://docs.trendex.gg/1-vision-and-ecosystem/1.3-ecosystem-roadmap-phase-0-phase-2.md?ask=&goal=
```
`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.