DBC Fees

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.

DBC fees are built for launches. A pool can start with simple fixed-fee behavior, high anti-sniper fees that decay over time, buy-size-sensitive rate limiter fees, and optional dynamic fees that respond to volatility. This gives launchpads and creators a way to shape early trading behavior while still allowing the token to graduate into a long-term DAMM market.

​

Fee Layers

Every DBC swap starts with a trading fee. $$\text{Trading Fee} = \text{Base Fee} + \text{Dynamic Fee}$$ The base fee is required. The dynamic fee is optional. Fee rates are stored as numerators over 1,000,000,000. A 0.25% fee is 2,500,000, and the total trading fee is capped at 990,000,000, or 99%.

​

Base Fee Modes

DBC has three on-chain base fee modes: linear scheduler, exponential scheduler, and rate limiter. Fixed-fee behavior is also available for teams who want a simple non-decaying fee.

​

Fixed-Fee Behavior

A fixed-fee launch charges one predictable base fee during the bonding curve phase unless optional dynamic fees are enabled. $$\text{Base Fee} = \text{Configured Fee}$$ If dynamic fees are enabled: $$\text{Total Trading Fee} = \text{Configured Fee} + \text{Dynamic Fee}$$ This is the simplest design to communicate. It works best when the launch values clarity over aggressive launch protection.

​

Dynamic Fee

Dynamic fees are useful when a launch wants fees to increase during volatile periods without permanently raising the base fee.

​

Collect Fee Modes

DBC has two bonding-phase collect fee modes.

​

Fee Bounds

DBC bonding phase trading fees use a 0.25% minimum base fee and a 99% maximum total fee cap. These bounds help keep launch configurations valid while still supporting high early fees for anti-sniper designs.

​

Fee Distribution

DBC splits fees into protocol, referral, partner, and creator portions. The referral share is paid out of the protocol fee, not in addition to it. The creator share is controlled by creator_trading_fee_percentage. If it is set to 0%, the partner receives the full partner and creator fee allocation. If it is set to 20%, the creator receives 20% of that allocation and the partner receives the remaining 80%. Trading fee balances are tracked on the virtual pool as swaps happen. Partner, creator, and protocol trading fees can be claimed as they accrue; they do not need to wait for migration.

​

Pool Creation Fees

Partners can configure a pool creation fee that is paid when the virtual pool is created. This fee is split between protocol and partner. Pool creation fee claims are separate from trading fees and migration. They can be claimed once after the virtual pool exists, subject to the program’s claim flags.

​

Migration Fees

DBC also supports a migration fee, which is separate from regular trading fees. This fee is taken from the migration quote amount when the pool graduates. The migration fee can be split between partner and creator. Partner and creator migration-fee withdrawals become available after the bonding curve is complete. They do not require the migrated DAMM pool to be fully created first.

​

Post-Migration Fees

When a DBC pool graduates, the migrated DAMM pool has its own fee behavior. For DAMM v2 migration, the config can define the migrated pool collect fee mode, base fee, dynamic fee option, market-cap scheduler settings, and compounding fee behavior. These settings affect the DAMM v2 pool after graduation, not the DBC virtual pool during the bonding phase.

​

Choosing a Fee Design