Token-2022 extensions and DEX compatibility

Token-2022 lets you bake behavior into a token: a transfer fee, interest, frozen-by-default accounts, and more. That power comes with a catch. A DEX has to understand the extensions you turned on, or it will refuse to host your liquidity. Some extensions trade fine almost everywhere. A few will block a pool outright.

This page maps extension against pool support so you can pick before you mint, and avoid launching a token that no venue will fund. If you are still deciding between programs, start with SPL vs Token-2022.

How venues read Token-2022

#how-venues-read-token-2022

A Token-2022 mint carries extra on-chain data that classic SPL never had. DEXes handle this in two ways. Newer pool programs inspect the extension set and decide whether they can safely host the mint. Older or stricter programs allow Token-2022 only when the extension set is plain enough that nothing changes their math.

The deciding factor is almost always the transfer fee. An AMM moves tokens in and out of its pool constantly. If a slice gets skimmed on every transfer, the pool’s accounting has to track it, and not every program does. A transfer-fee mint is the most common reason a pool refuses to open, so treat it as your first compatibility question.

J Tools works with Raydium (V4, CPMM, and CLMM), Meteora (DLMM), Orca (Whirlpool and Splash Pool), and PumpSwap. One route matters for Token-2022: Raydium’s Legacy AMM V4 accepts only classic SPL mints, so a Token-2022 token opens on Raydium through CPMM or CLMM, not V4. For what each venue is and which tool reaches it, see Supported DEXs and networks. Pump.fun is a bonding-curve launchpad, not a pool AMM, so token launches there follow their own path rather than the pool rules below.

Every route above is live for opening a pool today. Only the two Meteora DAMM routes (DAMM V1 and DAMM V2) still carry a coming-soon badge in the picker.

Extension versus pool support

#extension-versus-pool-support

Use this as a planning guide. Support shifts as venues update their programs, so the route selector inside Create LP is the live source of truth for what a given pool accepts today.

Extension	Pool-DEX outlook	What to watch
Metadata pointer	Broadly fine	Always on in Token-2022 Creator. It carries on-chain metadata and does not change pool math, so it rarely blocks anything.
Interest-bearing	Usually fine	The balance display accrues over time, but transfers move the raw amount, so most pools handle it.
Permanent delegate	Allowed, but a trust signal	A delegate can move or burn tokens from any account. Pools may host it, yet traders read it as risk. Disclose it.
Default-frozen	Risky for liquidity	New accounts start frozen, so a pool’s token account may need thawing before it can hold liquidity. Token-2022 Creator keeps your freeze authority when this is on so thawing stays possible, but it can still stall a launch.
Non-transferable	Cannot pool	A soulbound token cannot move between accounts, so no AMM can hold it. There is no liquidity path for this one.
Transfer fee	Depends entirely on the venue	The big one. Some pool programs support fee-bearing mints, others reject them. Check the route selector before you commit a launch plan.

Plan a launch that can get liquidity

#plan-a-launch-that-can-get-liquidity

Run these in order. The first answer that fits decides your path.

Do you need the token tradable on an AMM?

If yes, non-transferable is off the table. A soulbound token cannot enter any pool. Use it only for tokens that are meant to stay put, like a badge or a credential.
Are you charging a transfer fee?

If yes, this is your make-or-break choice. Open Create LP and check which venues accept a fee-bearing Token-2022 mint before you build your launch around one. If your target pool does not support it, either pick a venue that does or drop the fee.
Using default-frozen or a permanent delegate?

Both are allowed by some pools, but both affect how a launch behaves. Default-frozen accounts may need thawing before liquidity lands. A permanent delegate reads as a trust risk to buyers. Plan the disclosure and the operational steps before you mint.
Just want metadata and maybe interest?

You are in the safe zone. Metadata pointer and interest-bearing mints sit closest to plain Token-2022 and clear most pools.

The classic-SPL misread caveat

#the-classic-spl-misread-caveat

Even after a Token-2022 token is trading fine, a separate issue shows up in tooling. A Token-2022 LP mint can itself be Token-2022, and any scanner that only understands the classic SPL layout will read it wrong. The token is fine. The reader is using the old map.

Two symptoms come up most:

Pool value reads as $0.00. A naive scanner assumes the classic SPL layout and cannot parse the Token-2022 liquidity position, so a pool holding real funds shows as empty.
Labels show as Unknown. A tool that detects token type by the classic mint program alone mislabels a Token-2022 mint, for instance tagging it Unknown in a burn or pool view.

J Tools detects Token-2022 mints where it matters and reads them with the right layout, so the figures stay correct. If a Token-2022 position looks mis-valued in some third-party scanner, that is the scanner reading the old layout, not a fault in your token.

Fees

#fees

A Token-2022 mint costs 0.15 SOL base in Token-2022 Creator, plus 0.05 SOL for each authority you revoke at creation, and either 0.15 SOL for a generated custom mint address or 0.1 SOL for a vanity address, up to 0.45 SOL. On top of that you pay the Solana network fee and the mint rent, and Token-2022 rent scales with the extensions you enable. Opening a pool in Create LP is priced separately by route. Full table: Fee schedule.

#related