TxWhy

Error codes / Jupiter Aggregator v6

SlippageToleranceExceeded

Jupiter Aggregator v6 · Custom(6001) · 0x1771

custom program error: 0x1771

What it means

The swap would have paid out less than the minimum this transaction allowed (or cost more than its maximum). The price moved between the moment the quote was taken and the moment the transaction executed, by more than the slippage tolerance set in the swap.

The program's own message: “Slippage tolerance exceeded”

What to do

Get a fresh quote and resend with the same tolerance; the price has moved on. Widen the tolerance only if it keeps failing on a fast-moving token, and know that a wide tolerance is what sandwich bots feed on.

Seen on mainnet

About half of what explorers label with this code is not Jupiter at all: the Lighthouse guard program that wallets append uses the same number, 6001, for a failed assertion, and a guard cannot be repaired, only explained. TxWhy tells the two apart from the failing program. For a real Jupiter slippage failure it asks Jupiter for a fresh quote for the same tokens, amount and tolerance, replaces only the swap instruction, and refuses a route over 3% price impact or a quote more than 25% worse than the original.

From replaying real landed failures through the repair engine, around the clock since September 21, 2026. Every verdict and its reason is on the failure index.

TxWhy can repair this one

When the swap was routed through Jupiter, TxWhy replaces only the stale swap instruction with a current quote for the same tokens, amount and slippage tolerance, keeps every other instruction byte for byte, and proves the result passes simulation.

Code 6001 means something else in other programs

Custom codes are private to each program. Check which program actually raised it: it is the innermost failed call, not necessarily the program you called.