> 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/readme.md).

# NEXON Whitepaper

NEXON is a next-generation value connection network linking capital markets, digital finance and real-world consumption.

> **From Capital to Token. From Digital to Real.**

A position in a brokerage account, a token in a wallet and a real cross-border payment are all value. None of them has ever sat on the same ledger. Turning the first into the third still takes four systems, four identity checks and about a week — and at every step, a person is manually translating one language of value into another.

**NEXON = NEX (Nexus) + ON (enabled and online).** The name states the job: take that translation out of human hands and make it a product layer you can see, permission and hold to account.

As a product, NEXON is a **super financial-social ecosystem**: AI-Native PayFi, a Wallet, a Marketplace, a Stablecoin Card and a decentralized Social App — five entry points sharing one account system and one pair of assets. What binds them is a layer of AI that **reads what you mean but cannot move your assets**: you state an outcome and its boundaries, and it returns a route naming the amount, the destination, the executor and the expiry, for you to accept or decline.

To see why it has to be built this way, start with where the three markets actually break.

## Three markets, three languages

| Market           | What value means here                      | Rhythm                                             | Boundary                                   |
| ---------------- | ------------------------------------------ | -------------------------------------------------- | ------------------------------------------ |
| Capital markets  | Ownership, and a claim on future cash flow | Quarterly cadence · T+2 settlement · trading hours | Ends at a jurisdiction                     |
| Digital finance  | Liquidity and composability                | 7×24 · finality in seconds                         | Borderless, but barely touches real assets |
| Real consumption | The right to use something                 | A given time, a given place, usable                | Ends at a supplier's inventory             |

Three definitions, three clocks, three borders. None is wrong, and none can be read by the other two. The markets are not split for lack of pipes — bridges, stablecoin rails and tokenization all exist, and each solved something real. What is missing is a common language in which a connection could be expressed.

**That language is what NEXON builds.**

## One ecosystem, two assets

{% columns %}
{% column %}

### XO — Value Anchor

Carries staking, participation and long-term value accumulation.

In the current mechanism, XO is the **Staking Principal Token** inside the Staking Platform: a staking deposit is swapped into XO and starts earning at once, settled every 12 hours, with static yield paid in XO; referral and leadership rewards are paid in NX.
{% endcolumn %}

{% column %}

### NX — Circulation Engine

Connects trading, payment, exchange and consumption.

In the current mechanism, NX is NEXON's **Core Value Token**: subscribed at 0.1 USDT or earned as dynamic rewards, it lists at 1.0 USDT, it is sell-only, 28% of every deposit buys NX as fuel to be burned on static withdrawal, and X Points are bought with it from V3 up.
{% endcolumn %}
{% endcolumns %}

In one line: **NEXON is the ecosystem, anchored by XO and circulated through NX.**

## The economics running today <a href="#the-economics-running-today" id="the-economics-running-today"></a>

One account, two operating layers that mind their own business. The **NEX exchange** is the spot layer: XO trades freely, NX lists sell orders only with no buy orders, and the daily release is displayed from listing day. The **Staking Platform** handles XO staking, settlement every 12 hours, term bonuses, referral rewards, leadership bonuses and reward withdrawal. Both share the account system and the back office, but ledgers, permissions and disclosures stay separate.

A staking deposit is split in two the moment the order opens:

<figure><img src="https://609249596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDuNfUDKKCaOvp6aLuQX1%2Fuploads%2Fgit-blob-ab54c520be50ae6e904d389dfc4fd34804cd2f50%2Fonepage-04-fuel-wallet.svg?alt=media" alt="A 10,000 USDT deposit: 28%, or 2,800 USDT, buys 2,800 NX at 1 USDT each as fuel — burn only, no transfer, no trading"><figcaption><p>A 10,000 USDT deposit: 2,800 NX as fuel, the rest swapped into XO and earning</p></figcaption></figure>

