SPL Tokens: What Actually Happens When You Create a Fungible Token on Solana

Most guides on creating SPL tokens walk you through CLI commands and call it done. What they skip: the account model underneath. If you don't understand what a mint account actually is, how it relates to token accounts, and why metadata lives in a separate program entirely, you'll struggle the moment something breaks — a frozen supply, missing token info on explorers, or wallets showing raw addresses instead of symbols.

This article closes that gap. You already know what a token is. Here's how Solana actually stores and manages one.

On Ethereum, each ERC-20 token is its own smart contract with its own bytecode. Solana doesn't work that way. There's a single deployed program — the SPL Token program (address: TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA) — and every fungible token on Solana uses it. You don't deploy code; you create data accounts that the SPL Token program owns and operates on.

This means the token logic is shared. What differentiates your token from every other SPL token is the data stored in its mint account: the supply, decimal precision, and the public keys that have authority over it. The SPL Token program reads and writes to these accounts according to fixed rules — mint, transfer, burn, freeze.

This is an important mental model shift. When you "create a token" on Solana, you're allocating a new account on-chain, populating it with initial parameters, and telling the SPL Token program it exists. No compilation, no deployment, no gas-heavy contract creation.

⚠ Common mistake: Assuming each SPL token has its own program ID. It doesn't. Every SPL token shares the same program. If someone asks you for your token's "contract address," they mean your mint account address.

Two account types matter here, and confusing them causes real problems.

A mint account is the global record for a token. It stores: total supply, number of decimals (0–9, set at creation, immutable), the mint authority (who can create new tokens), and the freeze authority (who can freeze individual token accounts). There's exactly one mint account per token.

A token account (sometimes called an Associated Token Account or ATA) holds a specific wallet's balance of a specific token. If your wallet holds USDC and BONK, you have two separate token accounts — one for each mint. Each token account stores: the mint it's associated with, the owner's wallet address, and the balance. These accounts are owned by the SPL Token program, not by your wallet — your wallet is just listed as the authority.

The standard explanation says "your wallet holds your tokens." What's actually happening: your wallet's public key is the designated owner of token accounts scattered across the chain. The wallet itself holds only SOL for rent and transaction fees.

When you send SPL tokens, the SPL Token program decrements the balance in your token account and increments the balance in the recipient's token account for that same mint. If the recipient doesn't have a token account for that mint yet, one must be created first — which costs rent.

⚠ Common mistake: Sending tokens to a wallet that has no ATA for that mint without including the account creation instruction. The transaction will fail. Most wallets handle this automatically, but raw transactions and scripts often don't.

Here's what happens step by step when you create a new fungible SPL token using the spl-token CLI or equivalent SDK calls. Order matters — misordering these steps produces broken or unusable tokens.

Step 1: Generate a keypair for the mint account. This keypair's public key becomes your token's permanent address. You can let the CLI generate one randomly or use a vanity address. Once created, this cannot change.

Step 2: Create the mint account on-chain. This allocates 82 bytes of storage on Solana and pays rent (approximately 0.00144768 SOL for a mint account as of current rent rates). You set the decimal count here — for a standard fungible token, 6 or 9 decimals are typical (USDC uses 6, many memecoins use 6 or 9). This is permanent. You cannot change decimals after creation.

Step 3: Set mint authority and freeze authority. The wallet that creates the mint is the default authority for both. Mint authority controls supply expansion. Freeze authority can lock individual token accounts. You can later transfer these authorities to another address, or revoke them entirely by setting them to null.

Step 4: Create a token account for yourself. Before you can mint tokens to your own wallet, your wallet needs an ATA for this new mint. The spl-token CLI usually handles this implicitly when you run mint-to.

Step 5: Mint tokens. The mint authority signs a transaction telling the SPL Token program to increase the supply and credit tokens to a specified token account. You specify the amount in the smallest unit — if your token has 6 decimals, minting 1,000,000 units gives you 1.000000 tokens as displayed in wallets.

⚠ Common mistake: Setting decimals to 0 for a token you intend to be fungible and divisible. Decimals = 0 means every token is a whole unit and cannot be split. This is fine for tickets or points, but terrible for a currency-like token.

Solana now has a second token program: Token Extensions (also called Token-2022, program ID: TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb). It's a superset of the original SPL Token program with built-in extensions.

