> For the complete documentation index, see [llms.txt](https://docs.native.org/native-dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.native.org/native-dev/build-with-native/asset-issuers/for-pegged-assets.md).

# For RWA Issuers

24/7 Secondary market

Most onchain users still access primary-market liquidity, with pricing pulled from TradFi and liquidity appearing only when a trade is triggered. That puts the asset onchain, but not the market.

Native is built for secondary-market liquidity. Instead of pulling liquidity from TradFi only when a trade happens, Native enables issuers and LPs to provide inventory while market makers proactively quote on orderbooks. That allows pricing to continue during off-market hours and makes real onchain price discovery possible.

Among onchain liquidity models, AMMs are not capital-efficient for tokenized stocks, while RFQ + CLOB is the structure that can support an orderbook-based secondary market. Native is the first onchain spot liquidity DEX to combine RFQ + CLOB for this market.

### Institutional liquidity infrastructure for RWA markets

Native Core is the onchain orderbook where market makers quote proactively and price discovery happens continuously. Native Relay distributes that liquidity into wallets, aggregators, and trading interfaces.

Behind the market, Native Pool allows issuers and LPs to supply liquidity that can be loaned to market makers. Through cross-margin access, market makers can quote tighter spreads and support deeper books, while LPs participate through single-sided liquidity with no impermanent loss. This is what makes real 24/7 onchain trading possible.

{% hint style="info" %}
Fill out this [form](https://docs.google.com/forms/d/e/1FAIpQLSdyOZGlRzB9A31qh-ryrqdHlSpJDPz-lTDqZ8t40e19WHQyTw/viewform), and the Native team will be in touch.
{% endhint %}


---

# 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.native.org/native-dev/build-with-native/asset-issuers/for-pegged-assets.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.