Archived article · Original source date: 2024-08-17
This article is preserved from the previous Solana Bulls site as a historical archive. It reflects its original context; references to products, people, market conditions, eligibility, or rules may no longer be current.
Editorial note: This article is educational and is not financial, investment, legal, or tax advice. Products, protocols, yields, fees, liquidity, regulations, and tax treatment can change; verify current primary sources and evaluate the specific risks before acting.
Solana supports fungible tokens and many digital-asset patterns through two token programs: the original Token Program and Token-2022, also called Token Extensions.
Choose the token program and design
Start with the official token documentation. Decide whether the original Token Program is sufficient or whether a Token-2022 extension is required. Wallet and application compatibility varies by extension.
Define the token's purpose, decimals, supply policy, distribution, and whether mint or freeze authority will remain active. A token's existence does not establish legal ownership, value, liquidity, authenticity, or regulatory compliance.
Create and initialize the mint
Developers can use maintained Solana tooling or the official program examples to create a mint, create associated token accounts, and mint units. Test on Devnet before using mainnet and verify the program ID and cluster in every command or transaction.
The mint authority can create additional units while it remains active. The freeze authority can freeze supported token accounts. Revoking an authority is generally irreversible, so authority changes should be simulated and reviewed carefully.
Metadata and Token-2022 extensions
Metadata is commonly managed through Metaplex protocols or supported Token-2022 metadata extensions. Use the Metaplex documentation and Token Extensions documentation for the exact asset type and client support you need.
Extensions such as transfer fees, transfer hooks, permanent delegates, non-transferability, confidential transfers, or interest-bearing configuration materially change token behavior and risk. Many extensions must be selected when the mint is created.
Security and testing
- Use maintained SDKs and verify every program address.
- Keep mint, freeze, update, and upgrade authorities in deliberately secured signers or multisig arrangements.
- Test transfers, authority changes, metadata, integrations, and extension behavior before launch.
- Obtain an independent security review for custom programs or transfer-hook logic.
- Document supply, authorities, fees, upgrade paths, and user-facing restrictions clearly.
Distribution and legal responsibilities
Creating a mint is only a technical step. Marketing, sale, governance promises, revenue claims, consumer protection, sanctions, tax, and securities obligations depend on facts and jurisdiction. Obtain qualified legal advice before offering a token to the public.
For maintained code patterns, use the official Solana program examples rather than copying an old command, unaudited token launcher, or unverified social-media tutorial.