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

# Economic Model

Nexus is designed as one integrated economic system — a purpose-built blockchain, a decentralized exchange, and a native dollar stablecoin — built to enable powerful financial activity at scale.

## The Nexus Trifecta

Three reinforcing primitives operate as a single economic machine rather than as separate products:

* **The Nexus blockchain** — a purpose-built, EVM-compatible chain with a high-performance trading engine built in and verifiable execution.
* **The Nexus Exchange** *(planned)* — a decentralized spot and perpetual futures venue running directly on the chain.
* **USDX** *(planned)* — a native dollar stablecoin, backed 1:1 by short-duration U.S. Treasury bills and cash equivalents, used as the Exchange's margin and settlement asset.

## Economic engines

Each part of Nexus is an economic engine in its own right, and the three are designed to compound into a single system:

### The Exchange

The Nexus Exchange will use a **maker–taker model** — makers who add liquidity earn rebates, takers who remove it pay fees. Trading fees will be the Exchange's primary economic output, scaling with traded volume and liquidity depth.

### The Stablecoin

USDX is designed to be the Exchange's margin and settlement asset. Dollar balances settled in USDX — rather than a third-party stablecoin such as USDC or USDT — are intended to generate **U.S. Treasury-bill yield** on the backing reserves: an economic flow that scales with the dollar value held and settled through the network.

### The Blockchain

The Nexus blockchain is fully **EVM-compatible and permissionless**, so its economy grows with everything built on it. Builders extend the venue directly — market deployers list new spot and perpetual markets, and frontend operators route order flow, earning a share of the fees they generate. Beyond the Exchange, EVM applications and integrations broaden network usage, and all of this activity consumes blockspace — deepening the chain's base-layer economy.

## How the engines compound

The three engines are not independent — they reinforce one another, so activity in one strengthens the others. This is the core of the model:

```mermaid
flowchart LR
  T[Trading volume] --> U[USDX demand & TVL]
  U --> L[Deeper liquidity]
  L --> E[Better execution]
  E --> T
  B[New markets & apps] --> T
```

* **The Exchange → liquidity.** More trading volume deepens order books and tightens spreads, which improves execution and attracts still more volume.
* **The Stablecoin → capital.** More value settling in USDX grows reserve yield *and* deepens USDX liquidity, which improves margining and settlement — feeding back into trading.
* **The Blockchain → platform.** Permissionless builders and EVM applications add markets, order flow, and usage, broadening coverage and volume — which in turn attracts more builders.

Each loop also consumes blockspace, so growth in any one engine deepens the chain's base-layer economy. **NEX is the unit of account that circulates through these flows** — see [Tokenomics › Utility](/overview/tokenomics.md) for the token's specific roles.

***

<sub>Forward-looking statement. The Nexus Exchange and USDX are in development and have not yet launched; the features, economics, and revenue described here are planned, are estimates only, are subject to change without notice, and may differ materially from actual outcomes.</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 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/economic-model.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.