# Token Allocation and Release Schedule

INTX has a total fixed supply of **100,000,000 tokens.**

<div data-full-width="false"><figure><img src="/files/tfoEGo5PajOziKRdhl7q" alt=""><figcaption></figcaption></figure></div>

## **Token Allocation:**

### **Token Generation Event — 8.4%:**

**Private Round**: 412,500 // 0% on TGE, vested linearly over 6 months.

**Public Round:** 8,000,000 // 100% on TGE

Claimable in staked xINTX to participate and align with the long-term IntentX stakers.

### **Community Incentives - 21%**

**Total number of tokens:** 21,000,000

**Release schedule:** Over 3 years.

1. 3,000,000 INTX / 3% in the retroactive airdrop to **Open Beta** participants. 50% claimable on TGE, 50% 4 weeks after in the form of xINTX
2. 1,000,000 INTX / 1% of this supply is allocated to an additional airdrop to the broader Mantle Ecosystem.
3. The remaining supply (17,000,000 INTX) will be distributed to incentivise traders on IntentX after **TGE**.

Tokens will be available for claim on a daily basis. Full details available at [**Trade & Earn program**](/tokenomics/trade-and-earn-xintx.md)**.**

{% hint style="info" %}
**All trader incentives will be claimable in the staked xINTX form to provide long-term alignment amongst participants.**
{% endhint %}

The emission schedule is subject to change and the above acts as a guide only.

### **Treasury - 15%:**

**Total number of tokens:** 14,872,389

**Release schedule:** No vesting, however, **DOES NOT** form part of the circulating supply until utilized.

The treasury is reserved for various long-term functions of the project including:

* Liquidity Incentives as DEX bribes.
* Strategic treasury swap with SYMM to align long-term interests and benefit the IntentX platform.
* A proportion can be staked as xINTX to provide long-term income stream and build up a war chest.
* May be utilised in marketing, grants program, partnerships, exchange listings, etc.

The treasury will be managed carefully to ensure long term success of the project and to the benefit of xINTX stakers.

### **Team - 20%:**

**Total number of tokens:** 20,000,000

**Release Schedule:** 40 day cliff, vested linearly over 24 months.

Team tokens will be claimable in staked xINTX to participate in the value creation, fund development, and align team with the IntentX stakers.

{% hint style="info" %}
**Note:** In commitment to the long term growth of IntentX, the core team has agreed to locking their vested xINTX for 12 months from TGE (with option to renew). While participating in revenue distributions and backing ratio appreciation, no team tokens can be unstaked during this period.
{% endhint %}

### **Seed Round - 20%:**

**Total number of tokens:** 20,304,000

**Release Schedule:** 40 day cliff, vested linearly over 12 months.

Will be claimable in staked xINTX to participate align with the long term IntentX stakers.

### **Strategic Round - 10%:**

**Total number of tokens:** 10,111,111.13

**Release Schedule:** 40 day cliff, vested linearly over 12 months.

Will be claimable in staked xINTX to participate align with the long term IntentX stakers.

### **Advisors - 2.8%:**

**Total number of tokens:** 2,800,000

**Release Schedule:** Vests linearly over 2 years. 6 months cliff.

Allocated to key advisors on the project.

### **Liquidity Seed - 2.5%:**

**Total number of tokens:** 2,500,000

**Release Schedule:** Vested immediately.

Will be used as seed liquidity with stables on a host DEX.

## Release Schedule:

<div data-full-width="false"><figure><img src="/files/QySLgZxSIC4dZnLk2Ukk" alt=""><figcaption></figcaption></figure></div>

INTX will be fully vested over 3 years from TGE.


---

# 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.intentx.io/tokenomics/token-allocation-and-release-schedule.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.