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

# leaderboard

The leaderboard is powered by an off-chain indexer.

The contract remains the source of truth. The indexer reads contract state and builds a leaderboard view for the frontend.

## What The Leaderboard Tracks

The leaderboard can show:

* Total volume
* Unique players
* Settled rounds
* Biggest win
* Wallet rankings
* Rounds entered
* Rounds won
* Win rate
* Total deposits
* Total winnings
* Net result

## Why An Indexer Is Needed

Smart contracts are not optimized for frontend leaderboard queries.

The contract stores the data needed to verify rounds, but aggregating many rounds directly in the browser would be slow and unreliable.

The indexer builds a convenient API for the UI.

## Current Indexer Mode

The current indexer uses contract view calls instead of `eth_getLogs`.

This keeps the leaderboard simple and avoids relying on historical log indexing support.

The current indexer mode is:

```
contract-views
```

## Empty Leaderboard

If the leaderboard is empty, it usually means there have not been enough settled winner rounds yet.

Cancelled solo rounds are not counted as wins.

## Trust Model

The leaderboard is a UI convenience layer.

If the indexer is wrong or offline, the contract state is still the source of truth.


---

# 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://hyperpot.gitbook.io/hyperpot-docs/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.