# How it Works ## Intro TON DEXes have fragmented liquidity, each with its own set of liquid tokens. As the TON ecosystem grows, this uneven distribution worsens, leading to inefficient trades and arbitrage opportunities. Users often lose money due to the high price impact when swapping tokens on a single DEX. ## Problem Imagine you want to swap 100 TON for a NOT token. To get the best price, you need to compare offers across different DEXes. First, you need to know which DEXes have the tokens you want to swap (new DEXes are constantly emerging, and we’ve already secured agreements to integrate them into our routing algorithms). Let’s take a look at what the two biggest players in the market, DeDust.io and Ston.fi, offer:

In this case, Ston.fi offers a better amount of NOT. But what if I told you that we could get an even better price using their liquidity pools? ## Solution Rainbow Swap distributes trade volume across optimal routes to minimize price impact and slippage. This ensures you get a better price in a single transaction.

Here, you will receive an extra 97 NOT (+0.16%) by splitting your trade into 2 parts: sending 61.6 TON to the Ston.fi pool and 38.4 TON to the DeDust.io pools. Price improvement would depend on the tokens you want to swap and the amount of liquidity in DEXes pools. Here are a few price improvement examples:

## Conclusion Earn more and forget about constantly tracking all DEXes simply by using Rainbow Swap. Our user-friendly interface allows seamless swaps with the most efficient routes, considering swap distribution and gas costs. --- # 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://rainbow-ag.gitbook.io/docs/introduction/how-it-works.md?ask= ``` 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.