> 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/2-the-game/2.1-intro-game.md).
# 2.1 Intro Game
**Phase 1** of Trendex is a competitive on-chain game where fans activate Tokens linked to players, **and earn SOL based on real football performance.**
You don’t just follow the action, you take positions on the players you believe in.
Every tournament (two per week), your activated Tokens score points depending on how those players perform in real matches.
→ Your **skill** and **conviction** determine your results, **not luck.**
Trendex transforms football knowledge into economic outcomes.
**How Phase 1 works at a glance**
1. You acquire Tokens (Official or Community)
2. You activate the Tokens you want to compete with for the next tournament
3. A snapshot locks your active positions
4. Real games happen
5. Your players score
6. Leaderboards decide payouts
7. You earn SOL + SP
Short cycle → high signal → continuous opportunities.
**Why this matters**
Phase 1 is not the end of the vision, it is the first unlock of ownership.
It gives fans something they never had before in mainstream sports:
→ the ability to get rewarded when they were right.
That’s the foundation on which Phase 2 will build more layers of composable value.
---
# 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/2-the-game/2.1-intro-game.md?ask=&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.