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 transferKey addresses
Configured in backend/src/config.ts (override via env):
| Contract | Env override |
|---|---|
CLANKER_LOCKER_V4 | CLANKER_LOCKER_V4 |
CLANKER_FEE_LOCKER_ADDRESS | CLANKER_FEE_LOCKER_ADDRESS |
| USDC | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
Never hardcode addresses in docs without checking config.ts — use env for deployments.
Deploy
launchToken uses:
Clankerfromclanker-sdk/v4FEE_CONFIGS/ dynamic fee tiergetTickFromMarketCapUSDCfor initial pool tick- Protocol + creator recipients in rewards config
Claims
claimPooledFees(tokens[]):
- For each token:
collectRewardson locker - Read
availableFees(protocol, USDC) claimif above dust threshold- Return
{ txHash, usdcClaimed, perToken }
Batch size limited by CLAIM_BATCH_SIZE to keep gas predictable.
vs Pump.fun (Fission)
| Pump.fun | Clanker v4 |
|---|---|
| SOL fees | USDC fees |
| Sharing config PDA verification | Recipients at SDK deploy |
| Separate admin revoke check | Clanker 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).
