# 1.2 Problems of DEX

1\. There are too many DEXs operating in the market, with different chains and wallets, but new users don’t have a one-stop platform.

2\. User interfaces of web-based DEXs are usually complex and not user-friendly.

3\. Tokens & Pairs selection process on web-based DEX is too complicated.

4\. Not enough data for trading or decision making; traders require more information such as charts, liquidity data, order history, real time filled orders, user positions, APY, etc.

5\. Lack of deep and valuable data like hot trading pairs, newly listed pairs, liquidity rank, etc. where traders can find the invaluable opportunities they are looking for to make them rich.

6\. Trading procedure like pancakeswap cost too much time, usually 10 seconds.

7\. To exchange USDT between diffenert chains, you need to find other Apps.

8\. We can't do planned order on DEX.

![](/files/-Mhrt3b6zDJqT3DbGgA1)


---

# 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://msgsender-2.gitbook.io/msgsender/master/why-do-we-need-a-solution-for-current-dexs.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.