Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.meteora.ag/llms.txt

Use this file to discover all available pages before exploring further.

DLMM supports SPL Token 2022 assets so teams can create pools for tokens with newer Solana token features. This helps token creators use richer token designs while still accessing Meteora’s concentrated liquidity, dynamic fees, pool function modes, and aggregator-ready pool infrastructure. Token 2022 support is split into two paths:

Permissionless Support

If your mint only uses supported safe extensions, you can create and use a DLMM pool without additional approval from Meteora.

Token Badge Support

If your mint uses more sensitive extensions, Meteora can review it and initialize a token badge so the token can be used in DLMM.

​
Permissionless Extensions

If your Token 2022 mint uses only the following supported extensions, it can be used permissionlessly in DLMM:
  • TransferFeeConfig
  • MetadataPointer
  • TokenMetadata
  • TransferHook, only when both the hook program and hook authority are revoked
DLMM also handles MemoTransfer as an account-level extension for token accounts.
MemoTransfer is not a mint extension. It is applied to individual token accounts rather than the token mint itself.

​
Token Badge Extensions

Some Token 2022 extensions can affect transfers, account states, authority behavior, or user expectations. If your token uses one of these extensions, you need a token badge before it can be used seamlessly in DLMM. Start by completing this Google Form with the extensions your token requires. After submitting the form, open a Discord ticket so the Meteora team can review your request. At the program level, a valid token badge allows a Token 2022 mint to pass DLMM mint validation even if it uses extensions that are not on the permissionless allowlist. This review path is intended for extensions that can affect transfers, account state, authorities, pausing, hooks, confidentiality, non-transferability, scaled UI amounts, or other behavior that can materially affect swaps, deposits, withdrawals, and integrations.
Token 2022 mints with a freeze authority require additional review. DLMM does not permissionlessly accept mints that can freeze accounts.
DLMM rejects the native Token 2022 mint to avoid fragmented SOL liquidity. Use the standard wrapped SOL mint for SOL liquidity.

​
What This Means For Pool Creators

Token 2022 support gives token teams more flexibility, but each extension changes the user and integration surface of a pool. Before launching a DLMM pool, confirm that wallets, aggregators, trading bots, and analytics tools used by your community can properly display and transfer your token.
Your mint may be eligible for permissionless DLMM support, as long as it only uses permissionless extensions and does not include unsupported authority controls.
Transfer hooks are supported permissionlessly only when both the hook program and hook authority are revoked. If the hook can still execute custom transfer logic, request token badge review.
Request a token badge before creating the pool. This gives Meteora a review point for extensions that can affect swaps, LP deposits, withdrawals, or downstream integrations.

​
Why Token 2022 Support Matters

More Launch Flexibility

Teams can launch assets with Token 2022 features while still using DLMM’s liquidity shapes, dynamic fees, and launch pool infrastructure.

Better Token UX

Metadata extensions help wallets and interfaces display richer token information.

Fee-Aware Tokens

Transfer-fee tokens can be supported, enabling assets with built-in transfer economics to access DLMM liquidity.

Controlled Risk

The token badge path lets Meteora review extensions that could materially affect pool behavior or user safety.