Common Solana Token Minting Errors and How to Fix Them

Creating a token takes one or two signed transactions, yet a lot of first-time creators run into an error somewhere along the way. Most of those errors come from the same few causes. Here is what each one means and how to get past it.

"Insufficient funds for rent"

A new token needs several accounts: the mint, your own token account for the initial supply and, for a standard SPL token, a Metaplex metadata account. Each one needs its own rent-exemption deposit, roughly 0.0011 SOL, 0.0015 SOL and 0.0041 SOL. If your balance covers the network fee but not all three deposits, the simulation fails before your wallet even asks you to sign.

To fix it, keep enough SOL in the creating wallet for the three deposits, the network fee and whatever the tool charges. Solstack's creator charges a flat 0.1 SOL, so about 0.15 SOL in the wallet is plenty.

The logo upload fails or times out

Token images usually go to Arweave through a storage provider (Solstack uses Irys). A small transfer pays for the permanent storage first, then the file uploads. Two things go wrong. The funding transfer doesn't land, which is the same low-balance problem as above on a smaller scale. Or the upload gateway times out, which happens now and then when the network is busy.

A failed upload doesn't lose any SOL, so try again. If it keeps failing, look at the file size. Logos of several megabytes upload slowly and time out more often. Keep the logo under about 100 KB.

"Transaction simulation failed" with no clear reason

Wallets run a simulation before asking you to sign, so errors show up before anything is spent. A generic simulation failure usually has a specific reason further down in the error. Common ones are a broken metadata URI (invalid JSON, or a URL that can't be reached), a decimals value outside 0 to 9, or an initial supply too large for the mint at the decimals you chose. Open the full error text in your wallet. It normally names the instruction that failed and why.

"Account already in use"

You'll almost only see this with a custom or vanity mint address. It means an account already exists at that address, so the create-mint instruction can't set it up as new. If you didn't mean to reuse a keypair you generated earlier, the page was probably refreshed partway through a creation that had already started. Check whether the mint was created before you try again.

Blockhash expired, or "took too long to approve"

Every Solana transaction includes a recent blockhash, and an unsigned transaction expires roughly 60 to 90 seconds after it's built. A wallet password prompt or a slow hardware wallet confirmation can use up that window. This costs nothing. Run the creation again and approve as soon as the wallet prompt appears.

The revoke checkbox didn't take effect

Sometimes a creator ticks "revoke mint authority" or "revoke freeze authority", and the mint still shows a live authority afterwards. The usual cause is a form that never added the revoke instruction to the final transaction. Check the mint in Token Manager after creating it. You can revoke there on any mint you still control, whatever happened at creation.

Read the wallet's full error text

All of these errors appear as text in your wallet, before or after you sign. A tool's own summary message is there for convenience, and the wallet's text is the full error. Wallet and signing errors covers the wider set of wallet errors beyond token creation.

To try again: SPL Token Creator or Token-2022 Creator.