DBC Accounts and Permissions

This page summarizes the DBC implementation details that are useful when reading pool state, building integrations, or checking whether a claim or migration action is allowed.

Main Accounts

Account	What It Stores
`PoolConfig`	Reusable launch template: quote mint, fee claimer, leftover receiver, bonding curve, fees, migration target, token settings, liquidity distribution, migration fee settings, and migrated-pool fee settings.
`ConfigWithTransferHook`	Transfer-hook launch template: a `PoolConfig` plus the executable transfer-hook program configured by the partner.
`VirtualPool`	Live launch state: creator, base and quote vaults, reserves, current square-root price, activation point, fee balances, migration progress, surplus and claim flags, and protocol migration fee balances.
`TransferHookPool`	Transfer-hook pool state. It stores the same `PoolState` fields as `VirtualPool` with a separate discriminator.
`PartnerMetadata`	Optional partner metadata used by launchpad partners.
`VirtualPoolMetadata`	Optional metadata account for a launched virtual pool, created by the pool creator.
`TokenBadge`	Operator-created allowlist account for a Token 2022 quote mint that is not permissionless-supported.
`Operator`	Admin-created permission account used for protocol pool creation fee claims and token badge management.

SDK state readers normalize standard and transfer-hook account variants. Raw account readers and indexers should still distinguish PoolConfig from ConfigWithTransferHook, and VirtualPool from TransferHookPool.

Lifecycle State

The shared PoolState inside VirtualPool and TransferHookPool tracks migration progress with four states.

State	Meaning
`PreBondingCurve`	The pool is still trading on the DBC curve.
`PostBondingCurve`	The curve is complete and a locker step is still needed. This is used when locked vesting is configured.
`LockedVesting`	The pool is ready for DAMM pool creation, or vesting/locker setup has been completed.
`CreatedPool`	The migrated DAMM pool has been created.

When the quote reserve reaches migration_quote_threshold, normal curve trading stops. If locked vesting is configured, the pool moves to PostBondingCurve; otherwise it moves directly to LockedVesting.

Core Limits

Setting	Program Constraint
Active curve points	`1` to `16` points. The account stores 20 slots for compatibility and future capacity.
Token decimals	`6` to `9`.
Bonding-curve minimum base fee	`0.25%`, stored as `2_500_000` over `1_000_000_000`.
Bonding-curve maximum total fee	`99%`, stored as `990_000_000` over `1_000_000_000`.
Rate limiter duration	Existing rate-limiter pools use up to `43,200` seconds for timestamp activation or `108,000` slots for slot activation. New configs cannot select this mode.
Migration fee percentage	Up to `99%`. If the migration fee is `0`, the creator migration fee percentage must also be `0`.
Pool creation fee	If non-zero, from `0.001 SOL` to `100 SOL`, paid in lamports.
Migrated pool fee	`0.1%` to `10%` when custom DAMM v2 migrated-pool fees are configured.
Day-one locked liquidity	At least `10%` of migrated liquidity must still be locked after one day.
DAMM v2 vesting lock duration	At most `2` years.
Transfer hook program	Must be executable and cannot be DBC, SPL Token, Token 2022, or the default pubkey.

Permissions

Action	Required Authority
Create config	Any payer can create a config account, but the config fixes the `fee_claimer` and `leftover_receiver`.
Create transfer-hook config	Any payer can create it, but the config must be Token 2022 and stores an executable transfer-hook program.
Initialize virtual pool	Creator signs and launches from an existing config.
Initialize transfer-hook pool	Creator signs and launches from an existing transfer-hook config.
Create virtual pool metadata	Current pool creator.
Transfer pool creator	Current pool creator.
Claim partner trading fee	Config `fee_claimer`. Transfer-hook pools use the transfer-hook-aware claim path.
Claim creator trading fee	Current pool creator. Transfer-hook pools use the transfer-hook-aware claim path.
Partner withdraw surplus	Config `fee_claimer`.
Creator withdraw surplus	Current pool creator.
Withdraw partner migration fee	Config `fee_claimer`.
Withdraw creator migration fee	Current pool creator.
Withdraw leftover	Funds can only go to the config `leftover_receiver` after migration. The instruction is permissionless when the transfer fee on the leftover is zero. When that fee is non-zero, `leftover_receiver` must sign.
Claim protocol trading or migration fees	`claim_protocol_fee2` uses the fixed `protocol_fee_authority` signer. The older `claim_protocol_fee` and `zap_protocol_fee` instructions are removed.
Claim protocol pool creation fee	Operator with `ClaimProtocolFee` permission.
Create or close a quote-mint token badge	Operator with `CreateTokenBadge` or `CloseTokenBadge` permission.

