> For the complete documentation index, see [llms.txt](https://versus-x.gitbook.io/versus-x/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://versus-x.gitbook.io/versus-x/recipe-for-success/usdvsx-token.md).

# $VSX token

The $VSX token is the native utility token of the Versus-X ecosystem and the engine behind the platform's wagering system. Players use $VSX to place wagers across all game modes, and all payouts are made in $VSX. While the platform supports wagering with different tokens and currencies to lower the barrier to entry for players, $VSX always offers the most favorable terms, including the lowest rake fees. This creates a natural incentive for players to hold and use $VSX as their primary wagering currency, tying token demand directly to platform activity rather than speculation.

When players wager with partner tokens, a slightly higher rake applies. The additional revenue generated through partner token wagers can be used to support the ecosystem in various ways, including proprietary trading of $VSX on the open market, funding promotional campaigns, or strengthening liquidity. This ensures that all wagering activity on the platform, regardless of which currency is used, ultimately reinforces the value of the native token.

$VSX launched on April 2nd, 2024 and is currently trading on Gate.io and Uniswap. The current token distribution is as follows:

<figure><img src="/files/lhJtl0L9XNWkhkCZX7MN" alt=""><figcaption></figcaption></figure>

* 37.00% of total supply is locked and will vest gradually through 2029, with releases scheduled at 5M $VSX in June 2026, 7M $VSX in June 2027, 11M $VSX in June 2028, and 14M $VSX in June 2029. These tokens will be allocated to the treasury upon release to fund ecosystem growth and development.
* 12.73% of total supply remains dormant within early investor vesting contracts.
* 10.00% of total supply is held in the Versus-X treasury, used to fund operations, partnerships, and growth initiatives.
* 5.87% of total supply is allocated to liquidity pools supporting $VSX trading on decentralized exchanges.
* 34.40% of total supply is freely circulating supply.

Unlocked tokens will only enter circulation in response to growing market and player demand, ensuring that supply increases are matched by genuine ecosystem activity. Looking ahead, the team is exploring a range of token sink mechanisms to further support long-term token value. These include proven iGaming mechanics such as promotional campaigns that encourage wagering and token accumulation, as well as multiplayer game mechanics like seasonal passes, custom player skins, and exclusive in-game items that can only be acquired with $VSX. Combined with the potential for structured token accumulation programs funded by platform revenue, these mechanisms are designed to create sustained demand for $VSX that grows alongside the player base.


---

# 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://versus-x.gitbook.io/versus-x/recipe-for-success/usdvsx-token.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.
