Meteora DBC Explained: Bonding Curve to DAMM v2

What Meteora's Dynamic Bonding Curve is, how the virtual pool prices a token launch, and how the pool graduates into DAMM v2 liquidity.

Short answer

Meteora DBC (Dynamic Bonding Curve) is Meteora's token launch product. The token trades on a configured curve in a virtual pool, then graduates into a DAMM v2 pool.

In this guide 6 sections

What is DBC?

DBC stands for Dynamic Bonding Curve. It is Meteora's token launch product.

A launchpad or creator configures a curve once. The token then trades against a virtual pool, a pricing pool that exists only to run that curve.

Every buy adds quote tokens, the token you pay with, usually SOL or USDC. Each buy moves the price along the curve.

Sells do the reverse. The design gives a token on-chain price discovery before any normal pool exists.

After the launch, the token moves to a DAMM v2 pool. DAMM v2 is Meteora's Dynamic AMM (automated market maker) version 2.

The two phases

A DBC launch runs in two phases: the bonding curve phase and the graduated pool phase. The table follows the official product documentation.

DBC launch stages
StageWhat happens
Create configA partner or launchpad sets the quote token, curve segments, fees, token type, and migration target.
Create virtual poolThe creator launches the base token, the new token for sale, and its virtual pool from that config.
Trade on curveBuyers and sellers trade against the virtual pool until the quote reserve reaches the configured threshold.
Curve completeNormal curve swaps stop. Surplus quote and configured migration-fee claims become available.
Migrate to DAMMThe quote reserve and a configured base amount seed a DAMM pool; new launches use DAMM v2. Meteora's migration keeper, an automated service, runs the migration.

The curve and the threshold

The curve can use one segment or up to 16 segments. More segments let a team shape the price path in stages.

The migration threshold is a quote reserve target. When it is reached, the launch can graduate.

Leftover base tokens and surplus quote tokens are claimable after the curve completes. The docs define who can claim and when.

Launch fees and controls

Launch teams can configure a fee scheduler with fixed, linear, or exponential fee steps.

The docs list a rate limiter mode. It raises the fee as buy size grows. Meteora has deprecated it for new configurations.

Dynamic fees add a volatility-based layer on top of the base fee mode.

A partner can define the curve, fees, migration target, and LP distribution once. A creator then launches a token from that config.

Life after graduation

After migration, traders use the DAMM v2 pool. The curve and the virtual pool stop.

The docs set a 0.2% protocol migration fee. Migration also needs at least 10% of the liquidity locked on day 1, with vesting capped at two years.

Some DBC launches use tokens with transfer fees. A transfer fee takes tokens from a transfer. On the DAMM v2 migration path for these tokens, the larger fee fraction reduces both token deposits. Check the graduated pool's actual liquidity before you deposit.

For an LP, the graduated token is a normal DAMM v2 pool. The pool creator sets its range; LPs cannot set their own.

See the DAMM v2 guide. Treat a freshly graduated token like a new memecoin pool. Read the degen basket guide before you LP.

Treat the first days after migration as high risk. Thin liquidity, few holders, and unproven demand are common then.

What DBC is not

DBC is not a DLMM pool. It has no bins, no ranges, and no LP positions during the curve phase.

New DBC configs and new pools must graduate to DAMM v2. DAMM v1 stays available only for pools configured with that target earlier.

A separate DLMM pool for the token, if one exists, is independent of the launch. LP liquidity normally arrives with the migration.

Sources & inspiration