> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/exchange-layer-1/overview/tokenomics.md).

# Tokenomics

NEX is the Nexus token. It is an ERC-20 on Ethereum. This page covers its total supply, distribution status, and vesting schedule.

## Token overview

| Property                          | Value                                                      |
| --------------------------------- | ---------------------------------------------------------- |
| Token name / ticker               | Nexus (NEX)                                                |
| Total supply                      | **100,000,000,000,000 NEX (100T)**                         |
| Token contract (Ethereum, ERC-20) | `0xf57D49646621F563b0B905aFc8336923AC569Ec5` (18 decimals) |
| Genesis / TGE                     | May 20, 2026                                               |

## Distribution status

![NEX token breakdown: Treasury 60%, Team 20%, Investors 20%; total supply 100,000,000,000,000 NEX (100T).](https://2089897468-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9oLAShrvQHgS1nMEemAm%2Fuploads%2Fgit-blob-e8fb3576e7b15978a05399e886ba200277b10fba%2Fnex-tokenomics.png?alt=media)

| Allocation | Share | Amount (NEX)       |
| ---------- | ----- | ------------------ |
| Treasury   | 60%   | 60,000,000,000,000 |
| Team       | 20%   | 20,000,000,000,000 |
| Investors  | 20%   | 20,000,000,000,000 |

Early backers include Dragonfly ($2.2M seed, 2022) and Lightspeed and Pantera ($25M Series A, 2024). See [Contributors & partners](/exchange-layer-1/overview/contributors-and-partners.md) for the full list.

## Vesting schedule

At genesis, the **60T Treasury is unlocked** and the **40T Team & Investor allocation is locked** on a single schedule. A one-year cliff (May 20, 2027) releases **33%**, followed by monthly linear unlocking over the next 24 months, reaching full supply by May 2029.

| Milestone      | Date         | Unlocked supply |
| -------------- | ------------ | --------------- |
| Genesis (TGE)  | May 20, 2026 | \~60T (60%)     |
| 12-month cliff | May 2027     | \~73T (73%)     |
| Full unlock    | May 2029     | 100T (100%)     |

***

<sub>Note on rights. Consistent with the MiCA whitepaper, NEX does not confer ownership rights, dividend rights, or automatic governance/voting rights. Protocol rules are changed through the network's consensus mechanisms and by validators during protocol upgrades.</sub>

<sub>Forward-looking statement. The unlocked-supply trajectory and all dates and figures are estimates only, subject to change without notice, and may differ materially from actual outcomes. Token release and unlock schedules may be adjusted, delayed, accelerated, or otherwise modified.</sub>


---

# 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://docs.nexus.xyz/exchange-layer-1/overview/tokenomics.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.
