Why Does a Larger Fraxswap Swap Get a Worse Rate?
Fraxswap gives a larger swap a worse rate because each added unit of input shifts the pool’s reserves further from their starting balance. The fee is a separate, fixed percentage; the extra loss comes from trade size relative to available reserves, so the same order has less impact in a deeper pool.
How Reserve Shifts Change Your Output
A constant-product pool holds two token reserves, and their product, x·y = k, sets the price curve. If the pool starts with x units of your input token and y units of the token you want, a larger input pushes the reserves further along that curve: you receive progressively less output for each additional unit.
For input Δx and fee rate f, the estimated output is (Δx·(1−f)·y) / (x + Δx·(1−f)). The formula uses the input after the fee to calculate output; the fee itself remains in the pool. Uniswap v2 Core whitepaper (2020), by Hayden Adams, Noah Zinsmeister and Dan Robinson, describes this fee-adjusted constant-product calculation for its pair design. It explains the mechanism, though a live quote can also depend on the route and current reserves.
When choosing a route, compare pool reserves before sending the trade. The Fraxswap liquidity in a candidate pool matters because deeper reserves make the same order a smaller share of the pool, usually reducing the price movement you cause.
Separate the Fee From Price Impact
The fee is charged as a percentage of the swap, while price impact grows with the size of your input relative to the pool. A quoted rate can therefore worsen even when the fee has not changed. The app’s price impact estimate shows the expected effect of your trade on the pool price.
- Fee: the pool’s percentage charge on the trade.
- Price impact: the rate change caused by moving the reserves.
- Slippage: the difference between the estimate and execution if conditions change before confirmation.
These are distinct: the fee applies to the swap, price impact follows from its size, and slippage can add uncertainty between quote and execution. For example, if a quote worsens as you increase an order while the fee stays constant, the pool’s reserves are likely driving the difference.
Choose a Sensible Trade Size
For a large order against thin reserves, I would compare routes or use a longer execution window instead of sending one instant swap. Splitting an order can help you manage execution, but repeated swaps against the same pool still move its reserves and incur fees; splitting alone does not remove price impact. A time weighted order, such as a TWAMM order where available, spreads execution over time and can reduce the immediate demand placed on one pool.
Use the quoted impact and reserve depth to judge whether the rate is acceptable: deeper pools absorb more size, while small pools move sharply as Δx approaches x. The fee tells you the pool’s charge; the reserve shift tells you why your larger swap gets a worse rate and whether to reroute or spread it out.
Comments
Post a Comment