[ Uniswap V3 Arbitrum ] USDC routing issue on the interface

Hello,

We have a pool on Arbitrum, on Uniswap V3 : 0xc09254d1be9c3b7335021873546ba480383981d9 .
It's REUNI / USDT.

There are other pools with very low liquidity, less than $100, such as REUNI / USDC.

Because of this, your interface is unable to find the best possible route.

Let me explain :

• If a user wishes to exchange 100 USDC for REUNI, your interface will suggest going through the very low liquidity pool, leading to a loss of 50-80%.
• On the other hand, for any other tokens, USDC.e, USDT, etc., the interface understands that it is necessary to route through the pool with the most liquidity.

Here are two images to illustrate the problem.

Wrong routing

Correct routing

Solution :

• Optimize transaction routing by selecting by default the pool with the most liquidity, and/or offering several routes.

Some of our users, who wish to purchase with USDC, do not understand this recurring problem for several months.

Regards,

Start by reproducing the reported USDC-to-REUNI swap on Arbitrum using pool 0xc09254d1be9c3b7335021873546ba480383981d9 and compare its route with the displayed USDT, USDC.e, and other-token routes. Done means the interface no longer selects the low-liquidity REUNI/USDC pool when the higher-liquidity REUNI/USDT route is better, or clearly offers the relevant alternatives.