> For the complete documentation index, see [llms.txt](https://docs.fyuz.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyuz.fun/rewards-and-community/seasons-and-leaderboard.md).

# 🏁 Seasons & leaderboard

## 📊 The leaderboard

The global leaderboard ranks traders by **net volume** and accumulated points — updated live from the on-chain indexer. It's the spine of the rewards system: your rank drives your share of periodic reward distributions.

## ⏱️ Seasons

**Seasons** are time-boxed competitions layered on top: a start date, an end date, a live countdown and a **prize pot** 💰. When a season ends, final standings decide the payout split.

* Your season rank and the pot are always visible on the Season page.
* Season rewards are funded by the platform's share of trading fees — real revenue, not printed tokens.

## 💎 Trader tiers

Lifetime volume also assigns you a permanent tier — **Bronze, Silver, Gold, Diamond** — shown on your profile. See [Trader tiers](/rewards-and-community/trader-tiers.md).


---

# 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.fyuz.fun/rewards-and-community/seasons-and-leaderboard.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.