> 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./public-leaderboards.md).
# ๐ Public Leaderboards
Every move you make in OnChain Battles is tracked, ranked, and displayed in real time.\
This isnโt about private wins itโs about **proving you're the best, publicly**.
Our live leaderboard system turns trading performance into a public scoreboard. Traders are ranked transparently for everyone to see competitors, spectators, and potential sponsors alike.
***
### ๐งฎ Ranking Metrics
Each Arena Season features **real-time updating leaderboards**, visible to all users. Traders are ranked based on:
* **% Return** โ Who squeezed the highest ROI out of the trades
* **Absolute Return** โ Total profit in dollar terms
* **Win/Loss Ratio** โ Consistency across multiple trades
* **Wallet Identity** โ Leaderboard names linked to real onchain addresses (pseudonymous or doxxed)
* **Social Flex** โ Optional Twitter/X handles displayed next to names for extra visibility
***
### ๐ง Why It Matters
Public leaderboards bring:
* **Accountability** โ Every trader is held to the same standard
* **Transparency** โ No hiding, no manipulation, no screenshots
* **Entertainment** โ Spectators can follow performance like a sport
* **Status** โ Top performers earn respect, rep, and future opportunities
You donโt just win money โ you build a name.\
Your trading becomes a public performance.
***
>
---
# 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./public-leaderboards.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.