# The Ouroboros ($ORX) Token

<figure><img src="/files/ByBYafA2PGUIC4I6DLJ7" alt="" width="375"><figcaption><p>ORX</p></figcaption></figure>

* **Name:** Ouroboros
* **Symbol/Ticker:** ORX
* **Contract Address:** 0xd536e7a9543cf9867a580b45cec7f748a1fe11ec
* **Max Supply:** 1,270,600,000 (but likely to be much lower.  See [Vesting Schedule](/the-ouroboros-usdorx-token/launch-participation-mechanics.md) for more details)
  * Supply Breakdown:&#x20;
    * 1,000,000,000 tokens emitted via the [launch mechanism](/the-ouroboros-usdorx-token/launch-participation-mechanics.md)
    * 600,000 tokens emitted for initial liquidity provisioning (locked, smart contract controlled)
    * 20,000,000 tokens which *may* be emitted via the onboarding system
    * 200,000,000 Backstop Pool incentives (optional, not on at launch)
    * 50,000,000 USDX/WETH incentivised UniswapV2 farm (optional, not on at launch)

## Purpose

The ORX token sits at the center of the Ouroboros ecosystem, and acts as the **primary value accrual mechanism for the protocol**.  Any products launched under the Ouroboros umbrella will be required to divert **fee sharing/inflationary rewards to ORX holders**.  Protocols which have no fee/inflation structure should make use of ORX in some manner to enrich it with usecase/utility.

## Further Reading

1. [Pumpamentals](/the-ouroboros-usdorx-token/pumpamentals.md)
2. [Launch Mechanics](/the-ouroboros-usdorx-token/launch-participation-mechanics.md)


---

# Agent Instructions: 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:

```
GET https://docs.ouroboros.foundation/the-ouroboros-usdorx-token.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
