> For the complete documentation index, see [llms.txt](https://ncclabs.gitbook.io/ncc-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ncclabs.gitbook.io/ncc-docs/the-ncc-solution/unified-liquidity-engine.md).

# Unified Liquidity Engine

NCC's liquidity system is the Unified Liquidity Engine. Its emphasis is on asset coordination, execution, cross-chain routing and depth. Rather than promoting any single underlying matching mechanism.

## Multi-asset Liquidity Infrastructure

Traditional DEXs are typically built around native crypto assets and stablecoins. NCC's Unified Liquidity Engine, by contrast, supports a broader range of asset types. Including RWA tokens, NFTs, GameFi assets, Marketplace rights assets and PayFi scenario assets.

This design means NCC's liquidity does not only serve trading demand. It also serves asset applications, consumer scenarios, ecosystem incentives and long-term value management.

## Cross-chain Coordination

As multi-chain ecosystems mature, assets distributed across networks have become the norm. NCC's liquidity engine uses cross-chain messaging, asset mapping and routing mechanisms to enhance coordination across chains and reduce user complexity in cross-chain trading and asset management.

For RWAs, which depend more heavily on stable pricing and deep markets, a unified liquidity mechanism improves market efficiency, reduces trading friction and supports broader institutional and user participation.

The Unified Liquidity Engine also performs risk coordination. Different assets carry different liquidity parameters, risk levels, depth profiles and settlement logic. NCC uses tiered asset pools, routing strategies and risk-parameter management so that both high-frequency and low-frequency assets can operate in suitable liquidity environments.


---

# 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://ncclabs.gitbook.io/ncc-docs/the-ncc-solution/unified-liquidity-engine.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.