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

# $XIO

## XIO Utility Token

### Overview

$XIO is the **core utility token** of the XIO platform, designed to incentive engagement, governance, and staking functionalities within the ecosystem.&#x20;

***

{% hint style="info" %}

#### Key Fact:

$XIO is the primary utility token that drives the XIO ecosystem, providing governance, staking.
{% endhint %}

***

### $XIO Utility

$XIO powers various aspects of the platform, incentivizing users to participate in governance, provide liquidity, and benefit from fee reductions.

* **Governance Participation:** $XIO holders can propose and vote on key platform decisions, influencing the platform’s development and strategy.
* **Fee Reductions:** Users holding $XIO tokens can enjoy reduced trading fees and transaction costs.

***

### Key Features of $XIO

{% tabs %}
{% tab title="Governance" %}
As a $XIO holder, participate in platform governance by proposing or voting on critical decisions.
{% endtab %}

{% tab title="Fee Reductions" %}
Enjoy reduced trading fees and transaction costs by holding and using $XIO tokens on the platform.
{% endtab %}
{% endtabs %}

<details>

<summary>Future Utility of $XIO</summary>

The future utility of $XIO is designed to expand its role within the ecosystem as the platform grows. These utilities aim to increase the token's value while enhancing user experience and expanding the platform's capabilities.&#x20;

</details>

***

### Burn Mechanism

$XIO employs a **burn mechanism** that gradually reduces the total supply of tokens over time, enhancing scarcity. 20% of platform profits will be used to buy back and burn tokens, ensuring a deflationary mechanism.

#### **How the Burn Mechanism Works**

1. **Trading Profits Allocation**: Every quarter, **20% of the platform's profits** are allocated to buy back $XIO tokens from the open market.
2. **Token Burns**: The purchased tokens are **permanently removed** from circulation, reducing the overall supply of $XIO, which can create scarcity and potentially increase the value of remaining tokens over time.
3. **Quarterly Burn Schedule**: Burns are conducted **approximately every quarter**, but the exact dates are not pre-announced. This ensures a consistent reduction in supply without allowing individuals to predict and manipulate the market based on burn events. The randomness of the burn schedule also enhances fairness and prevents gaming of the system.

***

### Frequently Asked Questions

<details>

<summary>1. What is the purpose of the burn mechanism?</summary>

The burn mechanism is designed to create scarcity by reducing the circulating supply of $XIO tokens over time. A portion of the platform’s trading profits is used to buy back and burn tokens, benefiting long-term holders.

</details>


---

# 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://xio.gitbook.io/xio/token/overview/usdxio.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.
