Split trades can reach more pools if the router counts shared reserves once. This matters when you are comparing ways to swap a large amount: separate routes can improve your price, but overlapping routes can make available liquidity look deeper than it is.
Splitting a trade can soften its price impact
A router can divide your order among pools to avoid pushing the whole amount through one pool. A liquidity pool holds tokens for people to trade, and its price shifts as those reserves change.
For example, imagine two separate pools each hold 1,000 A and 1,000 B, with no fees. Selling 200 A into one pool returns about 167 B; selling 100 A into each returns about 182 B combined. The split gets a better price because neither pool takes the full trade.
If you are comparing a larger swap across separate sources, ParaSwap can quote routes that split the order. Compare the estimated amount you receive after network costs, since extra pool calls can use more gas—the fee paid to process a transaction.
Shared reserves can make a route look better than it is
Shared reserves are tokens that more than one candidate route would draw from. A route is the sequence of pools a swap follows; two routes may seem separate while relying on the same pool for one step.
Suppose one candidate sends A through an A/B pool, then B/C. Another sends A through that same A/B pool. The router cannot safely add both quoted outputs as if each route had an untouched A/B pool: the first trade changes that pool’s reserves and price for the next one.
A sound quote simulates the combined trade against each pool’s changing state, then checks the final output and minimum acceptable amount. This is the edge case that decides whether a split is real: routes must use independent liquidity, or the router must account for their overlap.
Choose by net output and route overlap
For a small trade, one direct pool may win because the price improvement from splitting does not cover the added gas. For a larger trade, splitting across independent pools can offset price impact enough to leave you with more tokens after costs.
Pool design affects that cost. The Uniswap v4 whitepaper describes a single contract that manages many pools and tracks temporary balance changes before settlement. That shared contract can reduce work between pools, but each pool still has its own state and reserves; one pool’s liquidity is not automatically available to another.
The ParaSwap API is one way to compare routes across sources, but the useful result is the net quote for your amount and chain. Choose a split when its gain after gas is clear and the routes do not count the same reserves twice; choose differently when the trade is small, routes overlap, or the quote’s minimum output is too low for your needs.
Top comments (0)