Two things go wrong when buying a new Solana token: the transaction fails outright, or it succeeds at a price noticeably worse than expected. People treat both as the same problem and reach for the same fix — raise slippage tolerance. That fix addresses one of them and quietly makes the other worse, because slippage and price impact are not the same thing.
Price Impact Is Caused by You
Price impact is how much your own trade moves the price, and it's determined entirely by your trade size relative to the pool's liquidity. Buy an amount that's small against the pool and impact is negligible. Buy an amount that's large against it and you are, mechanically, the thing pushing the price up as you fill.
This is why price impact is predictable before you trade, and why no tolerance setting helps: raising slippage tolerance doesn't reduce impact, it just permits it. The only levers are trade size and pool depth — which makes liquidity the number to check before you decide how much to buy, not after. Our meme coin glossary covers how to read that number against market cap.
Slippage Is Caused by Everyone Else
Slippage is the gap between the price when your transaction was built and the price when it actually landed on-chain. In that window — often under a second — other people traded, and the pool moved. Slippage tolerance is simply the instruction you attach: how far the price may move against you before the transaction should cancel itself instead of executing.
Which reframes the failure most people find frustrating. A swap that reverts because the price moved past your tolerance isn't broken — it's the protection doing exactly its job, refusing a fill you said you didn't want. On a token moving fast enough to be interesting, that will happen regularly.
Why Raising Tolerance Backfires
Setting a very wide tolerance does stop the failures — by removing the condition that was cancelling them. What remains is a transaction that will execute at almost any price, which is a different cost that simply doesn't announce itself as an error.
It also has an adversarial dimension. Your pending transaction is public, and a wide tolerance is a public statement of exactly how much worse a price you'll accept. That's the precise information a sandwich-style attack needs: buy ahead of you, let your order fill at the inflated price your own tolerance permitted, sell into it. The wider the tolerance, the more profitable you are to target.
Setting Tolerance Sensibly
There's no universal correct number, because the right tolerance depends on how fast the token is actually moving. The useful principle is to treat tolerance as a maximum acceptable cost rather than a dial you turn up until transactions stop failing. If a token requires an uncomfortably wide tolerance to fill at all, that's information about the token's volatility and pool depth — information worth acting on rather than overriding.
The same logic applies to trade size. A position sized sensibly against pool liquidity has low impact and needs less tolerance, so the two problems shrink together. This is one more reason liquidity appears in every DexsAlertBot alert alongside price and market cap: it's the number that determines both what your trade will cost to execute and whether you could exit it later.
One caveat worth carrying: a swap that fails repeatedly isn't always about volatility. If sells specifically never go through while buys work fine, that's the signature of a honeypot, not a tolerance problem — and no setting will fix it.
Before you set tolerance
- Check pool liquidity first — it decides your price impact
- Size the trade against the pool, not against your ambition
- Treat a failed swap as protection working, not as an obstacle
- Remember a wide tolerance is public — it advertises what you'll accept
- If only sells fail, stop adjusting settings and check for a honeypot
Frequently Asked Questions
What is the difference between slippage and price impact?
Price impact is how much your own trade moves the price, determined by your trade size relative to pool liquidity. Slippage is how much the price moved for other reasons between building your transaction and it landing. Raising slippage tolerance does nothing about price impact.
Why does my Solana swap keep failing?
A common cause is slippage tolerance set tighter than the price actually moved before the transaction landed, so the transaction reverts to protect you. On fast-moving new tokens this happens frequently, and it is the protection working rather than a bug.
Is setting high slippage tolerance dangerous?
It can be. A wide tolerance tells the network you will accept a much worse price, which both guarantees a poor fill in volatile conditions and makes you a more attractive target for sandwich-style attacks that profit from that acceptance.
How do I reduce price impact on a thin pool?
Reduce trade size relative to the pool, or split the trade. Price impact is a function of your size against available liquidity, so checking liquidity before trading is the only reliable way to anticipate it.
Liquidity in every alert
DexsAlertBot shows pool liquidity alongside price and market cap, so you can judge impact before you trade — free, on Telegram.
Open DexsAlertBot →⚠️ This article is educational and not financial advice. Execution behaviour varies by wallet, aggregator and network conditions — always do your own research (DYOR).