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

# Leaderboard rewards

How season rewards are funded, listed and claimed.

When a season ends, players claim their share of the **season prize pot**, paid in **ETH** on the Robinhood network directly from the Kitzyclubz contract.

## The prize pot grows with the game

* 💰 **Starts at $10K.** The game launches with an initial prize pool of **$10,000**, funded by the team.
* 📈 **Grows with every purchase.** As the game grows, part of all in-game spending goes straight into the final season pot.
* 🐾 **More players, bigger prizes.** The more players spend in the game, the bigger the prize pot becomes.

<figure><img src="https://4045171247-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJ6kLs195qNtzf8XRubT%2Fuploads%2FPbtrBm2rbU5C94y7j7jJ%2Fseason-ended.webp?alt=media" alt="The season ended page"><figcaption><p>When a season ends: your final rank and score, your reward and one Claim button.</p></figcaption></figure>

## How rewards are set

1. When the season ends, the final leaderboard is snapshotted during the \~3-day break between seasons.
2. The team uploads it to the contract as a list of **wallet + reward amount**, all in a single transaction.
3. Mistakes can be corrected only **before** the list is finalised. After that, it can't be changed.

## How to claim

1. Open **Rewards**. When a season has ended, you'll see your final rank, score and reward.
2. Press **Claim reward** and confirm the transaction in your wallet.
3. The reward is sent straight to your wallet.


---

# 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.kitzyclubz.xyz/seasons-and-rewards/leaderboard-rewards.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.
