Pcswap
Pcswap slippage
last updatedPancakeSwap uses slippage tolerance to limit the adverse price change an AMM swap can accept between quote and execution. For a failed AMM swap, check its output limit and trade size alongside token transfer rules, gas and the transaction deadline before increasing tolerance.
Slippage, Price Impact and Minimum Received
- Slippage
- The difference between the price expected from a quote and the price achieved when the swap completes.
- Price impact
- The effect of your own trade on the pool price. An order large relative to available liquidity can cause substantial impact.
- Minimum received
- For a fixed-input AMM swap, the lower output limit, expressed in the output token. Execution must meet this limit for the swap to succeed.
An AMM quote reflects the selected amount and route. Price impact can make that quote unattractive before any delay occurs. Other transactions can then change pool reserves before your swap executes, changing the output available at execution. In a hypothetical 100 CAKE swap, a quoted rate of 0.01 BNB per CAKE gives 100 × 0.01 = 1 BNB. Execution at 0.0098 BNB per CAKE gives 100 × 0.0098 = 0.98 BNB, a shortfall of (1 - 0.98) / 1 × 100 = 2%. The swap would fail its output check if minimum received were above 0.98 BNB.
Increasing tolerance lowers the minimum output accepted for the same fixed-input quote. It leaves more room for adverse movement without improving the quoted price or adding liquidity. Trading fees are a separate cost; the full permitted slippage is not automatically deducted from every swap.
Tolerance Choices and Routing Settings
A tight tolerance makes an AMM swap more likely to revert when prices move adversely between quoting and execution. A wider tolerance permits a worse result. The relevant setting depends on the output floor you accept, the token’s transfer mechanics and the liquidity available for that amount.
For AMM swaps, PancakeSwap offers Fixed Slippage and Auto Slippage in the Swap settings. Fixed Slippage lets you choose a percentage. Auto Slippage uses gas cost relative to the output’s USD value and selects a tolerance from 0.5% to 5% on supported Layer 1 chains such as BNB Smart Chain and Ethereum. Auto Slippage is not supported on Layer 2 chains; the previous setting applies, or 0.5% if none exists. Review the resulting minimum received before confirming a change. A percentage copied from an older tutorial or a different token does not establish an appropriate limit for the selected swap.
Exchange V3 routing has separate controls for liquidity sources, multihops and split routing. Disabling multihops restricts execution to direct swaps, while disabling split routing restricts execution to a single route. These restrictions can worsen execution or leave no usable route. A routing-configuration warning calls for reviewing those settings.
Failure Conditions
-
INSUFFICIENT_OUTPUT_AMOUNT - The swap cannot satisfy its output requirement. PancakeSwap associates this error with insufficient tolerance or low liquidity. Token transfer fees and restrictions can also prevent the expected amounts from reaching their destinations.
- High price impact
- A large trade relative to pool liquidity can produce a poor execution estimate. On Aptos, a price-impact warning can also arise from poor connectivity to blockchain nodes. Refresh the page and check your network connection; a persistent warning can indicate insufficient liquidity for the amount.
-
PancakeRouter: EXPIRED - The transaction has passed its deadline. Continuing a planned swap requires a fresh transaction with a valid deadline and a reviewed quote. Increasing tolerance does not extend the expired deadline. For an unexpected airdrop token, do not grant approval merely to troubleshoot this error.
- Insufficient gas, balance or allowance
- BNB is required for network gas on BNB Smart Chain. The wallet also needs sufficient input tokens and, where token allowance is required, authorization covering the intended spend. Slippage settings do not supply those balances or permissions.
An on-chain revert can still consume network gas, so repeated failed attempts can add costs.
Token Taxes and Selling Restrictions
An inclusive transfer tax diverts part of a transfer, reducing the amount its recipient receives. An exclusive tax requires an additional transfer from the sender. Either mechanism can affect the input or output requirements a swap must meet.
A compatible swap may need tolerance accommodating both the token tax and ordinary price movement. A wider limit does not remove the tax or establish compatibility with a route. Some token contracts block transfers or permit only selected addresses to sell; tolerance cannot override those restrictions.
TWAP Orders and PancakeSwap X
PancakeSwap TWAP divides an order into smaller trades over time. Smaller chunks can reduce each trade’s price impact, while more transactions increase overall gas costs. Market prices can move during execution and taker fees are deducted from output tokens. A TWAP limit order can remain partially filled when its price condition is unmet, and remaining trades expire at the order’s maximum duration.
PancakeSwap X can show zero price impact for eligible swaps. Its availability depends on the input and output tokens, trade size and network. PancakeSwap X fillers commit to an execution price when they accept an order, so the displayed slippage setting does not apply to X execution. A swap X cannot process falls back to AMM liquidity pools, where the slippage setting applies; the X zero-impact display does not describe that route.
Slippage Decision Checklist
- If the quote already shows high impact, compare a smaller amount and available routing before accepting a wider tolerance.
- If output falls below the execution limit, refresh the quote and inspect minimum received. Increase tolerance only if the revised floor is acceptable.
- If the token has transfer taxes or selling restrictions, establish its rules and route compatibility before retrying.
- If the error concerns gas, allowance or expiry, resolve that requirement before submitting another swap.
