Solana error codes › 0x177a

custom program error: 0x177a (6010)

0x177a is decimal 6010. Its meaning depends on the program that failed: InvalidRoutePlan in Jupiter Aggregator v6, AccountTypeNotSupported in Pump.fun Bonding Curve, InvalidLpMint in PumpSwap AMM and 27 more below.

Programs that use Anchor-style numbering start their own error list at 6000 (0x1770), so 6010 is the error at index 10 of the failing program's list. The same number means something different in every program.

0x177a by program

ProgramError
Jupiter Aggregator v6InvalidRoutePlan
Invalid route plan
Pump.fun Bonding CurveAccountTypeNotSupported
Account type not supported
PumpSwap AMMInvalidLpMint
Raydium CPMM (CP Swap)TransferFeeCalculateNotMatch
TransferFee calculate not match
Raydium AMM V3 (CLMM)TickAndSpacingNotMatch
tick % tick_spacing must be zero
Meteora DLMMInvalidTokenMint
Invalid token mint
Meteora CP AMM (DAMM V2)InvalidActivationType
Invalid activation type
Meteora Dynamic Bonding CurveInvalidMigrationFeeOption
Invalid migration fee option
Orca WhirlpoolsInvalidTickIndex
Provided tick index is either out of bounds or uninitializable
Raydium LaunchpadVestingRatioTooHigh
Vesting ratio too high
MoonshotInvalidCurrency
Invalid currency.
OKX DEX Aggregation Router V2InvalidDestinationTokenAccount
Invalid destination token account
BoopInvalidDampingTerm
Invalid damping term
Meteora AMMMismatchedLpMint
LP mint mismatched
BonkSwapMintMismatch
Mint mismatch
Drift V2UserHasNoPositionInMarket
User Has No Position In Market
Heaven DEXInvalidLiquidityProviderTokenLockVault
Invalid liquidity provider token lock vault
Jupiter DCANoOutATA
outAta not passed in
Jupiter Limit OrderInvalidKeeper
Magic Eden V2SOLWalletMustSign
If paying with sol, sol wallet must be signer
Metaplex Auction HouseSOLWalletMustSign
If paying with sol, sol wallet must be signer
Metaplex BubblegumDataHashMismatch
Provided metadata must result in provided data hash
Metaplex Candy MachineCandyMachineEmpty
Candy machine is empty!
Metaplex Fixed Price SaleStartDateIsInPast
StartDate cannot be in the past
Metaplex HydraHoldingAccountMustBeAnATA
A Mint holding account must be an ata for the mint owned by the config
Metaplex Token EntanglerEditionDoesntExist
Edition doesn't exist
Obric V2InsufficientActiveY
OpenBook V2InvalidInputOrderType
The order type is invalid. A taker order must be Market or ImmediateOrCancel
TensorWrongPool
this nft doesnt belong to this pool
TON Whales HoldersIncosistentReservedBalance

Same code, other formats

custom program error: 0x177a · {"Custom":6010} · Custom(6010) · Error Number: 6010

How to tell which program failed

  1. Open the failed transaction in an explorer (or the simulation result in your code) and read the program logs.
  2. Find the line Program <address> failed: custom program error: 0x…. If several programs failed with the same code, the first one listed is the deepest call, the one that raised it.
  3. Look the code up for that program. Error processing Instruction 2 is a zero-based index, so it points to the third instruction (often the first one after two Compute Budget instructions).

Decode your exact error

Free, no sign-up, nothing to connect. Works offline from a bundled list; we do not look anything up on-chain.

Swapping a token you do not know? A free Rugsight check shows mint and freeze authority, Token-2022 extensions, holder concentration and liquidity before you trade.

← 0x1779 · 0x177b → · All Solana error codes

Data: program error lists from published IDLs (solana-idls 1.2.1, MIT) and the System, SPL Token, Token-2022 and Associated Token Account source code, snapshot 2026-11-16. Programs can be upgraded and add or change errors; the failing program's current IDL is the final word.