Custom program error

0x88

Appears in logs as custom program error: 0x8. Defined by 2 programs: SPL Token, System. Check which program failed in your logs.

Which one is yours?
The log line Program <id> failed: custom program error: 0x8 names the program that returned the code. Match that id to the program below. Anchor programs also print Error Code: … Error Number: … right above the failure.
SPL TokenTokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA

InvalidNumberOfRequiredSigners

“Invalid number of required signers”

The m (required signers) value given when creating a multisig is invalid.

Common causes

  • m is zero, or larger than the number of signers provided, or more than 11.

How to fix it

  • Use 1 ≤ m ≤ n ≤ 11 when initialising the multisig.
Source definition ↗All SPL Token errors →
System11111111111111111111111111111111

NonceUnexpectedBlockhashValue

“specified nonce does not match stored nonce”

The blockhash in your transaction does not match the value currently stored in the durable nonce account.

Common causes

  • The nonce was advanced (by you or another signer) after you built the transaction.
  • You used a regular recent blockhash instead of the nonce value while including an advanceNonce instruction.

How to fix it

  • Fetch the nonce account, read its current nonce value and use that as the transaction's recentBlockhash.
  • Make sure the AdvanceNonceAccount instruction is the first instruction in the transaction.
Source definition ↗All System errors →

Decode another error

Try:

Nearby codes

0x5FixedSupply0x6AlreadyInUse0x7InvalidNumberOfProvidedSigners0x9UninitializedState0xaNativeNotSupported0xbNonNativeHasBalance