> 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/overview/tokenomics.md).
# Tokenomics
NEX is the native token of the Nexus blockchain. This page covers its total supply, utility, 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 |
## Utility
NEX is the **native token of the Nexus blockchain** — the asset that powers computation, pays for network operation, and aligns participants across the ecosystem. Each utility is described in detail below.
### Gas for transactions
Every transaction on the Nexus blockchain — value transfers, contract calls, and, in the future, exchange operations — pays its fee in NEX. NEX is the **sole gas asset**: it is required to submit any transaction to the network, so demand for blockspace translates directly into demand for the token. Gas is priced by the computational resources a transaction consumes, so heavier operations cost proportionally more NEX.
### Smart-contract execution
The Nexus blockchain is fully EVM-compatible, and NEX **meters the execution of smart contracts** deployed to it. Each operation a contract performs consumes gas, paid in NEX and priced by the resources used. As programmable activity on the network grows — DeFi, integrations, and applications built by third parties — NEX is the settlement asset that underpins all of it.
### Consensus and compute
NEX is used to **interact with the network's consensus and compute layers** — the systems that order transactions, reach finality, and generate the cryptographic proofs that let anyone verify execution independently. NEX denominates the fees that compensate these operations, tying the token directly to the security, liveness, and verifiability of the network. (NEX is a fee and operating asset; it does not confer staking rewards, dividends, or governance rights — see the note on rights below.)
### Exchange incentives and alignment *(planned)*
Beyond gas, NEX is intended to be the asset that **incentivizes and aligns activity on the Nexus Exchange** — encouraging the behaviors that make a venue liquid and useful. Planned mechanisms include:
* **Trading incentives** — fee discounts are the first and most concrete example: holding NEX is designed to lower taker fees and improve maker rebates, stacking with standard volume-tier pricing.
* **Liquidity and deposits** — incentivizing the capital and order flow (TVL) that deepen markets and improve execution.
* **Builders** — aligning third parties who list markets and route order flow with the growth of the venue.
Fee discounts are planned for the Exchange launch; the broader incentive mechanisms will be documented as they are introduced. See the [Economic Model](/overview/economic-model.md) for how exchange activity reinforces network usage.
### Future applications
As the network matures, NEX may be used within **additional applications** on the Nexus blockchain as production features are introduced. Any such utility will be documented here as it becomes available.
## Distribution status
| 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](/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%) |
***
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.
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.
---
# 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://docs.nexus.xyz/overview/tokenomics.md?ask=&goal=
```
`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.