> ## 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.

# DBC Token 2022 Support

> Learn how DBC supports Token 2022 launches, metadata handling, transfer-hook pools, supported quote tokens, authority choices, supply models, and DAMM v2 migration behavior.

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.

<Note>
  DBC supports the standard Token 2022 metadata path and a dedicated Token 2022 transfer-hook path. Other base-token extensions should not be assumed compatible unless they are explicitly supported by the DBC launch flow.
</Note>

## SPL Token vs Token 2022

| Token Type                    | Product Behavior                                                                                                                                                              |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SPL Token                     | Standard Solana token launch path. Can migrate to DAMM v1 or DAMM v2 depending on configuration.                                                                              |
| Token 2022                    | Modern token launch path with Token 2022 metadata handling. Must use DAMM v2 migration in the DBC configuration flow.                                                         |
| Token 2022 with transfer hook | Dedicated launch path where the base mint has a transfer hook during bonding-curve trading. The hook is revoked when the curve completes so the token can migrate to DAMM v2. |

## 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.

| Item           | Behavior                                                                                                              |
| -------------- | --------------------------------------------------------------------------------------------------------------------- |
| Config account | `ConfigWithTransferHook`, which wraps the normal `PoolConfig` and stores the executable transfer-hook program.        |
| Pool account   | `TransferHookPool`, which wraps the same `PoolState` layout used by standard virtual pools.                           |
| Trading path   | Transfer-hook pools use `swap2_with_transfer_hook`, not the standard `swap` or `swap2` instructions.                  |
| Fee claims     | Partner and creator trading fee claims use transfer-hook-aware `claim_trading_fee2` and `claim_creator_trading_fee2`. |
| Completion     | DBC revokes the transfer-hook program id and transfer-hook authority from the base mint when the curve completes.     |

For details, see [DBC Transfer Hook Pools](/core-products/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 is revoked before DAMM v2 migration because the graduated pool does not support active transfer hooks.

<Warning>
  DAMM v1 migration is restricted to SPL Token launches. A Token 2022 base-token launch cannot use DAMM v1 migration in DBC config validation.
</Warning>

## Supported Quote Tokens

DBC can use SPL Token quote assets. It can also support Token 2022 quote assets when the quote mint uses only supported metadata-related extensions.

Supported Token 2022 quote mint extensions include:

* Metadata Pointer.
* Token Metadata.

If a Token 2022 quote mint uses other extensions, it may not be supported as a quote token for DBC.

This means Token 2022 quote mints with transfer fees or other behavioral extensions should not be assumed compatible with DBC.

<Note>
  Native Token 2022 mint behavior is not supported as a quote mint.
</Note>

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.

## 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.

| Supply Model   | Product Behavior                                                                                            |
| -------------- | ----------------------------------------------------------------------------------------------------------- |
| Dynamic supply | DBC mints the initial base supply needed by the launch flow.                                                |
| Fixed supply   | DBC uses configured pre-migration and post-migration supply values, with possible leftover after migration. |

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

<CardGroup cols={2}>
  <Card title="Modern Token Standard" icon="certificate" iconType="solid">
    Token 2022 support gives launch teams access to newer token infrastructure.
  </Card>

  <Card title="Metadata Included" icon="tags" iconType="solid">
    DBC initializes token metadata as part of the Token 2022 launch flow.
  </Card>

  <Card title="DAMM v2 Alignment" icon="arrow-right" iconType="solid">
    Token 2022 launches should be designed around DAMM v2 graduation from the start.
  </Card>

  <Card title="Quote Token Review" icon="magnifying-glass" iconType="solid">
    Token 2022 quote assets should be checked for supported extensions before launch.
  </Card>
</CardGroup>