Common Solana Token Minting Errors and How to Fix Them

Creating a token is usually one or two signed transactions, but a surprising number of first-time creators hit an error somewhere in the process. Almost all of them fall into a small number of categories — here's what each actually means and how to resolve it.

"Insufficient funds for rent"

Creating a token isn't one account — it's several: the mint account, your own token account holding the initial supply, and (for standard SPL tokens) a separate Metaplex metadata account. Each needs its own rent-exemption deposit, roughly 0.0014 SOL, 0.002 SOL, and 0.0056 SOL respectively. If your wallet's balance covers the network fee but not all three deposits combined, the transaction simulation fails before you even see a wallet prompt. Fix: keep enough SOL in the creating wallet to cover mint + token account + metadata rent, the network fee, and whatever the tool you're using charges on top — Solstack's creator adds a flat 0.1 SOL, so about 0.15 SOL is a comfortable balance there.

Logo upload fails or times out

Token images typically go to Arweave via a storage provider (Solstack uses Irys), which involves a small funding transfer to pay for permanent storage before the actual upload. Two common failure points: the funding transfer doesn't land (same insufficient-SOL issue as above, just for a smaller amount), or the upload gateway itself times out — Arweave uploads occasionally hiccup on busy networks. In both cases, no SOL is lost on a failed upload; simply retry. If it keeps failing, check the image size — very large files (multi-megabyte logos) are slower to upload and more likely to time out; keep logos under roughly 100 KB.

"Transaction simulation failed" with no clear reason

Wallets run a dry-run simulation before asking you to sign, specifically to catch errors before anything is spent. A generic simulation failure almost always has a more specific reason buried in the expanded error — common ones include a malformed metadata URI (broken JSON, or a URL the simulation can't resolve), a decimals value outside the valid 0–9 range, or an initial supply that overflows the mint's numeric type at the chosen decimal count. Expand the full error text in your wallet rather than just reading the headline — it typically names the exact instruction and reason.

"Account already in use"

This shows up almost exclusively when using a custom/vanity mint address rather than letting the tool generate one randomly — it means an account already exists at that exact address, so the create-mint instruction can't initialize it fresh. If you're not intentionally reusing a pre-generated keypair, this usually means a page was refreshed mid-flow and partially completed; check whether a mint was already created before retrying from scratch.

Blockhash expired / "took too long to approve"

Solana transactions reference a recent blockhash and expire roughly 60–90 seconds after being built if unsigned. If you get pulled away mid-approval — a wallet password prompt, a hardware wallet confirmation that takes a minute — the transaction can go stale before you sign it. This costs nothing; the fix is simply to re-run the creation flow and approve promptly once the wallet prompt appears.

Revoke-on-creation checkbox doesn't seem to apply

If you checked "revoke mint authority" or "revoke freeze authority" during creation but the mint still shows a live authority afterward, the most common cause is checking the box in a form that didn't actually include the revoke instruction in the final transaction — worth re-verifying in Token Manager after creation, since revoking there works on any mint you still control regardless of what happened at creation time.

When in doubt, read the wallet's error text fully

Every one of these surfaces as text in your wallet before or after you sign — the summary message from a tool's UI is a convenience, not the authoritative error. For the full breakdown of wallet and signing error categories beyond token creation specifically, see Wallet & signing errors.

Ready to try again: SPL Token Creator or Token-2022 Creator.