DBC Launch Configuration

DBC configs are reusable launch templates. The curve defines price discovery; the surrounding config defines which token can launch, how fees behave, how migration works, and who can claim each economic bucket. Use this page as a checklist. For implementation limits and permissions, see DBC Accounts and Permissions.

Core Fields

Field	Program Behavior
Quote mint	SPL Token quote mints are permissionless. A Token 2022 quote mint is permissionless with metadata extensions, or with a `TransferFeeConfig` whose current fee is zero and whose transfer fee config authority is revoked. Anything else needs a token badge at remaining account index `0`. Token teams apply with the Token 2022 Whitelist Request Form. A non-zero fee or a live transfer fee config authority is accepted only by `create_config2`.
Activation type	Slot-based or timestamp-based. Fee schedules use the same activation type.
Token decimals	Must be from `6` to `9`.
Token type	SPL Token or Token 2022. Token 2022 launches must use DAMM v2 migration.
Token authority option	Controls whether creator, partner, or no one receives update authority, and whether creator or partner receives mint authority.
Transfer hook program	Optional Token 2022 transfer-hook path. Use a `ConfigWithTransferHook`; the program must be executable and cannot be DBC, SPL Token, Token 2022, or the default pubkey.
Collect fee mode	`QuoteToken` or `OutputToken` for bonding-curve trading.

Mint-authority token authority options are only valid for transfer-hook configs. Standard configs reject CreatorUpdateAndMintAuthority and PartnerUpdateAndMintAuthority.

A Meteora operator creates a quote-mint token badge after review. Apply with the Token 2022 Whitelist Request Form, then open a ticket in the Meteora Discord. Do not include the token launch date or time. See Quote mint token badges.

Supply

DBC supports dynamic supply and fixed supply.

Supply Model	Program Behavior
Dynamic supply	Initial base supply is calculated from the curve swap amount with a 25% buffer, migration base threshold, and locked-vesting amount.
Fixed supply	Config provides pre-migration and post-migration supply. The leftover receiver must be non-default, and pre-migration supply must cover the buffered requirement.

Fixed-supply cleanup is covered in DBC Surplus and Leftover.

Migration

Setting	Program Behavior
Migration target	DAMM v2 for new configs and new pools. DAMM v1 is deprecated and rejected for new configs and new pools. Existing DAMM v1 pools can still migrate.
Migration fee option	Fixed DAMM fee options or `Customizable` for custom DAMM v2 migrated-pool fee settings.
Migration fee percentage	Up to `99%`. If it is `0`, creator migration fee percentage must also be `0`.
DAMM v2 migrated pool fee	Must be `0.1%` to `10%` when custom migrated-pool fees are configured.
DAMM v2 compounding fee bps	Valid only when the migrated collect fee mode is compounding. `0` is allowed.
DAMM v2 market-cap scheduler params	Apply after migration; they do not affect the DBC bonding-curve fee.

For the migration flow and liquidity ownership, see DBC Migration and Liquidity.

Transfer Fees

Create new configs with create_config2. create_config does not take a base transfer fee, and it rejects a quote mint with a non-zero transfer fee or a live transfer fee config authority. transfer_fee_parameters is optional. Pass it to put a transfer fee on the base mint. The base mint must be Token 2022, and the fee is at most 10%. Omit it when the base mint has no transfer fee. 0 basis points still creates a TransferFeeConfig. A base transfer fee, or a quote mint with a non-zero transfer fee or a live transfer fee config authority, requires:

Fixed token supply, with pre_migration_token_supply equal to post_migration_token_supply.
No locked vesting.
migration_fee_option of Customizable.
Migrated collect fee mode Compounding.

A partner transfer-fee authority needs a non-default fee_claimer. The same rule applies to a Token 2022 partner token-update authority. Field values and the transfer-fee authority options are in DBC Token 2022 Support. Transfer-hook launches use DAMM v2. The hook is revoked from the base mint when the DBC curve completes, before migrated DAMM v2 liquidity is created.

Liquidity Distribution

The migrated liquidity distribution must add to 100% across:

Partner unlocked liquidity.
Partner permanent locked liquidity.
Partner vesting liquidity.
Creator unlocked liquidity.
Creator permanent locked liquidity.
Creator vesting liquidity.

At least 10% of migrated liquidity must still be locked after one day. DAMM v2 vesting lock duration is capped at two years.

Fees and Claim Addresses

Setting	Program Behavior
Pool creation fee	Optional. If non-zero, must be between `0.001 SOL` and `100 SOL`; split 10% protocol and 90% partner.
Creator trading fee percentage	Splits the non-protocol trading fee between creator and partner.
Fee claimer	Authorizes partner-side claims such as trading fees, pool creation fees, migration fees, and surplus.
Leftover receiver	Receives fixed-supply leftover after the migrated pool reaches `CreatedPool`.
First swap with minimum fee	Optional narrow path for an initialize-pool transaction that includes the first swap, targets that new pool, and has no referral account.

Bonding-curve fee modes are covered in DBC Fees. Transfer-hook launch behavior is covered in DBC Transfer Hook Pools.

User Guides

Core Products

Helper Products

Legacy Products

Core Fields

Supply

Migration

Transfer Fees

Liquidity Distribution

Fees and Claim Addresses

​Core Fields

​Supply

​Migration

​Transfer Fees

​Liquidity Distribution

​Fees and Claim Addresses

Core Fields

Supply

Migration

Transfer Fees

Liquidity Distribution

Fees and Claim Addresses