Skip to main content
DBC migration is the handoff from launch trading to long-term Meteora liquidity. During the bonding curve phase, traders buy and sell against a DBC virtual pool. When the quote reserve reaches the configured migration threshold, normal curve trading stops and the pool becomes eligible to create a DAMM pool.
For Token 2022 transfer-hook pools, curve completion also revokes the base mint’s transfer-hook program id and transfer-hook authority. DBC does this before DAMM v2 migration because migrated DAMM liquidity does not support an active transfer hook on the base mint.

​
Migration Progress

The program tracks migration as a sequence of states. Some launches move from curve completion directly into the migration-ready state. Others need the locker step first, especially when base-token locked vesting is configured.

​
Migration Targets

DBC supports two migration targets. DAMM v2 is the more flexible path for modern launches, especially Token 2022 launches and teams that need detailed post-migration liquidity controls. Transfer-hook launches also use DAMM v2. The hook is active only during the DBC bonding-curve phase and is revoked when the curve completes.
DAMM v1 migration is restricted to SPL Token base mints and SPL Token quote mints. Token 2022 launches must migrate to DAMM v2.

​
What Migrates

At migration, DBC uses:
  • The configured quote threshold from the bonding phase.
  • The base token amount allocated for the migrated pool.
  • The migration price discovered by the curve.
  • The configured partner and creator liquidity distribution.
The goal is to start the DAMM pool around the price discovered during the launch, rather than forcing teams to choose a separate post-launch price manually.

​
Liquidity Ownership

DBC can split migrated liquidity between partner and creator buckets. Each bucket can include: The full distribution across partner unlocked liquidity, partner permanent locked liquidity, partner vesting liquidity, creator unlocked liquidity, creator permanent locked liquidity, and creator vesting liquidity must add up to 100%.
DBC requires at least 10% of liquidity to remain locked at day 1 after migration. Vesting lock durations are capped at 2 years.

​
DAMM v1 Liquidity

For DAMM v1 migration, liquidity is represented through LP tokens. After the DAMM v1 pool is created, partner and creator LP-token claims can become available according to the configured distribution. If LP tokens need to be locked, the lock step happens after the migrated pool exists. This path is simpler, but it is also less configurable than DAMM v2.

​
DAMM v2 Liquidity

For DAMM v2 migration, DBC creates position NFTs for the migrated liquidity. The migration flow:
  1. Creates the DAMM v2 pool.
  2. Creates migrated liquidity positions.
  3. Applies configured permanent locks or vesting locks.
  4. Transfers position ownership to the partner or creator owner.
This means DAMM v2 migration is not just a pool creation step. It also finalizes who controls the migrated positions and how much of that liquidity is locked.

​
Protocol Liquidity Migration Fee

DBC applies a fixed 0.2% protocol liquidity migration fee during migration. This fee is tracked as protocol migration base and quote amounts. In product terms, it reduces the amount of base and quote liquidity that enters the migrated pool and becomes part of protocol-claimable balances.
This protocol liquidity migration fee is separate from the configurable partner and creator migration fee.

​
Leftover After Migration

For fixed-supply launches, some base tokens may remain in the virtual pool after migration accounting. Those unused tokens are called leftover and can be withdrawn to the configured leftover receiver after the migrated pool reaches the created state. Leftover is covered in more detail in DBC Surplus and Leftover.

​
Mainnet Migration Keepers

Meteora operates migration keepers on mainnet to help eligible DBC pools graduate automatically.
Migration keepers run on mainnet. For testing or manual flows, use the manual migrator, which supports mainnet and devnet.