> For the complete documentation index, see [llms.txt](https://dexrise.gitbook.io/dexrise-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dexrise.gitbook.io/dexrise-documentation/introduction/how-it-works.md).

# How DEXRise Works

DEXRise brings together three building blocks: a unified trading interface over multiple decentralized exchanges, its own native liquidity pools, and fully on-chain execution for every service it offers. Understanding these three layers makes it easy to see how each feature fits into the platform.

## Trading across multiple platforms

DEXRise connects to several major decentralized exchanges, including **PancakeSwap**, **Uniswap**, **SushiSwap** and others. Through the DEXRise interface, you can trade on liquidity pools that belong to these external platforms — while benefiting from a simple, easy-to-use experience and rich detail about each trading pair.

In practice, this means you keep the depth of established DEX liquidity, but with a cleaner interface, protective settings such as [Slippage Protection](/dexrise-documentation/trading/slippage-protection.md), and transparent [trading fees](/dexrise-documentation/trading/trading-fees.md) that depend on the pair type you are trading.

## Native and shared liquidity

DEXRise also operates **its own liquidity pools**. These native pools power the platform's own trading pairs — including [DXR](/dexrise-documentation/dxr-token/overview.md) pairs — and they are not closed off: any other platform can use DEXRise's pools to share liquidity.

This makes DEXRise liquidity a two-way resource: traders on DEXRise benefit from pools connected to the wider ecosystem, and external platforms can plug into the same liquidity.

## On-chain by design

Every core operation on DEXRise settles directly on the blockchain:

| Operation                                       | How it executes   |
| ----------------------------------------------- | ----------------- |
| Staking deposits, withdrawals and reward claims | Directly on-chain |
| Presale purchases                               | Directly on-chain |
| Airdrop claims                                  | Directly on-chain |

This on-chain execution model means the platform's operations are transparent and verifiable, with no black-box processing between the user's action and the blockchain result.

## How a trade flows through the platform

| Step | What happens                                                                                                                                                                                                           |
| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1    | You open a trading pair on the [DEXRise Trade Panel](/dexrise-documentation/trading/trade-panel.md)                                                                                                                    |
| 2    | The pair is connected to a liquidity pool — either a [DEXRise native pool](#native-and-shared-liquidity) or a pool belonging to an external platform                                                                   |
| 3    | The swap executes on-chain against that pool's live price                                                                                                                                                              |
| 4    | Your protective settings (e.g. the [slippage limit](/dexrise-documentation/trading/slippage-protection.md)) and the pair's [fee](/dexrise-documentation/trading/trading-fees.md) apply according to the pair's profile |

{% hint style="info" %}
The type of pair you trade determines its features and fee rate. See [Trading on DEXRise](/dexrise-documentation/trading/overview.md) for the two pair categories available on the platform.
{% 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 by asking a question.

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

```
GET https://dexrise.gitbook.io/dexrise-documentation/introduction/how-it-works.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.