> 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/the-breakdown./smart-contract-prize-pools.md).
# 🏆 Smart Contract Prize Pools
OnChain Battles rewards traders who perform\
When the season ends, only the top traders walk away with the prize\
The rest are left with a public record of where they fell short
This is not about participation\
It is about domination
***
### 🎯 Real Rewards with Real Risk
You are not trading for attention\
You are trading for profit
* The top trader claims the pot
* Everyone else walks away with nothing
* Every move is tracked
* Every decision carries weight
Your results are public\
Your record stays visible\
And your outcome is final
***
### 💥 Entry Fees Raise the Stakes
Tournaments include an entry fee, this is where things get serious.
Example tournament entry fees:
1k competition: $10
10k competition: $50
50k competition: $250
The winners take everything, the rest walk away empty.
You feel every trade, because every trade matters.
---
# 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://onchain-battles.gitbook.io/onchain-battles-docs/the-breakdown./smart-contract-prize-pools.md?ask=&goal=
```
`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.