> For the complete documentation index, see [llms.txt](https://nexon-3.gitbook.io/nexon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexon-3.gitbook.io/nexon-docs/part-v-economics/05-tokenomics/two-assets-two-jobs.md).

# Two Assets, Two Jobs

XO carries long-term value and EXON drives circulation; each has one precise job in the current mechanism.

NEXON uses two assets because **storing value and moving it are not the same job**.

**XO is the Value Anchor. EXON is the Circulation Engine.** Under that narrative, the current mechanism gives each asset a narrower, implementable, auditable function.

## The complete role map <a href="#the-complete-role-map" id="the-complete-role-map"></a>

| Dimension                 | XO                                                                                         | EXON                                                                                                                                                 |
| ------------------------- | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Where the name comes from | `X` for cross-domain connection and possibility; `O` for the closed loop and settled value | `EX` for exchange and experience; `ON` for circulation switched on                                                                                   |
| Narrative role            | Value Anchor                                                                               | Circulation Engine                                                                                                                                   |
| Narrative function        | Staking, participation, governance and long-term value                                     | Trading, payment, exchange, fees and consumption                                                                                                     |
| Current formal name       | Staking Principal Token                                                                    | Core Value Token                                                                                                                                     |
| How it is acquired today  | Trades freely on NEX; swapped automatically when a deposit is staked                       | Private-sale subscription at 0.1 USDT, or earned as dynamic rewards                                                                                  |
| Current market            | Free buying and selling on NEX                                                             | Lists at 1.0 USDT; NEX lists sell orders only, no buy orders                                                                                         |
| Current mechanical job    | Carries the staking principal; static yield is paid in XO                                  | Referral and leadership rewards are paid in EXON; 28% of every deposit buys EXON as fuel, burned on static withdrawal; X Points are bought with EXON |
| Supply                    | Minted; no fixed cap                                                                       | 1 billion, of which only 200 million enters the private sale                                                                                         |

`USDT` is the unit of account. XO's market and EXON's market are **deliberately separate**: one trades both ways, the other is sell-only.

## Why the split is not optional <a href="#why-the-split-is-not-optional" id="why-the-split-is-not-optional"></a>

Treat the staking principal and the circulating asset as one job and two things blur at once: a **market price move** gets misread as a **change in the earning base**; a **fuel burn** gets misread as a **loss of principal**.

The two-asset structure keeps four questions apart:

{% stepper %}
{% step %}

### What earns?

The XO that a staking deposit is swapped into. It settles every 12 hours at 0.2% – 0.6%; 10,000 USDT staked earns 40 – 120 USDT a day.
{% endstep %}

{% step %}

### Which asset is exposed to a public price?

EXON, circulating on NEX spot from its 1.0 USDT listing — sell only, never buy.
{% endstep %}

{% step %}

### What is bought when an order opens?

28% of the deposit buys EXON at 1 USDT each as fuel. In only.
{% endstep %}

{% step %}

### What burns when rewards are withdrawn?

On static withdrawal, fuel EXON burns: 30% on immediate settlement, 20% on 30-day, 10% on 60-day.
{% endstep %}
{% endstepper %}

Four questions, four different answers. No statement should merge any two of them.

## Narrative is not arithmetic <a href="#narrative-is-not-arithmetic" id="narrative-is-not-arithmetic"></a>

Calling XO the "Value Anchor" keeps it from being read as a disposable ledger entry — it links staking participation to the long-term ecosystem thesis. Its settled function today is **Staking Principal Token**: the principal earns on it, and all three reward streams are paid in it.

Calling EXON the "Circulation Engine" explains why this asset can, over time, connect digital and real-world activity. Its confirmed operations today are: private-sale subscription, dynamic-reward payout, spot listing (sell only), 1,095 days of daily release, fuel purchase, burn on static withdrawal, X Points. Trading, payment and exchange connect as each of the five entry points goes live (Roadmap).

## Boundaries that public copy has to hold <a href="#boundaries-that-public-copy-has-to-hold" id="boundaries-that-public-copy-has-to-hold"></a>

<table><thead><tr><th width="60">#</th><th>Boundary</th></tr></thead><tbody><tr><td>1</td><td>XO is not equity, debt or a claim on revenue</td></tr><tr><td>2</td><td>EXON is NEXON's project asset</td></tr><tr><td>3</td><td>Fuel EXON and the XO under stake are <strong>two ledgers</strong>: the first can only be burned, the second earns and pays static yield</td></tr><tr><td>4</td><td>An EXON burn is permanent destruction, not a transfer to an operator</td></tr><tr><td>5</td><td>Holding either asset authorises no AI, PayFi, wallet or other user to act on the account</td></tr><tr><td>6</td><td>Each new token use goes live with its entry point and is defined by that entry point's rules</td></tr></tbody></table>

## One sentence for external use <a href="#one-sentence-for-external-use" id="one-sentence-for-external-use"></a>

> **NEXON is the ecosystem, anchored by XO and activated through EXON.**

When the current mechanism is under discussion, add the narrower sentence: **XO is the Staking Principal Token — the principal earns on it and static yield is paid in it; EXON is the Core Value Token — subscribed or earned, sell-only, burned on static withdrawal, and the currency of X Points.** Said together, both the narrative and the source of truth are protected.

*Previous:* [*Token Economics*](/nexon-docs/part-v-economics/05-tokenomics.md) *· Next:* [*XO — Value Anchor*](/nexon-docs/part-v-economics/05-tokenomics/xo.md)


---

# 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://nexon-3.gitbook.io/nexon-docs/part-v-economics/05-tokenomics/two-assets-two-jobs.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.