Skip to main content
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

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

Supply

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

Migration

For the migration flow and liquidity ownership, see DBC Migration and Liquidity. 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

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