TON DEX Pool Depth: Why Trade Size Changes Execution remains the main reference point for users and Telegram Mini App developers following this update.
When trading on a decentralized exchange (DEX) like STON.fi, the depth of the liquidity pool is a key factor that determines the actual execution price of your trade. Token swaps don’t rely solely on listed prices—what matters most is how much liquidity backs the pool and how your order size interacts with that liquidity. If your trade is large relative to the pool's reserves, price slippage can increase significantly, resulting in a worse execution price.
Many users focus on the displayed token price and ignore pool depth, leading to unexpected outcomes—especially for larger swaps. Always compare your trade size to the total liquidity available and check the estimated output shown in the swap preview before confirming any significant transaction.
How Pool Depth Directly Affects Your Swap
On DEXs like STON.fi, every swap reduces one side of a liquidity pool and increases the other. That means a large trade can push the token price in the pool further away from the “headline” or displayed rate. This phenomenon—known as price impact—explains why a swap for a small amount may yield a different rate than a swap for a much larger amount, even seconds apart.
STON.fi advises traders to verify the actual token output quoted for their intended swap size before proceeding. Even moderate increases in trade size can drop your effective output if the underlying pool is thin. When facing limited liquidity, consider breaking large trades into smaller pieces or looking at alternative pools with more depth to minimize slippage.
Ignoring pool depth and simply relying on listed rates can cause hidden losses at the time of execution. Always preview the quoted output for the exact amount you are swapping.
What Happens When You Trade Large on Low-Liquidity Pools
A large swap on a pool with limited liquidity can trigger high price impact, causing your effective rate to diverge sharply from what you’d expect based on the market price. What’s displayed as the current price is typically calculated for minimal trade sizes. If you place a large order, the AMM formula will shift the pool’s internal balance enough to pull the rate against your favor.
This means two users swapping different trade sizes back-to-back might receive significantly different token output, even if the “market price” appears the same. Checking the detailed quoted output before confirming a swap is critical for asset managers and active traders. If the previewed output drops unexpectedly, consider either reducing your trade size or splitting your transaction.
Steps Before Executing Token Swaps on TON DEXs
Before confirming a swap on any TON decentralized exchange, do more than glance at the token’s listed price:
- Check the quoted token output for your specific trade amount; this reflects pool depth and current rate after price impact and fees.
- For unfamiliar or newer pools, look for data on liquidity reserves, 24h trading volume, and TVL when available.
- Be cautious of pools with low or volatile liquidity, as even moderately sized trades may result in large slippage and poor execution.
- Use the swap preview to see final output. If there’s a large difference from your expectations, try breaking the order into smaller chunks.
Unlike centralized exchanges, AMMs base rates on real-time pool balances. Even small changes in trade size can noticeably affect your swap output, especially in thin pools.
Testing a smaller trade first can provide a quick check on price impact and help avoid outsized losses due to insufficient liquidity.
For more technical and practical user guides, see TON tools and DeFi.
TON DEX Pool Depth: Why Trade Size Changes Execution remains the main reference point for users and Telegram Mini App developers following this update.
TON DEX Pool Depth: Why Trade Size Changes Execution remains the main reference point for users and Telegram Mini App developers following this update.
Source reference: original source.