<table><thead><tr><th width="150">Parameter</th><th width="230">Value</th><th>What it does</th></tr></thead><tbody><tr><td>Deposit split</td><td>28% fuel · the rest into XO</td><td>28% buys NX at 1 USDT each as fuel (burn only); the rest is swapped into XO and staked</td></tr><tr><td>Static settlement</td><td>0.2% – 0.6% every 12 hours (0.4% – 1.2% a day)</td><td>10,000 USDT deposited earns 28.8 – 86.4 USDT a day, static yield paid in XO</td></tr><tr><td>Term bonus</td><td>base / +10% / +20% / +30% / +50%</td><td>30 / 90 / 180 / 360 / 540 days, set by term alone; on the 30-day term the principal comes back at maturity</td></tr><tr><td>Withdrawal and burn</td><td>30% / 20% / 10%</td><td>Immediate / 30-day / 60-day settlement of static yield; the equivalent fuel NX burns, gone for good</td></tr><tr><td>Private sale and listing</td><td><code>0.1 USDT → 1.0 USDT</code></td><td>Three tiers of 1,000 / 5,000 / 10,000 USDT, 11,500 allocations, 200 million NX; paired with an XO stake at 3:1; sell only, never buy</td></tr><tr><td>Linear release</td><td>1,095 days · 2,190 payouts</td><td>Daily from listing day, <code>D = A ÷ 1,095</code></td></tr><tr><td>Dynamic rewards</td><td>20 generations at 76% · V1 – V12</td><td>On each downline's daily static output, paid on the level differential, settled in NX, burning no fuel; X Points bought with NX from V3 up</td></tr></tbody></table>

This mechanism is the current economic baseline. The larger product narrative sits on top of it without rewriting a single number.

## The long arc: an AI-native financial-social ecosystem

Five product surfaces close one loop: **discover in Social → decide in Wallet → route through PayFi → use in Marketplace or Card → return with data and relationships.** AI-Native PayFi is the second focus of the narrative, because it is where "here is what I want" becomes a route that can be checked, approved, executed and receipted.

```mermaid
flowchart LR
    S["Social<br/><i>discover</i>"] --> W["Wallet<br/><i>decide</i>"]
    W --> P["AI-Native PayFi<br/><i>route and approve</i>"]
    P --> M["Marketplace<br/><i>use</i>"]
    P --> C["Stablecoin Card<br/><i>use</i>"]
    M --> R["Receipts · preferences · relationships"]
    C --> R
    R -. "returned only if the user chooses" .-> S
    R -. "policy and history" .-> W
    classDef anchor fill:#047854,stroke:#047854,stroke-width:1.5px,color:#F5F3F0
    classDef engine fill:#8B5CF6,stroke:#8B5CF6,stroke-width:1.5px,color:#F5F3F0
    classDef solid fill:#F5F3F0,stroke:#141414,stroke-width:1.2px,color:#141414
    class S,W,M,C solid
    class P anchor
    class R engine
```

## Where to start

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Start with the problem</strong></td><td>Why the three markets are still disconnected, and what bridges, stablecoin rails and tokenization each leave out.</td><td><a href="/nexon-docs/part-i-the-problem/01-the-split.md">The Split</a></td></tr><tr><td><strong>Start with the thesis</strong></td><td>Intent → Route → Policy Check → User Approval → Execution → Receipt: the six stages that replace manual translation.</td><td><a href="/nexon-docs/part-ii-the-connection-thesis/02-the-translator.md">The Value Translator</a></td></tr><tr><td><strong>Start with the numbers</strong></td><td>0.2% – 0.6% every 12 hours (0.4% – 1.2% a day), term bonuses, the private sale at 0.1 USDT listing at 1.0 USDT, the 1,095-day release, burn on withdrawal and the worked examples.</td><td><a href="/nexon-docs/part-v-economics/05-tokenomics.md">Token Economics</a></td></tr></tbody></table>

If you want the arithmetic first, jump to [Worked Examples](/nexon-docs/part-v-economics/05-tokenomics/worked-examples.md). If you want to know who is responsible for each leg and who resolves a failure, jump to [Protocol Architecture](/nexon-docs/part-iii-architecture/03-architecture.md).

Posters, one-pagers, PDFs and logos are available in [Project Materials](https://docbay.nexon.markets/).

NEXON is the first flagship platform on the NEX exchange.

*The economic parameters and calculations in this paper follow the current mechanism finalised on 10 September 2026; the legal and risk boundaries are in the* [*Legal Disclaimer*](/nexon-docs/appendix/legal-disclaimer.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://nexon-3.gitbook.io/nexon-docs/readme.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.