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.

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.
Token 2022 support in DBC does not allow you to utilize any token extensions.

​
SPL Token vs Token 2022

Token TypeProduct Behavior
SPL TokenStandard Solana token launch path. Can migrate to DAMM v1 or DAMM v2 depending on configuration.
Token 2022Modern token launch path with Token 2022 metadata handling. Must use DAMM v2 migration in the DBC configuration flow.

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

​
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.
DAMM v1 migration is restricted to SPL Token launches. A Token 2022 base-token launch cannot use DAMM v1 migration in DBC config validation.

​
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.
Native Token 2022 mint behavior is not supported as a quote 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.

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

​
Fixed and Dynamic Supply

Token 2022 launches can be used with DBC’s supply models.
Supply ModelProduct Behavior
Dynamic supplyDBC mints the initial base supply needed by the launch flow.
Fixed supplyDBC 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

Modern Token Standard

Token 2022 support gives launch teams access to newer token infrastructure.

Metadata Included

DBC initializes token metadata as part of the Token 2022 launch flow.

DAMM v2 Alignment

Token 2022 launches should be designed around DAMM v2 graduation from the start.

Quote Token Review

Token 2022 quote assets should be checked for supported extensions before launch.