> 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.7-leaderboards.md).

# 2.7 Leaderboards

**Trendex uses two independent leaderboards every tournament.**\
\
Each leaderboard rewards a different type of skill, and each one pays out SOL from the tournament reward pool.

***

#### Total Points Leaderboard (80% of the pool)

This leaderboard ranks players based on allocation × skill.

The more activated tokens you have on players who perform well → the higher you rank.

This is where allocation × skill is rewarded.

***

#### SquadScore Leaderboard (20% of the pool)

This leaderboard ranks players based on selection quality, independent of how many tokens they activated.

To be eligible, you need at least 4 different activated players.

This is where pure football IQ can beat larger wallets.

***

#### Why 2 Leaderboards?

We separate both dimensions into different ladders, so both styles can win:

| Style                 | Leaderboard  |
| --------------------- | ------------ |
| allocation × skill    | Total Points |
| pure scouting quality | SquadScore   |

Trendex rewards both types of players:<br>

* players who take larger positions
* players who have the best skills<br>

***

#### Payout Timing

Payouts happen after the tournament ends, once PlayerScores are final.<br>

**SOL rewards are sent directly on-chain.**

**SP are credited directly to your Trendex account.**


---

# 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/2-the-game/2.7-leaderboards.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.