NOT AFFILIATED
Technical

Slippage - Trading Glossary

The gap between the price you expected and the price you actually receive.
Published:
Updated:
trading execution bnb-chain glossary definition

Slippage

The gap between the price you expected and the price you actually receive.

Slippage measures the difference between the price you saw when submitting an order and the price the market gave you. On AsterDEX this applies to Perpetual Pro orders, 1001x Simple intents, and any swap routed through BSC Chain liquidity.

What Drives Slippage

  • Depth available: shallow order books or AMM pools cannot absorb size.
  • Speed of movement: high volatility moves price between order submission and fill.
  • Competition: other traders or bots hit the book first, displacing your order.
  • Routing logic: aggregators may split across pools; if one runs dry, you pay more.

Slippage Benchmarks for Aster Traders

Market TypeTypical Tight SettingWhen to Widen
Perpetual Pro majors0.1%–0.3%During news spikes or thin sessions
New 1001x Simple listings0.5%–1%Campaign launches, low-liquidity hours
Long-tail AMM swaps1%–3%Microcaps or meme tokens

Defensive Techniques

  • Use limit/post-only orders on Perpetual Pro to guarantee price.
  • Split intent size when using 1001x Simple; send in tranches.
  • Check pool depth on PancakeSwap/Wombat before large swaps.
  • Leverage MEV-protected RPCs so bots can’t sandwich your trade.

Calculating Slippage

Slippage % = ((Fill Price – Expected Price) / Expected Price) × 100

Log this for every trade. If slippage consistently exceeds expectation, adjust entry method or time of day.

Slippage vs. Price Impact

  • Price impact is the theoretical move caused by your size in a perfect world.
  • Slippage is the real-world outcome including latency, MEV, and competition.

You control impact by sizing and venue choice; you control slippage by execution technique.

Checklist Before Sending a Large Order

  1. Review live depth and open interest.
  2. Set a max slippage tolerance that keeps the trade profitable.
  3. Consider staging with TWAP or intent batches.
  4. Monitor execution reports—if fills deviate, pause and reassess.

Slippage is unavoidable, but disciplined execution keeps it manageable and predictable.