DBC

🔧 What Is a Dynamic Bonding Curve?

A bonding curve is a smart contract-based pricing model where the price of a token increases (or changes) as more of it is bought. In the Dynamic Bonding Curve, this curve is virtual and highly customizable, enabling flexible launch strategies.

---

🎯 Purpose

To allow any platform (like a launchpad) to:

• Let users create and launch tokens with their own bonding curve settings.
• Enable dynamic pricing, trading, and migration to an AMM like Meteora DAMM.
• Offer custom fee logic, token types, and trading behavior.

---

🛠️ Key Features and Customizations

1. Customizable Curves

• Partners can define how token prices increase or decrease as users buy/sell.
• Supports up to 20 price/liquidity segments to define fine-grained control over the curve.

2. Multiple Quote Tokens

• Supports SOL, USDC, JUP, and other tokens for pricing and trading.

3. Token Standards

• Supports both SPL tokens and Token2022 (Solana’s advanced token type).

4. Custom Fees

• Base Fees: Fixed fee or time-based fee (e.g., high at launch to prevent bots).
• Dynamic Fees: Fees that adapt to trading volume or volatility.
• Fees can be collected in quote tokens or in both quote/base tokens.
• Portion of the fees can go to: protocol, referrer (Jupiter/bots), partner, and token creator.

5. Launch Pool to AMM Migration

• Tokens graduate to Meteora DAMM v1/v2 once a quote token threshold is reached.
• LP tokens (liquidity provider tokens) are locked, but fees from them can be claimed by creators and partners according to configured percentages.

---

🧩 Partner Integration Flow

1. Create a Configuration Key
   • Partners use the SDK or UI to define all settings (fees, token type, LP distribution, etc.).
   • This configuration is identified by a unique config key.
2. User Launches Token
   • On the partner’s platform, a user launches a token using this config key.
   • A virtual bonding curve pool is created.
3. Token Trading Begins
   • Integrated platforms (e.g., Jupiter, trading bots) can trade the token immediately using the curve’s rules.
4. Threshold Reached
   • When a predefined price or quote token amount is met, the bonding curve pool locks, preventing more trades.
5. Migration to AMM
   • A keeper process triggers migration to Meteora DAMM.
   • LP tokens are distributed and locked based on partner/creator configuration.
   • Fees from LPs are claimable by partners and creators.

---

🧾 Configuration Parameters Explained

Parameter	Description
pool_fees	Fixed and dynamic trading fees configuration.
collect_fee_mode	0 = only quote token fees, 1 = both token fees.
migration_option	0 = migrate to Meteora DAMM.
activation_type	0 = slot-based time, 1 = timestamp-based.
token_type	0 = SPL Token, 1 = Token2022.
token_decimal	Decimal places (6–9) supported by the token.
partner_lp_percentage	Claimable LP % for partner after migration.
creator_lp_percentage	Claimable LP % for token creator.
migration_quote_threshold	Quote amount at which migration is triggered.
fee_claimer	Address where protocol/partner fees are sent.
quote_mint	Quote token address (e.g., USDC mint address).
locked_vesting	Locks creator’s tokens post migration (e.g., for vesting).

---

🧪 Example Workflow

1. Partner creates a configuration (config_key) with desired parameters.
2. A user on the partner’s platform creates a token using that config.
3. The pool launches and begins trading on DBC and integrated exchanges.
4. Once the token hits the configured threshold, it migrates to DAMM.
5. Trading fees and LP tokens are shared among partners and creators.

---

📌 Key Benefits

• Permissionless: Any launch platform can integrate without approval.
• Seamless Trading: Instant tradability via Jupiter and other DEXs.
• Fair Launch Mechanism: Bonding curves deter bot attacks and support gradual price discovery.
• Liquidity Management: Locked LPs and fee-sharing create long-term incentives.
• Open Source: Code is publicly available at GitHub Repository.