Treasury Swap Size and Pool Depth Explained
A treasury swap size should be capped by the pool’s quoted output, not by a fixed dollar amount. The same trade can be cheap in a deep pool and costly in a shallow one, so check the route and execution cost each time you trade.
If the swap is part of a wider treasury decision, how QuickSwap handles treasury swaps is useful when weighing a spot conversion against liquidity provision. For sizing a spot trade, start with the pool’s reserves and the quote for your intended amount.
How does pool depth set your trade size?
Pool depth is the amount of each token available in the pool; in a constant-product pool, a trade changes their ratio. The Uniswap V2 whitepaper describes the invariant as x × y = k: as the pool gives out one asset, its balance falls and the relative price of that asset rises.
That price movement is called price impact. It grows with the trade relative to the pool’s reserves, and the pool’s swap fee also reduces the amount you receive. A large treasury order can therefore cost more than the displayed spot price suggests, even before network fees.
For example, imagine a pool with $500,000 of each asset and a $10,000 swap into it. Ignoring the fee, the constant-product formula returns about $9,804 worth of the other asset, roughly 1.96% below the mid-price value. With a 0.30% pool fee as an illustration, the output falls to about $9,755, or around 2.45% below mid-price. The actual quote depends on the pool’s fee and current reserves.
How do you choose a maximum order size?
Choose a price-impact ceiling that fits the treasury’s policy, then get quotes at several sizes until the quote stays within that limit. The ceiling is a control, not a universal market standard: a liquid stablecoin conversion may justify a tighter cap than a volatile asset trade with less depth.
For a quick what-if, suppose your policy allows at most 0.75% price impact. Quote $2,000, $5,000, and $10,000 against the intended route. If $5,000 comes in below the ceiling but $10,000 does not, set the single-trade limit near $5,000, then check whether the extra transactions required to convert the full amount are worth their added network cost.
Compare the expected output with a reference price from a reliable market source, not just the pool’s own spot price. A pool can be thin or temporarily out of line with the wider market; an attractive quote against a stale or distorted reference does not make the trade cheap.
When should you split a swap, and what do you check?
Splitting helps when each smaller trade gets a better route or lets liquidity recover between executions; it does not automatically reduce total price impact. In an untouched constant-product pool, splitting one order into several back-to-back trades produces nearly the same cumulative pool movement, while each transaction may add network fees.
On QuickSwap V2, check the selected network, token addresses, route, pool fee, quoted output, and minimum received before signing. The minimum received is the output floor implied by your slippage tolerance: set it tight enough to reject a materially worse execution, but expect a transaction to fail if the market moves beyond it before confirmation. Pool fees and network costs are separate parts of the trade’s total cost.
For recurring conversions, record the quote, reference price, price impact, pool fee, network fee, and fill result. I would use a per-trade impact ceiling and compare the all-in cost of splitting against one order; that keeps the rule quick to apply while tying it to the pool and network conditions at execution time.