A pool’s token order is an internal label, not a different market price: the same pool can quote a trade in either direction. When you swap from your wallet, compare the amount you will receive after pool fees, price impact and network cost; the pool’s displayed pair order alone does not tell you which route is better.
What does a pool’s token order mean?
Pool contracts assign two assets the labels token0 and token1, usually by sorting their contract addresses. That order is fixed for the pool, even if an app displays the pair with the other token first. The swap direction is a separate detail: a trade can send token0 and receive token1, or send token1 and receive token0.
For example, a pool labeled USDC/WETH in one interface may appear as WETH/USDC elsewhere. Check the token symbols and, when there is any doubt, their contract addresses. Reversing the display order does not create a second pool or change its reserves; swapping the direction changes which asset goes in and which comes out.
This is useful context when how ParaSwap compares and completes swaps comes up: an aggregator can compare available routes, but you still need to read each quote as the same question—how much of your desired token arrives for the amount you spend? ParaSwap presents the result in your chosen input and output tokens, not as a token0/token1 puzzle.
How does reversing direction change the quote?
Reversing direction changes the pool calculation, because the input and output reserves switch roles. In a basic constant-product pool, the reserves roughly follow x × y = k: taking one token out changes the ratio and moves the price. A larger trade compared with the pool’s depth gets a worse average rate, in either direction.
Say a pool holds 3 million USDC and 1,000 WETH, and you trade 100,000 USDC for WETH. Ignoring fees, the constant-product calculation gives about 32.26 WETH: 1,000 × 100,000 ÷ (3,000,000 + 100,000). With a 0.30% pool fee, the output is roughly 32.16 WETH. These figures are illustrative; real pools may use different pricing rules and fees.
Now reverse the trade: putting WETH in and taking USDC out starts from the WETH reserve and applies the fee to the WETH input. You cannot simply flip the displayed exchange rate and expect the reverse trade to return the original amount. Fees and price impact make the two directions asymmetric.
What should you compare across routes?
Compare the estimated amount received for the same input, on the same network. A route may use one pool or several, and an aggregator can split an order across pools. Pool depth, fee tier, trade size and intermediate swaps all affect the result; the order in which a pair’s symbols appear does not.
For a practical comparison, look at the net output and the costs behind it:
- Pool fee: charged by the liquidity pool and reflected in the swap calculation.
- Price impact: the price movement caused by your trade size relative to pool depth.
- Network fee: gas paid to execute the transaction; a split or multi-pool route can require more work.
- Minimum received: the slippage-protected floor set for execution, which can be lower than the quote.
A route with a better pool rate can still leave you with less after network costs. For a small trade, an extra hop or split may cost more gas than it saves; for a larger trade, splitting may reduce price impact enough to pay for that extra execution. The best route depends on your trade size and current network conditions.
How do you check a quote before signing?
Confirm the input and output token, network, amount, estimated output and minimum received in your wallet or swap interface. Then check that the token addresses match the assets you intend to trade, especially if similar names or symbols appear. ParaSwap can help compare routes, but a quote is an estimate until the transaction executes.
I would compare the final output and gas estimate first, then inspect the route if the result seems surprising. Keep the trade within a slippage limit you can accept: a lower minimum received reduces the chance a price move causes the transaction to fail, while a very loose limit may let it complete at a worse rate. Before signing, treat token order as a labeling convention and judge the route by what you spend, what you receive and what execution costs.