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

# Leaderboard

The Helix Profit and Loss (PNL) Leaderboard ranks the top traders based on realized trading PNL across four durations:

* **Today**: Starts at 00:00 UTC each day.
* **This Week**: Begins at 00:00 UTC on Monday.
* **This Month**: Starts at 00:00 UTC on the first day of the current month.
* **All Time**: Tracks realized PNL since August 1, 2024.

### **How the Leaderboard Works**

* **Eligibility**: Connected wallets appear on the Leaderboard only if their PNL clears a dynamic hurdle set by the top traders' performance. Wallets with negative PNL, PNL below the hurdle, or no PNL will not see their rank until profitable trades exceed the hurdle.
* **Updates**: The Leaderboard refreshes every hour on the hour.
* **Inactivity**: Wallets with extended inactivity or trades predating the Leaderboard's start may not be ranked.

### **Key Notes**

* **For Reference Only**: Leaderboard figures are for vanity purposes and trading competitions. Figures on the PNL Leaderboard **are not** a substitute for thorough tax reporting calculations.
* **Spot Markets**:
  * Only spot trades made after the Leaderboard launch count toward PNL.
  * PNL is calculated using the **First In, First Out (FIFO)** method.
* Purchases made before the Leaderboard went live do not count toward PNL, even if sold afterward.
* **Derivatives Markets**:
  * Realized PNL is calculated for each trade when it is closed, based on emitted trade logs.
  * Totals from individual trades are aggregated and added directly to the Leaderboard PNL.
  * Adjustments for scenarios like liquidations or funding payments are included in the PNL calculation.


---

# 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://docs.helixapp.com/leaderboard.md?ask=<question>&goal=<user_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.