Key extensions relevant to fungible tokens: transfer fees (protocol-level fee on every transfer, no wrapper contract needed), confidential transfers (encrypted balances using zero-knowledge proofs), permanent delegate (an address that can transfer or burn tokens from any account — useful for regulated assets), and non-transferable (soulbound tokens).

Token-2022 tokens and original SPL tokens are not interchangeable at the program level. A token account created under the original program cannot hold Token-2022 tokens and vice versa. DEXs and wallets must explicitly support Token-2022 — most major ones (Jupiter, Raydium, Phantom) now do, but integration depth varies.

If you're creating a new token today and need any of these extensions, use Token-2022. If you want maximum compatibility with every protocol and tool, the original SPL Token program is still the safer default.

⚠ Common mistake: Assuming Token-2022 is a mandatory upgrade. It's not. The original SPL Token program remains active, supported, and isn't deprecated. Most existing tokens (USDC, JUP, BONK) still use the original program.

The SPL Token program stores zero metadata. No name, no symbol, no image. That's handled by a separate on-chain program: the Metaplex Token Metadata program (address: metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s).

To make your token display a name, ticker, and logo in wallets and explorers, you create a metadata account that's a PDA (Program Derived Address) seeded from your mint address. This metadata account stores the token name, symbol, and a URI pointing to a JSON file (usually hosted on Arweave or IPFS) that contains the image URL and description.

Without this metadata account, wallets display your mint address as the token name. Explorers show "Unknown Token." This isn't a bug — it's the architecture. Metadata is opt-in and separate from the token itself.

For Token-2022 tokens, there's an alternative: the TokenMetadata extension baked into Token-2022 itself, which stores name, symbol, and URI directly in the mint account without needing Metaplex. This is simpler but has less ecosystem support for rich metadata features.

⚠ Common mistake: Uploading metadata JSON to a centralized server. If the server goes down, your token's name and image disappear from wallets. Use Arweave or IPFS for persistence.

After creation, the two critical authorities on your mint account are mint authority and freeze authority. How you handle these defines your token's trust properties.

Revoking mint authority means no one — including you — can ever mint new tokens. The supply becomes permanently fixed. To do this, you set the mint authority to None using the spl-token authorize command (or the equivalent SetAuthority instruction). This is a one-way operation. You can verify it on-chain: if the mint account's mint_authority field is empty, supply is fixed forever.

Revoking freeze authority ensures no one can freeze individual token accounts. For DeFi tokens, community expectation is that both authorities are revoked after initial distribution. Tokens with active mint or freeze authorities carry centralization risk — protocols like Jupiter display warnings for such tokens.

You can verify authority status for any token on Solana Explorer (explorer.solana.com) or Solscan (solscan.io) — look up the mint address and check the "Mint Authority" and "Freeze Authority" fields. A null/empty value means revoked.

⚠ Common mistake: Revoking mint authority before you've minted your full intended supply. This cannot be undone. Double-check your total supply before revoking.

• Solana Explorer (explorer.solana.com): Paste any mint address to see supply, decimals, authorities, and all token accounts holding that token.
• Solscan (solscan.io): More detailed token analytics — holder distribution, transfer history, and metadata resolution.
• spl-token display command in the CLI: Returns the full on-chain state of a mint account — supply, decimals, authorities, and whether it's Token-2022 or original SPL.
• Jupiter Token Verification (station.jup.ag): Check whether a token is verified on Jupiter's strict list, which requires metadata, liquidity, and revoked authorities.
• Metaplex Token Metadata explorer: Any tool that resolves the PDA from a mint address can show you the on-chain metadata and URI.

• Create a token on devnet first. Use the Solana CLI with the --url devnet flag. Devnet SOL is free from faucets. Make every mistake here, not on mainnet.
• Study Token-2022 extensions in depth. If you need transfer fees or confidential transfers, read the SPL Token-2022 documentation at spl.solana.com — each extension has specific initialization requirements that must be set at mint creation time.
• Learn how liquidity pools use mint accounts. When you add liquidity on Raydium or Orca, the pool creates its own token accounts for both mints. Understanding ATAs makes LP mechanics click.
• Explore the Metaplex SDK for metadata automation. If you're creating tokens programmatically, the Metaplex JavaScript SDK handles PDA derivation, metadata account creation, and Arweave uploads in a single workflow.