Several claim paths also use one-time flags on the pool state, so a valid signer cannot claim the same surplus, migration fee, pool creation fee, or leftover more than once.

Claims by Lifecycle Stage

Lifecycle Stage	Claim Paths
After virtual pool creation	Partner and protocol pool creation fees can be claimed once, when configured.
During bonding curve trading	Partner, creator, and protocol trading fees can be claimed as fees accrue.
After curve completion	Surplus and partner or creator migration fees become available.
After migrated pool creation	Fixed-supply leftover withdrawal, DAMM v1 LP-token claims, and DAMM v2 migrated position ownership are finalized.

Token Support

DBC can launch SPL Token or Token 2022 base mints. New configs must migrate to DAMM v2. Existing DAMM v1 pools can still graduate. Transfer-hook launches are Token 2022 only. They use ConfigWithTransferHook, TransferHookPool, swap2_with_transfer_hook, and transfer-hook-aware trading fee claims. The base mint’s transfer hook is revoked when the curve completes. Quote mints can be SPL Token mints. A Token 2022 quote mint is permissionless when its extensions are limited to MetadataPointer, TokenMetadata, and a TransferFeeConfig whose current fee is zero and whose transfer fee config authority is revoked. Other extensions, a non-zero transfer fee, or a live transfer fee config authority need a TokenBadge. A non-zero fee or a live authority is accepted only by create_config2. The Token 2022 native mint is rejected as a quote mint. Token teams apply for that badge with the Token 2022 Whitelist Request Form. Do not include the token launch date or time. An operator with CreateTokenBadge calls create_token_badge after review. See Quote mint token badges.

Config Validation Highlights

DBC validates the launch template before it can be used:

The quote mint must be permissionless, or a valid token badge must be supplied at remaining account index 0. A missing badge returns InvalidQuoteMint. A badge that does not match the mint returns InvalidTokenBadge.
A quote mint with a non-zero transfer fee or a live transfer fee config authority is accepted only by create_config2.
A base transfer fee, or that quote-mint case, requires constant token supply, no locked vesting, MigrationFeeOption::Customizable, and MigratedCollectFeeMode::Compounding.
The collect fee mode must be QuoteToken or OutputToken.
The migration target must be DAMM v2. MeteoraDamm is rejected for new configs and new pools.
BaseFeeMode::RateLimiter is rejected for new configs and new pools.
Transfer-hook configs must use Token 2022 and a valid executable transfer-hook program.
Mint-authority token authority options are only valid for transfer-hook configs.
Liquidity percentages across partner, creator, permanent locks, and vesting must add to 100%.
Curve prices must strictly increase and every active curve point must have positive liquidity.
Fixed-supply configs must set a non-default leftover receiver and must provide enough supply for the curve, migration liquidity, locked vesting, and the 25% swap buffer.

User Guides

Core Products

Helper Products

Legacy Products

Main Accounts

Lifecycle State

Core Limits

Permissions

Claims by Lifecycle Stage

Token Support

Config Validation Highlights

​Main Accounts

​Lifecycle State

​Core Limits

​Permissions

​Claims by Lifecycle Stage

​Token Support

​Config Validation Highlights

Main Accounts

Lifecycle State

Core Limits

Permissions

Claims by Lifecycle Stage

Token Support

Config Validation Highlights