How to Create a Mintable SPL Token on Solana: No-Code, CLI & Mint Authority Guide

How to Create a Mintable SPL Token on Solana: No-Code, CLI & Mint Authority Guide

A mintable SPL token is a Solana token whose mint authority is still active. That means new supply can be minted later for rewards, vesting, ecosystem incentives, treasury operations, or staged token launches.

That flexibility is useful, but it also creates a trust problem: if the mint authority is controlled by the wrong wallet, poorly secured, or never revoked, holders may worry that supply can be inflated later. Charming little nightmare, because apparently token launches needed more ways to go wrong.

This guide explains how to create a mintable Solana token using three practical paths:

• No-code: fastest path with the DEXArea Solana Token Creator
• CLI: direct spl-token workflow for developers
• TypeScript: programmatic creation and minting with @solana/web3.js and @solana/spl-token

TL;DR

What is a mintable SPL token?

SPL tokens are Solana's standard token format. They are managed by Solana's Token Program or Token-2022 Program. A token's mint account stores the shared state for that token, including supply, decimals, mint authority, and optional freeze authority.

A token is called mintable when the mint authority is still present. That authority can sign a mint instruction later and increase total supply.

A token is called fixed supply when mint authority has been revoked. After that, new supply cannot be minted for that mint.

Mintable vs fixed-supply token

Option 1: Create a mintable SPL token with no code

The fastest way to create a mintable token is to use a wallet-based token creator. This is the better path if your goal is to launch a token, not spend your evening arguing with terminal flags like it owes you money.

Basic no-code flow

1. Open the Solana Token Creator.
2. Connect your Solana wallet.
3. Choose the network: Devnet for testing or Mainnet for production.
4. Enter token name, symbol, decimals, image, and metadata.
5. Set the initial supply.
6. Decide whether the token should remain mintable.
7. Create the token and confirm the transaction in your wallet.
8. Verify the mint address in a Solana explorer.

When to keep mint authority active

Keeping mint authority active can make sense if your project needs:

• Future emissions
• Staking or reward distribution
• Vesting unlocks
• Treasury-controlled supply expansion
• Programmatic minting through a smart contract or PDA

When to revoke mint authority

You should consider revoking mint authority when:

• The full supply is already minted
• You want a fixed-supply token
• You want to reduce holder concerns about future inflation
• Your launch page or community promises no more minting

Option 2: Create a mintable SPL token with Solana CLI

The CLI path is useful when you want direct control and a repeatable developer workflow.

1. Set your CLI to Devnet

solana config set --url https://api.devnet.solana.com
solana address
solana balance

If you need Devnet SOL:

solana airdrop 2

2. Create the token mint

Create a standard SPL token mint with 9 decimals:

spl-token create-token --decimals 9

The CLI will print a mint address. Save it.

Creating token <MINT_ADDRESS>
Signature: <TRANSACTION_SIGNATURE>

That mint address is the token's unique on-chain identifier.

3. Create your token account / ATA

A mint account is not where wallet balances live. You also need a token account, usually an Associated Token Account (ATA), to hold your balance.

spl-token create-account <MINT_ADDRESS>

4. Mint the initial supply

spl-token mint <MINT_ADDRESS> 100

Then verify:

spl-token balance <MINT_ADDRESS>
spl-token supply <MINT_ADDRESS>

5. View mint details

spl-token account-info <MINT_ADDRESS>

Check:

• Decimals
• Supply
• Mint authority
• Freeze authority
• Token program

Option 3: Create and mint a token with TypeScript

Use TypeScript if your app needs to create token mints programmatically or prepare transactions for wallet signing.

Install dependencies:

npm install @solana/web3.js @solana/spl-token

TypeScript example

import {
  Connection,
  Keypair,
  clusterApiUrl,
  LAMPORTS_PER_SOL,
} from "@solana/web3.js";
import {
  createMint,
  getOrCreateAssociatedTokenAccount,
  mintTo,
  TOKEN_PROGRAM_ID,
} from "@solana/spl-token";

