Solana error codes › 0x3a

custom program error: 0x3a (58)

0x3a is decimal 58. Its meaning depends on the program that failed: NotEnoughProofContextStateAccounts in Token-2022, PrintingWouldBreachMaximumSupply in Metaplex Token Metadata.

Small numbers like this are used by native programs (System, SPL Token, Token-2022, Raydium AMM v4 and others), each with its own list, so the meaning depends on which program failed.

0x3a by program

ProgramError
Token-2022NotEnoughProofContextStateAccounts
Not enough proof context state accounts provided
The name points to a balance check: an account holds less than the instruction needs.
Metaplex Token MetadataPrintingWouldBreachMaximumSupply

Same code, other formats

custom program error: 0x3a · {"Custom":58} · Custom(58) · Error Number: 58

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.

← 0x39 · 0x3b → · 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.