Pump.fun Public Documentation

The Pump program enables the creation of SPL coins that are immediately tradable on a bonding curve without requiring initial liquidity seeding.

Key Lifecycle:

1. Bonding Curve Phase: Coins trade on a bonding curve based on a Uniswap V2-style formula using synthetic reserves.
2. Migration: Once a coin reaches a specific market cap, the liquidity is migrated to PumpSwap (an AMM on Solana).
3. Liquidity Burn: The LP tokens received from the PumpSwap pool are automatically burnt.

Program Addresses:

• Program ID: 6EF8rrecthR5Dkzon8Nwu78hRvfCKubJ14M5uBEwF6P (deployed on both Mainnet and Devnet).

PumpSwap is a constant-product Automated Market Maker (AMM) program. It is deployed at the following address on both Mainnet and Devnet:

pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA

When quoting, pricing, or indexing a pool, you must use the effective quote reserves rather than the raw vault balance. This ensures compatibility with future pools that may use virtual_quote_reserves.

Formula: effective_quote_reserves = pool_quote_token_account.amount + Pool::virtual_quote_reserves

Note: The base side remains unchanged; use the raw pool_base_token_account.amount for base reserves. Indexers can reconstruct effective reserves from BuyEvent and SellEvent logs as they include the virtual_quote_reserves field.

Every buy_v2 call requires a feeRecipient and a buybackFeeRecipient.

• Non-mayhem coins: Choose one of the 8 normal fee recipients as feeRecipient.
• Mayhem mode coins: Choose one of the 8 reserved fee recipients as feeRecipient.
• All coins: Choose one of the 8 buyback fee recipients as buybackFeeRecipient.

Refer to the FEE_RECIPIENTS.md documentation for the full list of valid addresses.

The creator_vault is a Program Derived Address (PDA) used to hold fees for a specific coin creator. It is derived using the creator-vault seed and the creator's public key from the BondingCurve account.

PDA Seeds:

• b"creator-vault"
• bonding_curve.creator (the creator's Pubkey)
• bump

#[account(
    mut,
    seeds = [
        b"creator-vault",
        bonding_curve.creator.as_ref()
    ],
    bump
)]
pub creator_vault: AccountInfo<'info >,

The Pump SDK is provided in three distinct tiers depending on your integration needs:

• PumpAmmSdk: The high-level SDK designed for UI integrations. It includes autocomplete methods to help sync UI inputs (like base/quote amounts) with pool states.
• PumpAmmInternalSdk: The low-level SDK for programmatic integrations. Use this when you need full customization of the underlying instructions.
• PumpAmmAdminSdk: A specialized SDK that provides access to admin-protected instructions.

When quoting, pricing, or indexing a PumpSwap pool, you must use the effective quote reserves instead of the raw quote-vault token balance. This ensures accuracy if the pool carries a non-zero virtual_quote_reserves value.

Use the following formula: effective_quote_reserves = pool_quote_token_account.amount + Pool::virtual_quote_reserves

Note: For all pools currently, virtual_quote_reserves is 0, but switching to this calculation now will future-proof your integration.

For Indexers: Effective quote reserves can be reconstructed from the event stream because the BuyEvent and SellEvent logs include the appended virtual_quote_reserves field.

The fee structure has transitioned from a static model to a dynamic model based on the current market cap of the coin (in lamports). This applies to:

1. Pump bonding curves
2. PumpSwap canonical pools: A pool is considered canonical if its pool.creator (not pool.coinCreator) matches the pumpPoolAuthorityPda(baseMint)[0].

To implement this correctly, use the official TypeScript SDKs:

• @pump-fun/pump-sdk
• @pump-fun/pump-swap-sdk

Coin creators accrue fees in two separate, independent vaults depending on the coin's lifecycle stage:

1. Bonding Curve Creator Vault: Held by the Pump program. Fees are drained via collect_creator_fee_v2.
2. AMM Coin Creator Vault: Held by the Pump AMM program (post-migration). Fees are drained via collect_coin_creator_fee.

A creator typically needs to call both instructions to fully sweep all accrued fees.

Note on Migration: If a coin's creator vault has been migrated to a sharing_config (multi-creator-recipient), these instructions will fail. In that case, fees must be distributed through the Pump Fees program instead.