Solana error codes › 0x177c

custom program error: 0x177c (6012)

0x177c is decimal 6012. Its meaning depends on the program that failed: LedgerTokenAccountDoesNotMatch in Jupiter Aggregator v6, InitialVirtualTokenReservesShouldBeGreaterThanInitialRealTokenReserves in Pump.fun Bonding Curve, UnsortedNotUniqueProtocolFeeRecipients in PumpSwap AMM and 26 more below.

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

0x177c by program

ProgramError
Jupiter Aggregator v6LedgerTokenAccountDoesNotMatch
Token account doesn't match the ledger
Pump.fun Bonding CurveInitialVirtualTokenReservesShouldBeGreaterThanInitialRealTokenReserves
initial_virtual_token_reserves should be greater than initial_real_token_reserves
PumpSwap AMMUnsortedNotUniqueProtocolFeeRecipients
Raydium AMM V3 (CLMM)InvalidTickArrayBoundary
Invalid tick array boundary
Meteora DLMMPairInsufficientLiquidity
Pair insufficient liquidity
Meteora CP AMM (DAMM V2)InvalidQuoteMint
Quote token must be SOL,USDC
Meteora Dynamic Bonding CurveNotEnoughLiquidity
Not enough liquidity
The name points to a balance check: an account holds less than the instruction needs.
Orca WhirlpoolsLiquidityZero
Liquidity amount must be greater than zero
Raydium LaunchpadVestingNotStarted
Vesting not started
The name points to a feature or pool state that currently blocks this action.
MoonshotThresholdNotHit
Market Cap threshold not hit, cannot migrate funds yet
OKX DEX Aggregation Router V2InvalidCommissionRate
Invalid commission rate
BoopInvalidProtocolFeeRecipient
Invalid protocol fee recipient
Meteora AMMInvalidVaultAccount
Invalid vault account
BonkSwapWrongFarm
Cannot add supply to wrong farm
Drift V2InvalidRepegRedundant
AMM repeg already configured with amt given
Heaven DEXInsufficientBalance
Insufficient balance
The name points to a balance check: an account holds less than the instruction needs.
Jupiter DCAInsufficientBalanceInProgram
Trying to withdraw more than available
The name points to a balance check: an account holds less than the instruction needs.
Jupiter Limit OrderProgramMismatch
Magic Eden V2NoPayerPresent
No payer present on this txn
Metaplex Auction HouseNoPayerPresent
No payer present on this txn
Metaplex BubblegumMetadataNameTooLong
Metaplex Candy MachineHiddenSettingsConfigsDoNotHaveConfigLines
Configs that are using hidden uris do not have config lines, they have a single hash representing hashed order
Metaplex Fixed Price SaleIncorrectOwner
Incorrect account owner
Metaplex HydraIncorrectOwner
Metaplex Token EntanglerInvalidMint
This token is not a valid mint for this entangled pair
Obric V2InvalidInputAmount
input amount must be greater than 0
OpenBook V2InvalidInputHeapSlots
Slot above heap limit
TensorPriceMismatch
specified price not within current price
TON Whales HoldersIncorrectNewLimits

Same code, other formats

custom program error: 0x177c · {"Custom":6012} · Custom(6012) · Error Number: 6012

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.

← 0x177b · 0x177d → · 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.