> For the complete documentation index, see [llms.txt](https://arbidex.gitbook.io/arbitrum-exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arbidex.gitbook.io/arbitrum-exchange/tokenomics/arx-token.md).

# ARX Token

**Ticker:** ARX

**Contract Address:** 0xD5954c3084a1cCd70B4dA011E67760B8e78aeE84

ARX on **BASE**:\
\
**Contract Address:**  0x58ed4fd0c3d930b674ba50a293f03ef6cd7de7a3

## The basics

At the heart of the ArbiDex ecosystem lies ARX, the main token that powers the platform.

* By staking $ARX, users can earn 100% of protocol revenue and participate in the governance of ArbiDex
*  Locking or flexibly staking $ARX can result in increased earnings of the token
* Earn $ARX by farming 

## **Emission rate** <a href="#emission-rate" id="emission-rate"></a>

### **per second**

| **Metric**         | **Emission/second(ARX)** | **Emission/day (ARX)** |
| ------------------ | -----------------------: | ---------------------: |
| Effective Emission |  0.13 (\*see note below) |                 11,232 |

## Tokenomics  <a href="#distribution" id="distribution"></a>

| Breakdown           | Details                  |
| ------------------- | ------------------------ |
| Ticker              | $ARX                     |
| Max Supply          | 20,000,000               |
| Initial Supply      | 187,548                  |
| Initial Liquidity   | $70,000                  |
| Initial Price       | $1                       |
| Effective Emissions | 0.13/second (\*see note) |

\*The Effective Emissions rate is 0.13 ARX/Second, calculated using the formula: \
Emissions Per Second \* 0.6. \
This is derived from the total Emissions rate of 0.23 ARX/Second, of which approximately 80% is in the form of xARX (Escrowed ARX) and is not immediately liquid.

\*To calculate Effective Emissions, we consider that 80% of the total emissions are in xARX. From this, 50% becomes liquid ARX after a minimum vesting period of 15 days. This liquid portion is then added to the initial 20% liquid portion of the total emissions, resulting in an effective 60% of total emissions. Hence, the Effective Emissions rate is 60% of the total Emissions rate, or 0.13 ARX/Second.

## Token Allocation

| Allocation           | Percentage \[%]                                  |
| -------------------- | ------------------------------------------------ |
| Liquidity Incentives | 87.1%                                            |
| Team                 | 5% (vested linearly 2 years, harvestable weekly) |
| Treasury             | 5% (vested linearly 2 years, harvestable weekly) |
| Initial Mint         | 2.9%                                             |

### Initial Mint Allocation&#x20;

| Allocation     | Percentage |
| -------------- | ---------- |
| Seed Investors | 36,508     |
| Presale        | 56,041     |
| Treasury       | 30,000     |
| Team           | 30,000     |

## How to Confirm ARX Supply for yourself

If you want to confirm the circulating supply of the ARX token, you can do so at:

<https://arbiscan.io/token/0xd5954c3084a1ccd70b4da011e67760b8e78aee84>\
and view the Total Supply listed there.

## Does ARX  have a hard cap?

Yes, ARX has a hard cap of 20,000,000 tokens.


---

# 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://arbidex.gitbook.io/arbitrum-exchange/tokenomics/arx-token.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.