Errors & states

Wallet & signing errors

Everything that can stop a transaction between clicking a button and it landing on-chain.

Connection

No wallet found	No compatible wallet extension is installed or unlocked. Install one (Phantom, Solflare…), unlock it, reload.
Wallet not connected	You triggered an action before connecting. Click Select Wallet in the top bar first.
Connection request rejected	You dismissed the wallet's connect prompt. Click Select Wallet again and approve.
Wrong account active	Your wallet has multiple accounts and the active one isn't the one you meant. Switch accounts in the wallet, then reconnect.
Disconnected mid-task	The wallet locked or the extension reloaded. Reconnect and re-run — nothing partial was signed.

Insufficient funds for fee	You need a small SOL balance for the network fee (~0.000005 SOL) even on read-light actions. Top up.
Insufficient funds for rent	The action creates an account (a mint, a token account, a stake account) that needs a rent deposit — often 0.002–0.0025 SOL each. Add SOL to cover every account the action creates.
Insufficient token balance	You're trying to send or burn more of a token than you hold. Check the balance, allow for decimals.

User rejected the request	You pressed Reject. Harmless. Re-run to try again.
Transaction simulation failed	The pre-flight dry-run failed. Expand the error — it usually contains a program error code (below) or a plain reason like an empty recipient list.
Blockhash not found / expired	Too long between building and approving. Re-run; approve within a minute.
Transaction too large	Too many instructions in one transaction (limit is 1232 bytes). Split the work — e.g. fewer recipients per Multisender batch.
Already processed	This exact transaction was already submitted. It likely succeeded — check Transaction Inspector before re-running.
Blockheight exceeded / dropped	Network congestion. Re-run and add a priority fee if the tool offers one.

An on-chain failure ends with a code like custom program error: 0x1. Common ones from the Token program:

0x1	Insufficient funds — not enough tokens or SOL for what the instruction tried to do.
0x4	Owner does not match — you don't control the account you're acting on.
0x5	Not enough account keys / invalid account for this instruction.
0xB	Account already in use — trying to create something that exists (e.g. a mint address collision).
0x11	Account not associated / wrong mint — the token account is for a different mint.

Not the mint authority	You can't mint more of this token — the mint authority is another key, or it's been revoked (fixed supply).
Not the freeze authority	Only the freeze authority can freeze or thaw accounts. Yours isn't it.
Not the update authority	Metadata edits require holding the update authority for that mint.
Authority already revoked	The authority is set to none and can never be used again. This is permanent by design.