DBC Token 2022 Support

DBC supports both SPL Token and Token 2022 base token launches. Token 2022 support helps launch teams use newer Solana token capabilities while still accessing DBC’s bonding curve, launch fee controls, and DAMM migration flow.

​

SPL Token vs Token 2022

​

Token 2022 Base Tokens

When DBC launches a Token 2022 base token, the launch flow initializes the mint with Token 2022 metadata support. DBC handles:

• Creating the Token 2022 mint.
• Setting token decimals from the config.
• Initializing metadata pointer behavior.
• Initializing token metadata with name, symbol, and URI.
• Initializing metadata with the creator, then setting metadata pointer and token metadata update authority according to the configured authority option.
• Minting the initial base supply into the pool vault.
• Setting mint authority according to the configured authority option.

This lets creators launch a Token 2022 token through the same product flow as a standard DBC launch.

​

Transfer Hook Base Tokens

DBC supports Token 2022 base mints with transfer hooks through separate config, pool, swap, and fee-claim paths. For details, see DBC Transfer Hook Pools.

​

Migration Target

Token 2022 launches must use DAMM v2 migration in the DBC configuration flow. DAMM v2 is the modern migration target for Token 2022 support, advanced collect fee modes, dynamic fees, and vesting behavior. For transfer-hook launches, the hook is active during bonding-curve trading only. The base mint’s transfer hook program ID and authority are revoked before DAMM v2 migration so the graduated mint can use DAMM v2 without relying on transfer-hook remaining accounts.

​

Supported Quote Tokens

DBC can use SPL Token quote assets permissionlessly. Token 2022 quote assets are permissionless only when the mint uses metadata-related extensions and has a zero transfer fee. Permissionless Token 2022 quote mint extensions:

• Metadata Pointer
• Token Metadata

SPL Token quote mints are always accepted. A Token 2022 quote mint with no extensions is also accepted permissionlessly, as long as it is not the Token 2022 native mint. DBC records whether the quote mint belongs to the SPL Token program or Token 2022 program. Token transfers use transfer_checked, so integrations should provide the token program that matches each mint.

​

Quote Mint Token Badges

Some Token 2022 quote mints use extensions outside the permissionless allowlist, such as Permanent Delegate. Those quote mints need a token badge before they can be used in a new DBC config or virtual pool. This is the path used for Stock Tokens and other Token 2022 quote assets that need extra extensions. A DBC token badge is scoped to DBC. It does not automatically satisfy DAMM v2 mint validation. DAMM v2 configs used by DBC migration include the CreatePoolWithoutMintValidation permission so a badged quote mint can still graduate. A badge does not allow a non-zero transfer fee. Current and any scheduled transfer_fee_basis_points must be 0. Expired historical older_transfer_fee values are ignored. The program enforces that zero-fee rule when a token badge is created, when a config or pool is created, and on every instruction that transfers quote tokens. If a quote mint later has a non-zero transfer fee, quote-side swaps, surplus withdrawals, and quote fee claims fail until the fee returns to zero. Base-only fee claims can still succeed. For config and pool creation, pass the token badge as remaining account index 0 when the quote mint is not permissionless-supported. The SDK adds this account when you supply tokenBadge.

​

Token Authority Choices

Token 2022 launches can use the same product-level authority choices as other DBC launches. Launch teams can configure whether authority is:

• Held by the creator.
• Held by the partner.
• Made immutable.
• Extended to include mint authority options for advanced configurations.

Authority choices should match the launch’s trust model. Immutable settings may be easier for communities to reason about, while retained authority may be useful for managed launchpad flows. The mint-authority options, CreatorUpdateAndMintAuthority and PartnerUpdateAndMintAuthority, are only allowed for transfer-hook configs. Standard SPL Token and standard Token 2022 pool initialization rejects those options and revokes mint authority at launch.

​

Fixed and Dynamic Supply

Token 2022 launches can be used with DBC’s supply models. For fixed-supply Token 2022 launches, leftover handling works the same product way: unused base tokens can be withdrawn to the configured leftover receiver after migration.

​

Product Considerations