pumperp

Clanker

v4 deploy, USDC pools, FeeLocker claims, and dynamic fee tiers.

pumperp launches tokens through Clanker SDK v4 on Base — replacing Fission's Pump.fun integration entirely.

Fee pipeline

sequenceDiagram
  participant T as Clanker token
  participant L as ClankerLocker v4
  participant FL as FeeLocker
  participant P as Protocol wallet

  Note over T: Trading generates LP fees
  P->>L: collectRewards(token)
  L->>FL: Accrue USDC for recipients
  P->>FL: claim(protocol, USDC)
  FL->>P: USDC transfer

Key addresses

Configured in backend/src/config.ts (override via env):

ContractEnv override
CLANKER_LOCKER_V4CLANKER_LOCKER_V4
CLANKER_FEE_LOCKER_ADDRESSCLANKER_FEE_LOCKER_ADDRESS
USDC0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Never hardcode addresses in docs without checking config.ts — use env for deployments.

Deploy

launchToken uses:

  • Clanker from clanker-sdk/v4
  • FEE_CONFIGS / dynamic fee tier
  • getTickFromMarketCapUSDC for initial pool tick
  • Protocol + creator recipients in rewards config

Claims

claimPooledFees(tokens[]):

  1. For each token: collectRewards on locker
  2. Read availableFees(protocol, USDC)
  3. claim if above dust threshold
  4. Return { txHash, usdcClaimed, perToken }

Batch size limited by CLAIM_BATCH_SIZE to keep gas predictable.

vs Pump.fun (Fission)

Pump.funClanker v4
SOL feesUSDC fees
Sharing config PDA verificationRecipients at SDK deploy
Separate admin revoke checkClanker ownership model

Deploy auth

Deploy is fully onchain: clanker-sdk/v4 + protocol wallet via viem. There is no Clanker REST API key in the live launch path.

Optional: PINATA_JWT to pin image URLs to IPFS before deploy (backend/src/services/ipfs.ts).

On this page