async function main() {
  const connection = new Connection(clusterApiUrl("devnet"), "confirmed");

  const payer = Keypair.generate();
  const airdropSignature = await connection.requestAirdrop(
    payer.publicKey,
    2 * LAMPORTS_PER_SOL
  );
  await connection.confirmTransaction(airdropSignature, "confirmed");

  const decimals = 9;
  const mintAuthority = payer;
  const freezeAuthority = payer.publicKey;

  const mint = await createMint(
    connection,
    payer,
    mintAuthority.publicKey,
    freezeAuthority,
    decimals,
    undefined,
    undefined,
    TOKEN_PROGRAM_ID
  );

  const ata = await getOrCreateAssociatedTokenAccount(
    connection,
    payer,
    mint,
    payer.publicKey
  );

  const uiAmount = 100n;
  const rawAmount = uiAmount * 10n ** BigInt(decimals);

  await mintTo(
    connection,
    payer,
    mint,
    ata.address,
    mintAuthority,
    rawAmount
  );

  const supply = await connection.getTokenSupply(mint);

  console.log("Mint:", mint.toBase58());
  console.log("ATA:", ata.address.toBase58());
  console.log("Supply:", supply.value.uiAmountString);
}

main().catch((error) => {
  console.error(error);
  process.exit(1);
});

For production apps, do not use a randomly generated payer like this. Use wallet signing, secure key management, multisig, or a program-controlled authority depending on your architecture.

Token Program vs Token-2022

Solana has the original Token Program and the newer Token-2022 Program. Most basic SPL tokens use the original Token Program. Token-2022 supports extensions such as transfer fees, metadata pointer patterns, confidential transfer features, and other advanced options.

If you are creating a simple token for broad compatibility, standard SPL is usually the safer default. If you need transfer fees or specific Token-2022 extensions, use Token-2022 intentionally and test compatibility with wallets, explorers, and dApps before launch.

You can create Token-2022 mints with the Token-2022 program ID:

spl-token --program-id TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb create-token --decimals 9

Metadata: name, symbol, image, and URI

Wallets and explorers need metadata to display your token properly. Metadata usually includes:

• Token name
• Symbol
• Description
• Image URL
• Metadata JSON URI

For standard SPL tokens, metadata is commonly handled with the Metaplex Token Metadata Program. For Token-2022 mints, metadata can also use extension-based patterns.

Mint authority: keep, transfer, or revoke?

After creating a mintable SPL token, you need a plan for the mint authority.

Keep mint authority

Keep it only if future minting is part of your token design. For example:

• Reward programs
• Staking emissions
• Vesting schedules
• Treasury releases
• DAO-controlled supply expansion

Transfer mint authority

Transferring mint authority can be safer than keeping it on a normal wallet. You may transfer authority to:

• A multisig
• A governance-controlled wallet
• A program-derived address (PDA)
• A more secure cold wallet

Revoke mint authority

Revoking mint authority permanently disables future minting for that token mint. This is common when projects want to prove the supply is fixed.

CLI example:

spl-token authorize <MINT_ADDRESS> mint --disable

Common mistakes when creating mintable Solana tokens

1. Choosing the wrong decimals

Most Solana tokens use 6 or 9 decimals. Once the mint is created, decimals cannot realistically be changed. If you choose the wrong value, you usually need to create a new mint.

2. Minting to the wrong token account

A wallet address and a token account address are not the same thing. Each wallet usually needs an ATA for each token mint.

3. Forgetting metadata

A token without metadata may look broken or suspicious in wallets and explorers.

4. Keeping mint authority on a hot wallet

If your mint authority wallet is compromised, an attacker may mint new supply. That is not exactly the branding moment most projects dream of.

5. Revoking too early

If you revoke mint authority before minting the intended final supply, the token is permanently capped at the current supply.

6. Testing directly on Mainnet

Always test the full flow on Devnet first: create token, mint supply, update metadata, transfer tokens, revoke authority, and verify on explorer.

Recommended launch checklist

For a stronger launch security flow, combine:

• Token Creator
• Mint Tokens
• Update Metadata
• Revoke Mint Authority
• Revoke Freeze Authority
• Make Token Immutable

FAQ

Final thoughts

Creating a mintable SPL token on Solana is straightforward. Managing it responsibly is the real work.

A clean launch flow looks like this:

1. Create the token.
2. Add metadata.
3. Mint the intended supply.
4. Verify the mint and token accounts.
5. Transfer or distribute tokens if needed.
6. Revoke or secure authority based on your tokenomics.

References

• Solana Docs: Create a Token Mint
• Solana Docs: Mint Tokens
• Solana Docs: Set Authority
• Solana Docs: Token Extensions
• SPL Token CLI Guide