Solana error codes › 0x177d

custom program error: 0x177d (6013)

0x177d is decimal 6013. Its meaning depends on the program that failed: InvalidTokenLedger in Jupiter Aggregator v6, FeeBasisPointsGreaterThanMaximum in Pump.fun Bonding Curve, InvalidProtocolFeeRecipient in PumpSwap AMM and 26 more below.

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

0x177d by program

ProgramError
Jupiter Aggregator v6InvalidTokenLedger
Invalid token ledger
Pump.fun Bonding CurveFeeBasisPointsGreaterThanMaximum
fee_basis_points greater than maximum
PumpSwap AMMInvalidProtocolFeeRecipient
Raydium AMM V3 (CLMM)SqrtPriceLimitOverflow
Square root price limit overflow
The name points to a checked arithmetic failure inside the program, often from extreme amounts or an outdated client.
Meteora DLMMInvalidFeeOwner
Invalid fee owner
Meteora CP AMM (DAMM V2)InvalidFeeCurve
Invalid fee curve
Meteora Dynamic Bonding CurvePoolIsCompleted
Pool is completed
The name points to a feature or pool state that currently blocks this action.
Orca WhirlpoolsLiquidityTooHigh
Liquidity amount must be less than i64::MAX
Raydium LaunchpadNoVestingSchedule
No vesting schedule
MoonshotInvalidAuthority
Invalid Authority provided.
The name points to a permission check: the wrong signer or owner account was passed.
OKX DEX Aggregation Router V2InvalidTrimRate
Invalid trim rate
BoopInvalidSqrtPrice
Invalid sqrt price
Meteora AMMInvalidVaultLpAccount
Invalid vault lp account
BonkSwapRewardsExceedingSupply
Cannot withdraw rewards exceeding supply left
Drift V2InvalidRepegDirection
AMM repeg incorrect repeg direction
Heaven DEXExceededSlippage
Exceeded slippage
The name points to a slippage or minimum-output check: the price moved past the limit set in the transaction.
Jupiter DCAInvalidDepositAmount
Deposit should be more than 0
Jupiter Limit OrderUnknownInstruction
Magic Eden V2DerivedKeyInvalid
Derived key invalid
Metaplex Auction HouseDerivedKeyInvalid
Derived key invalid
Metaplex BubblegumMetadataSymbolTooLong
Metaplex Candy MachineCannotChangeNumberOfLines
Cannot change number of lines unless is a hidden config
Metaplex Fixed Price SaleMarketIsNotStarted
Market is not started
The name points to a feature or pool state that currently blocks this action.
Metaplex HydraWalletDoesNotOwnMembershipToken
Wallet Does not Own Membership Token
Metaplex Token EntanglerEntangledPairExists
This pair already exists as it's reverse
Obric V2NumOverflowing
The name points to a checked arithmetic failure inside the program, often from extreme amounts or an outdated client.
OpenBook V2InvalidOracleTypes
Cannot combine two oracles of different providers
TensorExistingNfts
cannot close pool with nfts in escrow -- withdraw all before closing
TON Whales HoldersIncorrectNewSeqno

Same code, other formats

custom program error: 0x177d · {"Custom":6013} · Custom(6013) · Error Number: 6013

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.

← 0x177c · 0x177e → · 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.