Token-2022 (the SPL Token Extensions program) is Solana's next-generation token standard — it keeps the core SPL model but adds opt-in extensions like transfer fees, confidential transfers, transfer hooks, metadata-on-mint, and non-transferable tokens. The catch for launchers: not every wallet, AMM, or aggregator supports every extension yet, so a Token-2022 mint with the wrong extension can be invisible or untradeable on surfaces that only speak classic SPL. The articles below explain what Token-2022 changes versus the original SPL Token Program, which extensions are safe to use for a tradeable memecoin today, and when the classic standard is still the right default.
Guides in this topic
SPL Token: The Program Behind Solana Tokens (2026)
What an SPL token actually is on-chain: mint accounts, ATAs, the 3 authorities, Token-2022 extensions — how Solana's token program works.
solanaspl-tokenspl-token-programtoken-2022associated-token-accountpillarSPL Token vs Token-2022: When to Pick Each (2026)
SPL Token vs Token-2022: differences, transfer fees, confidential transfers, when each makes sense, and which memecoins should pick (2026 guide).
solanaspl-tokentoken-2022explainer
How these Token 2022 guides connect
Every guide tagged token-2022 is written from the operator's seat — by people who have launched real Solana tokens and watched what actually happens after the transaction confirms. Rather than abstract documentation, each piece covers the on-chain mechanics, the irreversible decisions, and the verification steps you check on Solscan, DexScreener, and Phantom before and after you sign. Read them together and you get the full picture for this part of the launch, not an isolated how-to.
New to launching on Solana? Start with How to Create a Solana SPL Token for the end-to-end walkthrough, work through the Solana memecoin launch checklist, then come back to the token 2022 guides above for the detail on this specific step. When you're ready to ship, the Solana token creator handles the mint, metadata, and authority revocation in one no-code flow — no Rust, no CLI.