# Routes and steps

With default router settings your swap splits into up to 4 different routes and 2 steps in each route.

{% hint style="info" %}
If you wish to make a direct swap, involving only one pool, choose maximum 1 route and 1 step in it.
{% endhint %}

<div><figure><img src="/files/drsC40F2KvhUTUXWIlw6" alt=""><figcaption></figcaption></figure> <figure><img src="/files/9E9Sz9grZumKtCIEhdQg" alt=""><figcaption></figcaption></figure> <figure><img src="/files/ZSvt6RfofAtmrUN3a4R6" alt=""><figcaption></figcaption></figure></div>

The more routes and steps you allow, the more efficient your swaps will be. But it increases [slippage](/en/trade/advanced/slippage.md) probability on any of the steps, and you may get some intermediate tokens instead of expected ones.

{% hint style="info" %}
Currently each of the four separate routes executes multi-step trade within pools of the same protocol. Technically, [CPMM v2](/en/liquidity/pools/types.md#claimable-fees-pool-cpmm-v2) and [Classic](/en/liquidity/pools/types.md#classic-pool-cpmm-v1) pools (or [Stable-swap](/en/liquidity/pools/types.md#stable-swap-pools)) are also two "different" protocols, which can't be involved together within one single route.
{% endhint %}

{% hint style="success" %}
If you need to swap, for example, **TON —> BOOM**, while:

* BOOM token's liquidity is paired with USDT only, specifically in CPMM v2 pool, and
* there's poor liquidity in TON/USDT pools of CPMM v2 type (unlike in Classic TON/USDT pool), but
* there are liquid CPMM v2 pools DUST/TON and DUST/USDT, that can be involved for efficient swap,

consider allowing 3-step route: **TON —> DUST —> USDT —> BOOM**, insted of 2 steps allowed by default.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://help.dedust.io/en/trade/router/settings/routes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.