Solana error codes › 0x178f

custom program error: 0x178f (6031)

0x178f is decimal 6031. Its meaning depends on the program that failed: StartTimeInThePast in Pump.fun Bonding Curve, EndTimeInThePast in PumpSwap AMM, RewardTokenAlreadyInUse in Raydium AMM V3 (CLMM) and 17 more below.

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

0x178f by program

ProgramError
Pump.fun Bonding CurveStartTimeInThePast
PumpSwap AMMEndTimeInThePast
Raydium AMM V3 (CLMM)RewardTokenAlreadyInUse
The init reward token already in use
The name points to account state: an account was expected to exist (or not exist) already.
Meteora DLMMUnauthorizedAccess
Unauthorized access
The name points to a permission check: the wrong signer or owner account was passed.
Meteora CP AMM (DAMM V2)InvalidRewardVault
Invalid reward vault
Meteora Dynamic Bonding CurveInvalidVestingParameters
Invalid vesting parameters
Orca WhirlpoolsMulDivOverflow
Muldiv overflow
The name points to a checked arithmetic failure inside the program, often from extreme amounts or an outdated client.
OKX DEX Aggregation Router V2InvalidBundleInput
Invalid accounts and instruction length
BoopTokenGraduated
Token graduated
Meteora AMMInvalidTokenMultiplier
Invalid token multiplier
Drift V2ReferrerMustBeWritable
Heaven DEXCannotUpdateLpLock
Cannot update lp lock
Jupiter DCAUnknownInstruction
Unknown Instruction
Magic Eden V2InvalidAccountState
Invalid account state
Metaplex Auction HouseNoAuctioneerProgramSet
No Auctioneer program set.
Metaplex BubblegumCollectionMustBeAUniqueMasterEdition
Collection Must Be a Unique Master Edition v2
Metaplex Candy MachineMetadataAccountMustBeEmpty
The metadata account has data in it, and this must be empty to mint a new NFT
Metaplex Fixed Price SalePrimarySaleIsNotAllowed
Primary sale is not allowed
OpenBook V2InvalidPriceLots
Price lots should be greater than zero
TensorWrongFrozenStatus
wrong frozen status

Same code, other formats

custom program error: 0x178f · {"Custom":6031} · Custom(6031) · Error Number: 6031

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.

← 0x178e · 0x1790 → · 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.