JUMPBIT
Open app
FixesUpdated 23 Oct 20261 min read

Raydium "Price slippage check" error 6017 (0x1781)

The fix

On a Raydium concentrated (CLMM) pool, the price moved past the limit set by your slippage or price range before the instruction ran. When adding one-sided liquidity, a range that starts on the current tick also triggers it.

Tools covered

  1. RaydiumRaydium is a Solana DEX with AMM v4, CPMM and CLMM pools and LaunchLab, documented with a published fee table.UpVisit

What the error means

Error Code: PriceSlippageCheck. Error Number: 6017. Error Message: Price slippage check

On a Raydium concentrated (CLMM) pool, the price moved past the limit set by your slippage or price range before the instruction ran. When adding one-sided liquidity, a range that starts on the current tick also triggers it.

Where it comes fromRaydium CLMM program
Code6017 (0x1781); related 6018 TooLittleOutputReceived, 6019 TooMuchInputPaid

How to fix it

  1. Swaps: raise slippage a little, trade smaller or retry with a fresh quote.
  2. Adding liquidity one-sided: start the range at least one tick spacing away from the current price.
  3. Retry when the pool is less volatile.

If that is not it

  • On CPMM or AMM v4 pools, slippage failures show as "Exceeds desired slippage limit" instead, see Raydium slippage limit.

More fixes: how to decode any Solana error code and why Solana transactions fail.

Source

Error text and code from Raydium CLMM error definitions (raydium-io/raydium-clmm), read on 24 October 2026.

Questions people ask

What is Raydium error 0x1781?

CLMM error 6017, Price slippage check.

Why does adding liquidity fail with it?

A one-sided range that touches the current price; move it one tick spacing away.

Raydium "Price slippage check" error 6017 (0x1781) | Jumpbit