TxWhy

Error codes / Lighthouse

AssertionFailed

Lighthouse · Custom(6001) · 0x1771

custom program error: 0x1771

What it means

The failing instruction is a safety guard added by the wallet or trading app that built this transaction (Lighthouse, the open-source assertion program). What it required was no longer true at execution, so it aborted the whole transaction before anything else ran. This is not Jupiter's slippage error, although it shares the number 0x1771: the state the app previewed (a balance, a pool reserve, or a deadline) changed before the transaction landed.

The program's own message: “A state guard placed by the wallet or app did not hold at execution”

What to do

Nothing was swapped or moved; only the network fee was paid. Build a fresh transaction in the app so it previews current state and sets new guards. If it keeps tripping on a fast-moving token, the app's guard range is tighter than the market is moving: raise the app's slippage or protection setting rather than retrying the same transaction.

Have the transaction that failed with this?

Paste its signature. TxWhy shows the exact instruction and inner call that raised the error, and rebuilds the transaction when the cause is one it can fix (compute limit, expired blockhash, priority fee, stale swap quote).

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.