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

# Leaderboard

## Overview

The Leaderboard ranks all HertzFlow traders by performance. It's publicly accessible — anyone can view rankings without connecting a wallet. Connect your wallet to see where you stand relative to the top 100.

<figure><img src="/files/0XquxxBUYOgU28A7GkJM" alt=""><figcaption></figcaption></figure>

Two headline stats sit at the top:

* **Degens** — total number of traders on the platform
* **Aped** — total cumulative trading volume across all traders

***

## Ranking Dimensions

You can sort the leaderboard by three metrics:

| Dimension    | What It Measures                                                                               |
| ------------ | ---------------------------------------------------------------------------------------------- |
| **PnL**      | Your realized profit and loss (USD) — all closed positions, excluding fees and funding         |
| **Volume**   | Your cumulative notional trading volume (USD) — open + close notional from perpetual positions |
| **Win Rate** | Share of your closed trades that ended in profit                                               |

Click a dimension to switch the active sort. Ties are broken by who reached the same value first.

**Default sort:** PnL (descending)

Each row also displays **Trades** (number of closed trades) and **Referee** (number of users referred), though these are not sortable dimensions.

***

## Time Filters

Switch between three time windows:

| Filter       | Coverage                                       |
| ------------ | ---------------------------------------------- |
| **Monthly**  | Current calendar month (resets at month start) |
| **Weekly**   | Current calendar week (Monday 00:00 UTC)       |
| **All Time** | Full historical — never resets                 |

**Default view:** Weekly

***

## How Rankings Display

* Only the **top 10 traders** are shown per dimension per time period

### Your Performance

When you connect your wallet, a **Your Performance** panel shows your standing at a glance:

* **Rank** — your global position (e.g. `#32`)
* **PnL**, **Volume**, **Trades**, **Win Rate** — your stats for the selected time window
* **Referee** — number of users you've referred

In the ranking table itself, if you're in the top 100 your row is **highlighted** so you can spot yourself without paging through.

***

## What Counts

**Volume includes:**

* ✅ Notional value of opened and closed perpetual positions

**Volume excludes:**

* ❌ LP deposits and withdrawals
* ❌ Pending/unfilled limit orders
* ❌ Additional market types may be included in future updates

**PnL includes:**

* ✅ Realized directional profit/loss **after fees** from closed positions

**PnL excludes:**

* ❌ Unrealized PnL from open positions

***

## Coming Soon

Points-based rankings (Total Points, Perp Points, Referral Points) and additional leaderboard tiers are planned for future releases.


---

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