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.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.
Migration Progress
The program tracks migration as a sequence of states.| State | Product Meaning |
|---|---|
| PreBondingCurve | The pool is still trading on the DBC curve. |
| PostBondingCurve | The curve is complete, and migration can continue. |
| LockedVesting | Required vesting or locker setup has been completed, and the DAMM pool can be created. |
| CreatedPool | The migrated DAMM pool has been created. |
Migration Targets
DBC supports two migration targets.| Migration Target | Product Behavior |
|---|---|
| DAMM v1 | Creates a simpler constant-product DAMM pool and uses LP tokens to represent migrated liquidity. |
| DAMM v2 | Creates a more configurable migrated pool with position NFTs, advanced fee settings, compounding options, and vesting support. |
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.
Liquidity Ownership
DBC can split migrated liquidity between partner and creator buckets. Each bucket can include:| Liquidity Type | Product Meaning |
|---|---|
| Unlocked liquidity | The recipient can manage it according to the migrated pool rules. |
| Permanently locked liquidity | Liquidity remains locked while still supporting the pool. |
| Vesting liquidity | Liquidity unlocks over time according to the configured schedule. |
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:- Creates the DAMM v2 pool.
- Creates migrated liquidity positions.
- Applies configured permanent locks or vesting locks.
- Transfers position ownership to the partner or creator owner.
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.| Keeper | Threshold Requirements |
|---|---|
| CQdrEsYAxRqkwmpycuTwnMKggr3cr9fqY8Qma4J9TudY | 10 SOL, 750 USDC, or 1500 JUP |
| DeQ8dPv6ReZNQ45NfiWwS5CchWpB2BVq1QMyNV8L2uSW | At least 750 USD equivalent in the quote token |
Migration keepers run on mainnet. For testing or manual flows, use the manual migrator, which supports mainnet and devnet.