Skip to main content
Dynamic Bonding Curve (DBC) is Meteora’s token launch primitive for creating a virtual reserve pool, trading through a configured bonding curve, and migrating finished pools to DAMM v1 or DAMM v2. To learn more about fee behavior, migration design, and formulas, you can read the following documentations.

Learn more about DBC

Overview of DBC, universal curves, launch configurations, fees, surplus, leftover tokens, and migration.

DBC Formulas

Formulas for price, curve progress, reserves, fees, and migration calculations.

​
Integration

Program Accounts

Account model for pool configs, virtual pools, vaults, metadata, operators, and migration accounts.

Program Instructions

Instruction families for partners, creators, swaps, migration, fee claims, and operators.

Program Events

Event-CPI payloads for configs, pools, swaps, fee claims, migration, and operator flows.

Program Errors

Anchor custom errors, messages, and common integration causes.

TypeScript SDK

Official TypeScript SDK for config builders, pool creation, quotes, swaps, migration, and state reads.

Transfer Hook SDK

TypeScript SDK methods for Token 2022 transfer-hook configs, pools, swaps, claims, and state reads.

Rust Integration

Rust quote helpers and program-side integration notes for dynamic_bonding_curve.

Go Integration

Go examples for pool reads, swaps, fee claims, and creator transfer flows.

​
Program IDs

The dynamic_bonding_curve program ID is the same on mainnet and devnet: The pool authority PDA used by the program is:

DBC Program

Anchor program source for dynamic_bonding_curve.

DBC IDL

Published Anchor IDL used by the TypeScript SDK.

TypeScript SDK

Public SDK for transaction builders, state reads, quotes, curve helpers, PDA helpers, and tests.

Go Examples

Go examples for backend reads, swaps, fee claims, and creator transfer flows.

​
Migration Keepers

Meteora runs migration keepers on mainnet to migrate eligible DBC pools when the bonding curve is complete and the pool has enough quote-side liquidity.
Migration keepers run on mainnet. The Manual Migrator supports both mainnet and devnet.

​
DAMM Fee Config Keys

The SDK exposes these arrays as DAMM_V1_MIGRATION_FEE_ADDRESS and DAMM_V2_MIGRATION_FEE_ADDRESS.

​
DAMM v1

​
DAMM v2

​
Commands

Some SDK tests depend on local validator fixtures and deployed program artifacts. For production integrations, simulate transactions and test on devnet before sending mainnet transactions.

​
Stay Updated

DBC Changelog

Program, IDL, SDK, quote, migration, and validation changes for integration planning.