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

# VDEX500

The VDEX500 is a monthly competition that rewards consistently profitable traders and referrers.

On the first of every month, the Trader and Referral Leaderboards are paid out and the new competitions begin. The Referral Leaderboard’s pool is half of the Trader Leaderboard’s.

Before placing on the Trader Leaderboard, users must first fill their progress bar. The progress bar increases through consistently profitable trades. Once completed, traders are automatically eligible for the next monthly competition and do not need to refill it. However, if the account accumulates losses, the progress bar could be partially or fully undone.&#x20;

Trader Leaderboard rankings and payouts are based on Sharpe ratio, MTD profit, and drawdown. More trades with tight TP/SLs will result in higher payouts than fully allocated long-term positions. Each trader’s payout is calculated independently of other traders.

Referral Leaderboard rankings and payouts are based on score, the cumulative monthly payout of referred traders. For example, if a user referred two traders who earned $1,000 and $100 in payouts that month, then their score would be 1,100. Top referrers may be invited to the Business Developer program. BDs earn 50% of the score for indirect referrals, so that if a BD was upstream of the direct referrer in the example above, they would earn a score of 550.


---

# 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.vdex.trade/more/vdex500.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.
