How to Create a Fixed Supply Token on Solana

Choose between the original Token Program and Token Extension Program before creating the mint. Both support basic minting, but extensions can change account sizing, wallet compatibility, and transfer behavior. A plain fixed supply asset usually needs no advanced extension. Define a human readable name, symbol, decimals, total atomic units, treasury ownership, and a truthful purpose statement before touching the CLI.

Install the Solana CLI and the token CLI documented by Solana, create a dedicated keypair, and fund it with devnet SOL from an official faucet. Keep the recovery material offline. Never paste a seed phrase into a web launcher. If multiple people govern the project, decide whether a multisignature should control the mint during setup, but remember that fixed supply ultimately requires mint authority to become null.

• Select devnet and confirm the RPC endpoint and signer address.
• Calculate supply in base units: displayed supply multiplied by ten to the decimals power.
• Write down whether freeze authority is needed and explain that choice publicly.
• Prepare original metadata and artwork that cannot be confused with another issuer.

Create the mint with the chosen token program and decimals, then create an associated token account owned by the intended treasury. Mint the exact quantity to that account. Read the mint and token account back from the network before changing any authority. A typo in decimals can make an intended million units display as a radically different amount, while minting to the wrong address may be irreversible.

After the supply and destination are correct, disable mint authority through the token CLI authority command. This transaction must name the mint and set the minting role to none. Do not rely on a promise that a key will remain unused. Onchain null authority is the independently verifiable condition. Freeze authority is separate: retaining it may allow accounts to be frozen, while revoking it removes that control permanently.

Token metadata is not the same as mint state. Follow the metadata mechanism supported by the selected program and ecosystem tooling, host durable public assets, and use accurate descriptions. Wallet presentation can lag or differ by provider, so metadata visibility is not proof of legitimacy or fixed supply.

Verify with an independent RPC or explorer. Inspect the mint owner to identify its program, confirm decimals and total supply, and confirm that mint authority is absent. Check the treasury token account balance and owner. Repeat the same reads from a second provider when the result will be published.

• Checklist: correct cluster, signer, mint program, decimals, quantity, recipient, and metadata URI.
• Checklist: mint authority is null and freeze authority matches the disclosed policy.
• Verification: save transaction signatures and direct explorer links for the mint and authority change.
• Verification: attempt no destructive test on mainnet; use read only commands after revocation.

A fixed supply does not create value, liquidity, security, or demand. Holders may still face concentrated ownership, inaccessible treasury keys, mutable offchain metadata, program risks, and poor market depth. Revoking mint authority does not revoke freeze authority, transfer fee controls, metadata update authority, or powers in unrelated programs.

Laws and platform rules depend on jurisdiction and use case. Obtain appropriate legal and security review before a public launch. Publish control addresses and material risks in plain language. Never copy branding, fabricate partnerships, hide privileged controls, or imply that fixed supply guarantees scarcity, returns, or safety.