> For the complete documentation index, see [llms.txt](https://onchain-battles.gitbook.io/onchain-battles-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onchain-battles.gitbook.io/onchain-battles-docs/how-usdocb-works.md).
# How $OCB works
### 💰 How Rewards Work
At the heart of every tournament is a **real prize pool**. Once the season ends, the winners paid automatically. No claims. No delays.\
Top PNL = biggest payout. Everything happens onchain. This means traders don’t just play for status they play for **serious money**, in real time.
### 🥇 Tiered Pools = Bigger Stakes
You only compete against traders in your verified PNL bracket:
* $1K+ PNL = Entry-level tier
* $10K, $50K, $100K, and $1M+ = Higher tiers
* Each tier has **its own prize pool**
Higher tiers mean **less competition, but higher risk and bigger pots**.\
The better you are, the more you can win.
### 👁️ For Spectators and Bettors
Not a trader? You can still win.
* **Watch** real-time dashboards of traders in action
* **Bet** on your favorite performers in upcoming tournaments
* **Earn** if your pick prints PNL
Fantasy trading creates a second layer of strategy you don’t have to trade to profit. You just have to **know who’s good**.
### 🧠 Trade. Win. Repeat.
Each Arena Season is time-limited (weekly or monthly).\
Only trades made during the season count.\
At the end, the leaderboard locks and **prizes are paid out immediately**.
Win the round. Claim the pot. Level up your rep.\
Then do it again against tougher traders, for bigger stakes.
---
# 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://onchain-battles.gitbook.io/onchain-battles-docs/how-usdocb-works.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.
