Two Token Standards, One Decision
Solana has two SPL token standards in production. Most users only know the original (often just called "SPL"). The newer one, Token-2022, is broader, more powerful, and more complicated.
In 2026, every new Solana token launch involves an implicit choice between them. This post explains what Token-2022 actually adds, the compatibility trade-offs, and when to pick which.
[stats]
Classic SPL | 2020 | Battle-tested, universal support
Token-2022 | 2023 | Newer, extensions, partial support
Wallet support T22 | ~80% | Up from 30% in 2023
DEX support T22 | ~60% | Varies by extension used
[/stats]
What Token-2022 Adds
Token-2022 is a superset of classic SPL. Every classic operation still works. The new features are exposed as "extensions" that you opt into when creating the token. The big extensions:
Transfer Fees
Charge a percentage fee on every transfer of the token. The fee is collected by the mint and can be withdrawn by a designated authority. Common uses: protocol revenue, deflationary mechanics, treasury funding.
Example: a token with a 1% transfer fee earns 1% of every secondary trade and every wallet-to-wallet transfer.
Confidential Transfers
Hide the amount of a transfer using zero-knowledge proofs. The sender and recipient know the amount; outside observers see only that a transfer happened. Useful for privacy-sensitive applications.
This is not full anonymity (the wallets are still visible) but it does conceal the amount.
Transfer Hooks
Run custom logic on every transfer. The mint specifies a program that gets called whenever the token moves. Use cases: enforce KYC, check holding limits, integrate with a compliance system.
The hook program can reject the transfer if its conditions aren't met. Used heavily in the tokenized-equities space; the Securitize / Jupiter equity tokens use hooks to enforce KYC whitelisting.
Non-Transferable Tokens
Once minted to a wallet, the token can never move. Used for "soulbound" credentials, badges, identity tokens.
Interest-Bearing Tokens
The token's balance grows over time at a fixed rate. The underlying supply doesn't change; the displayed balance accumulates interest. Used for yield-bearing wrappers around base assets.
Metadata Pointer
The metadata can live in the mint account itself instead of a separate Metaplex account. Reduces storage cost and simplifies the architecture.
The Compatibility Trade-Off
Every extension you enable creates compatibility friction. Three places this matters:
Wallets. As of May 2026, ~80% of wallets fully support Token-2022. Phantom, Backpack, Solflare are all in. A few smaller wallets still have partial support; tokens with rarely-used extensions sometimes display incorrectly.
DEXes. Raydium, Jupiter, Orca all support Token-2022. Specific extensions (especially transfer hooks) may break automated routing. Jupiter handles most extensions but excludes some unusual configurations.
Bridges. Cross-chain bridges (Wormhole, etc.) lag on Token-2022 support. A token with confidential transfers cannot be bridged to most other chains because the destination doesn't understand the extension.
The general rule: the simpler the extension you enable, the better the compatibility. Transfer fees and metadata pointer are well supported. Transfer hooks and confidential transfers are still rough.
When to Use Token-2022
Three concrete use cases where Token-2022 is the right answer:
Tokens that need protocol revenue. Transfer fees are the cleanest way to capture fee revenue from secondary trading. If your token's economics depend on the protocol collecting fees, use Token-2022 with transfer fees.
Compliance-sensitive deployments. Tokenized equities, regulated stablecoins, KYC-gated assets. The transfer hook extension lets you enforce per-transfer compliance checks at the protocol level. Securitize's tokenized stocks are the canonical example.
Soulbound or non-transferable credentials. Identity tokens, on-chain achievements, certifications. Use the non-transferable extension.
When to Stick with Classic SPL
Three cases where classic SPL is the better call:
Memecoins and consumer tokens. If your goal is "trade everywhere, list on every DEX, easy to swap, easy to bridge", classic SPL is the path of least resistance. Token-2022 adds complexity without benefit for most memecoins.
Tokens you want to maximize compatibility for. Smaller wallets and older bridges sometimes break on Token-2022 in subtle ways. Classic SPL is the safe choice.
Tokens where you don't fully understand the extensions. Don't enable transfer hooks or confidential transfers because they sound cool. Every extension is a permanent property of the mint. Once set, it can't be removed without re-minting.
Decision Tree
A quick decision tree:
- Do you need transfer fees on secondary trades?
- Yes → Token-2022 with transfer-fee extension.
- No → continue.
- Do you need KYC enforcement at the token level?
- Yes → Token-2022 with transfer hooks.
- No → continue.
- Is the token non-transferable by design?
- Yes → Token-2022 with non-transferable extension.
- No → continue.
- Do you need maximum compatibility across wallets, DEXes, and bridges?
- Yes → Classic SPL.
- No → continue.
- Are you launching a memecoin or consumer-facing token?
- Yes → Classic SPL.
- No → Token-2022, default extension set off, add only what you need.
How to Deploy Each
The deployment workflow differs slightly.
Classic SPL via ManagerNest Token Creator:
- Connect wallet, enter name, symbol, supply, decimals.
- Sign one transaction. Done.
Total time: 60 seconds. Platform fee: 0.15 SOL.
Token-2022 via spl-token CLI:
`
spl-token create-token --program-id TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb \
--enable-metadata --transfer-fee 100 100
`
This creates a Token-2022 mint with a 1% transfer fee (the 100/100 is the rate in basis points). The full CLI documentation is on the SPL Token GitHub.
For most creators not familiar with the CLI, the best path today is to launch classic SPL and either accept the limitations or migrate to a custom Token-2022 deployment later if you need extensions.
What Gets Broken by Extensions
Specific examples of what each extension breaks:
Transfer fees: Some bots and automated DEX aggregators don't account for the fee in their swap calculations. Slippage can be wrong by the fee amount.
Transfer hooks: Jupiter routes that pass the token through multiple pools may fail if any intermediate pool doesn't support the hook.
Confidential transfers: Cross-chain bridges typically reject these tokens entirely.
Non-transferable: Obviously cannot be traded on any DEX. Used only for credentials.
Compatibility Matrix (May 2026)
Numbers are approximate and improving fast. By Q1 2027, expect Token-2022 compatibility to be ~95% across all surfaces.
Frequently Asked Questions
Can I convert a classic SPL token to Token-2022?
Not directly. You would have to mint a new Token-2022 token and run an airdrop to existing classic SPL holders, swapping their old tokens for new ones. Disruptive; only worth it if the extension you need is critical.
Are Token-2022 tokens more expensive to create?
Slightly. The mint account is larger (more extension storage), so the rent-exemption deposit is higher. Talking about 0.001-0.005 SOL difference. Negligible.
Does Jupiter charge more for swapping Token-2022 tokens?
No. Jupiter's fee structure is the same. The transfer-fee extension does mean the recipient receives slightly less than the swap quote (because the token mint takes a percentage), but Jupiter's own platform fee is unchanged.
Should I use Token-2022 for a memecoin?
Almost never. Memecoins benefit from maximum compatibility. Classic SPL is the safe, universal default.
Can I add an extension to a Token-2022 mint after creation?
No. Extensions are set at mint creation and cannot be added, removed, or changed afterward.