Errors & states
Wallet & signing errors
Common wallet and signing errors, what they mean and how to resolve them.
Connection
| No wallet found | No compatible wallet extension is installed, or it is locked. Install one such as Phantom or Solflare, unlock it and reload the page. |
|---|
| Wallet not connected | The action was started before a wallet was connected. 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 run the action again. Nothing was partially signed. |
|---|
Not enough SOL
| AccountNotFound / no record of a prior credit | Your wallet has never held SOL on the network you're on, so it can't pay the fee. Nothing was sent. Add SOL, or switch to Devnet and get free test SOL from the faucet. |
|---|
| Transfer: insufficient lamports (raw form: InstructionError … Custom: 1) | Your wallet has some SOL, but not enough to cover everything the action pays for: the Solstack fee, the network fee and rent for each new account it creates. Nothing was sent. The error card shows your balance on that network. Add SOL and try again. |
|---|
| Insufficient funds for fee | Every transaction needs a small SOL balance for the network fee, about 0.000005 SOL. Add SOL to the wallet. |
|---|
| Insufficient funds for rent | The action creates an account (a mint, a token account or a stake account) that needs a rent deposit, often 0.002–0.0025 SOL each. Add enough SOL to cover every account the action creates. |
|---|
| Insufficient token balance | The amount to send or burn is larger than your balance. Check the balance, including decimals. |
|---|
Signing & submission
| User rejected the request | You rejected the request in your wallet. Nothing was sent; run the action again to retry. |
|---|
| Transaction simulation failed | The pre-flight dry run failed. Expand the error: it usually contains a program error code (listed below) or a plain reason such as an empty recipient list. |
|---|
| Blockhash not found / expired | Too much time passed between building and approving. Run it again and approve within a minute. Multisender asks once more with a fresh transaction when your approval arrives too late. |
|---|
| Wallet window never opens | Click the wallet's icon in the browser toolbar; on a Mac in full-screen it can open on another desktop. If it still won't show, switch the extension off and on in chrome://extensions and unlock it. In Multisender, Stop waiting pauses the job with nothing sent, and you resume it from Distribute → Manage. |
|---|
| Unexpected error (Phantom) | Phantom shows this for any failure on its own network connection. Solstack asks the wallet only to sign and sends the transaction itself, so you normally see the RPC's actual error instead. If this still appears, reload the page and try again. |
|---|
| Transaction too large | The transaction exceeds Solana's size limit of 1,232 bytes. Split the work into smaller parts, for example fewer recipients per batch. |
|---|
| Already processed | This transaction was already submitted and has probably succeeded. Check it in the Transaction Inspector before running the action again. |
|---|
| Blockheight exceeded / dropped | The transaction expired during network congestion. Run it again, with a priority fee if the tool offers one. |
|---|
Program error codes
An on-chain failure ends with a code such as custom program error: 0x1. Common Token program codes:
| 0x1 | Insufficient funds: the account doesn't hold enough for the transfer or burn. A System program transfer returns the same code when SOL runs short. |
|---|
| 0x3 | Mint mismatch: the token account belongs to a different mint. |
|---|
| 0x4 | Owner mismatch: the signer doesn't own or control the account. |
|---|
| 0x5 | Fixed supply: the mint authority has been revoked, so no more tokens can be minted. |
|---|
| 0x6 | Already in use: the account the instruction tried to initialize already exists. |
|---|
| 0x11 | Account frozen: the freeze authority has frozen this token account, so it can't send, receive or burn. |
|---|
Authorities
| Not the mint authority | You can't mint more of this token. The mint authority belongs to another key or has been revoked (fixed supply). |
|---|
| Not the freeze authority | Only the freeze authority can freeze or thaw accounts, and the connected wallet doesn't hold 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't be used again. Revocation is permanent. |
|---|