What is the Dynamic Bonding Curve?

For integrators to launch tokens with customizable virtual curves directly on your launchpad or platform.

The Dynamic Bonding Curve (DBC) program is a permissionless launch pool protocol that allows any launch partners to enable their users to launch tokens with customizable virtual curves directly on their platform (e.g. launchpad). This allows their users to create a new token and create a Dynamic Bonding Curve pool where anyone can buy tokens based on that bonding curve.

With direct integration into Jupiter and other trading platforms, traders can trade these launch tokens immediately across all these integrations.

The Dynamic Curve program provides these key benefits:

• Launch partners can have different configurations for their launch pools, for example, customizable quote token (SOL/USDC/JUP etc.), customizable curve for token graduation, customizable fees, etc.

• Users on these launch platforms can easily create tokens and launch pools directly with the partners' configurations directly on their partners' UI.

• Trading platforms/bots can immediately trade on these tokens with our direct integrations.

• Tokens will graduate to various AMM (right now we only support Meteora DAMM v1 and DAMM v2), based on partner configuration. With locked LP tokens, launchers can claim fees on the locked LPs.

• Full API support for easy integration for launch partners and trading platforms/bots.

Notable Features

• Multiple quote tokens support: SOL, USDC, JUP etc.

• SPL Token and Token2022 support

• Fee scheduler: Timestamp based fees, such as high fees at launch to deter snipers

• Dynamic Fee: Volatility based fee, to capture more fees during high volume/volatility periods.

• Flexible fee collect mode (e.g. collect fee only in quote token, keep % of all fees generated on the Dynamic Bonding Curve.

• Customizable liquidity distribution (up to 20 price ranges with different liquidity curves)

Customizable Fees

• Virtual pool will collect trading fee evey time user trade with that pool (buy or sell).

• A percentage of trading fee will be paid to the Dynamic Bonding Curve protocol.

• A swap host (Jupiter/Photon/Trading bots) can submit the swap transaction with a referral account to get some referral fee as part of the protocol fee. The rest of the trading fee belongs to the partner.

• After the token has graduated and migrated, LP is locked for the partner and token creator. The ratio of the locked LP is based on what partner has configured in the configuration. With this setup, partner and token creator can claim fees based on the locked LP on Meteora DAMM v1 or DAMM v2.

• The last swap will create a surplus on the quote token, that will be shared between the partner and the protocol.

If the Dynamic Bonding Curve pool is able to reach a pre-defined quote token / price threshold, the liquidity will automatically be migrated to a Dynamic AMM Pool v1 or DAMM v2 Pool on Meteora. The type of pool the token migrates to can be configured by the integrator.

This Dynamic Bonding Curve implementation is open source and available at https://github.com/MeteoraAg/dynamic-bonding-curve

Example Flow

• Partner will create a unique config key, that includes all configuration for their Dynamic Bonding curve on their platform.

  • This can be done using the DBC SDK or via the config key generation UI on launch.meteora.ag
• Users of the platform can create a token and create a Dynamic Bonding Curve pool using this unique partner config key

• Trading platforms (e.g. Jupiter, trading bots) will swap with the Dynamic Bonding Curve pool

• When the pool reaches a pre-defined price/quote threshold, no one can swap with that pool anymore

• Keeper then sends a crank to create a Meteora Dynamic AMM pool and lock the LP tokens

Dynamic Bonding Curve Integration

Please visit this section of the docs.