The Ultimate Guide to Clanker
How Base's Modular Token Launchpad Actually Works (and How to Use It With Tokenized Fees)
History of Clanker
The Origin Story
Clanker launched in November 2024 as an AI-powered token deployment agent on Farcaster. Created by @dish (Dish), it revolutionized how tokens are created on Base by allowing anyone to deploy a token simply by tagging @clanker in a cast.
What started as an experiment quickly became the primary token factory on Base, kickstarting a new wave of social tokenization and memecoin culture.
Created by
@dish
Launched
November 2024
Network
Base (L2)
Click metrics to view live analytics on Dune
Mental Model: What Clanker Actually Is
1. Onchain Token Launchpad
At the contract level, Clanker is a modular launchpad system:
Factory
- • Mints new ERC-20 with 100,000,000,000 total supply
- • Creates the Uniswap v4 pool for your token pair
- • Pushes tokens into LP via LP locker
- • Triggers extensions (vaults, dev buy, airdrop)
Hooks
- • Implement per-pool fees: Static (fixed) or Dynamic (base + volatility)
- • Implement the protocol fee
- • Route fees into fee locker instead of positions
LP Locker
- • Places up to 7 LP positions for your pool
- • Defines your liquidity "staircase" across price ticks
- • Aggregates swap fees
Extensions + MEV
- • Vaults (locked / vested allocations)
- • Dev / creator buy from your own pool
- • Airdrops with optional locks
- • MEV: 2-block delay, sniper auctions, descending fees
2. Social / UX Layer
On top of that core:
- •
@clankeragent on Farcaster that deploys from casts - •clanker.world as the canonical admin / deploy / claim interface
- •Other UIs (Bankr, Clanker.fun, Pool.fans, miniapps) that call the same contracts
You can treat Clanker as the control plane for token markets built on Uniswap v4, with Farcaster and external UIs as intent surfaces.
Clanker System Architecture
SOCIAL / UX LAYER
Intent surfaces for token deployment
ONCHAIN TOKEN LAUNCHPAD
Smart contracts on Base (Uniswap v4)
MARKET OUTPUT
What gets created on deploy
TL;DR: Cast or click → Clanker factory + hooks → Uniswap pool + fee stream
Deployment Paths + Recommended Setups
Today there are four ways to deploy a Clanker token. All hit the same contracts, but they differ in control, defaults, and typical use.
⛓️ Chain Availability
Clanker is available on:
Pool.fans Tokenizer:
1. Cast Deployment (@clanker)
The original "AI tokenbot" flow that kicked off the Base memecoin boom
Flow:
- • Cast on Farcaster, tag @clanker
- • Include name, ticker, image/GIF
- • Clanker deploys or asks for more data
What it gives you:
- • Fastest path from idea → live token
- • Strong narrative tie to origin cast
- • Fewer knobs; good for memes
Real-world example:
RUNNER – "First memecoin deployed on Clanker | run to earn" on Base
2. clanker.world Deployment
Full control over launch parameters with clear admin UI
Configure:
- • Name, symbol, image, chain
- • Static or dynamic fee model
- • LP staircase layout
- • Vaults / airdrop / dev buy
- • Reward recipients and splits
- • MEV module
What it gives you:
- • Full control over launch parameters
- • Clear provenance and admin UI
- • Better for long-lived tokens
Real-world example:
PoolFans ($FANS) – Dynamic fees (1% base, 5% max), 70% LP, 25% vault, 5% airdrop, Verified Clanker
3. Other Interfaces (Clanker.fun, Bankr, Pool.fans)
Opinionated frontends built on the Clanker SDK and API
Bankr
AI trading agent; launch tokens from X/Farcaster
Clanker.fun
Classic web interface for browsing and launching
Pool.fans
Fee Tokenizer + staking for $FANS integration
Real-world example:
BNKR (Bankr) – AI DeFi companion; second-largest Clanker token by market cap
4. Clanker SDK / API
For devs and new UIs building on top of Clanker
- • Official Clanker SDK and HTTP API
- • Used by Bankr, Clanker.fun, Pool.fans
- • Your app collects config, SDK hits factory, token tagged with your interface
Real-world example:
DEEP – Utility token for automatic Hyperliquid trading bot by 0x911
Recommended Deployment Paths by Persona
| Persona | Recommended Path | Why This Path | Example |
|---|---|---|---|
| Pure meme deployer | Cast with @clanker | Fastest feedback loop, minimal config | RUNNER |
| Miniapp builder | Interface + SDK | Control UX, integrate with app/bot flows | BNKR |
| Creator / protocol | clanker.world + Pool.fans | Full control + ability to tokenize revenue | $FANS |
Token and Liquidity Shape
1. Token Invariants
Every Clanker deployment:
- •ERC-20 on Base (and in some cases Arbitrum / mainnet)
- •100B total supply, non-mintable after deploy
- •Burnable via
burn()
On deploy:
- 1. Full supply minted
- 2. Up to 90% allocated to extensions (vaults, dev buy, airdrops)
- 3. Remaining supply goes into LP locker as initial multi-range liquidity
You post tokens, not ETH. Buyers bring the quote asset in.
2. Liquidity Staircase
The LP locker creates up to 7 Uniswap v4 positions. Each defines a price band and token allocation. You choose:
- •How much cheap supply is available early
- •How aggressively supply unlocks as price rises
- •How sharp or smooth the curve is
This is the "shape of your launch" more than any one number like FDV.
Simulated Liquidity Distribution
positionBps[] across 7 price ranges
Ranges 1-2
Ration cheap supply
Ranges 3-5
Depth for flow
Ranges 6-7
Tail reflexivity
Fees and Reward Routing
Two layers: How much each swap pays, and where fees go.
3. Fee Programmability
v4 Superpower #2 — Clanker v4 exposes Uniswap v4 fee logic through the hook layer. Choose either static or dynamic fees.
Static Fees
- • Fixed bps per input token
- • Can be asymmetric: buy fee 150 bps, sell fee 75 bps
- • Use when you want predictable incentives
Default: 1% static on both inputs if omitted
Dynamic Fees
- • Base fee + variable fee reacting to impact/volatility
- • Defaults: ~0.5% base and up to 5% max
- • Use to skim turbulent periods and protect LP depth during spikes
Example: $FANS runs 1% base, 5% max
Clanker Protocol Fee: 0.2% additive to your configured LP fees
Fee Curve Comparison
Static vs Dynamic fee behavior
Static Fee
Fixed rate regardless of conditions. Predictable.
Dynamic Fee
Scales with volatility. Protects LP depth.
4. Revenue Routing
v4 Superpower #3 — At deploy you set up to 7 reward recipients. rewardBps[] sum to 10,000 and are immutable. Each recipient is paired with an admin that can update the address later.
Revenue Distribution
rewardBps[] splits across up to 7 recipients
Fee Locker
LP Fees Accrued
Treasury
40%
4000 bps
Admin 1
User Rewards
25%
2500 bps
Admin 2
Community
20%
2000 bps
Admin 3
LP Incentives
15%
1500 bps
Admin 4
Admins can update recipient addresses • BPS allocations are immutable
Protocol Cut and Reward Recipients
For each swap:
- 1. LP fee is computed
- 2. Protocol takes its fixed cut
- 3. Remaining fee is split across up to 7 reward recipients with fixed BPS at deploy
Each entry is: (rewardAdmin, rewardRecipient, rewardBps) with BPS sum = 10,000
rewardAdmin can rotate rewardRecipient but cannot change BPS. Fees accumulate in a fee locker.
This is the surface Pool.fans plugs into.
MEV Modules
v4 MEV modules modify early lifecycle behavior, shaping the first swaps after deployment. You can't delete bots. You can decide whether they pay you.
2-Block Delay
Swaps blocked for first two blocks after deploy
Sniper Auctions (V0/V2)
Up to 5 auctions, one every 2 blocks. If a round has no bids, auctions stop.
Descending Fees (V2)
Start at ~80%, decay to ~5% over ~30s, then revert to normal fee config
MEV Protection Timeline
Sniper Auction V2 with descending fee curve
Fee decay: 80% → 5% over ~30s
apply
Fee decay: 80% → 5% over ~30s
Launch Lifecycle (Quick)
Intent
meme, miniapp, creator
Config
cast, clanker.world, or SDK
Deploy
token minted, LP ranges set
MEV Window
delay / auction / ramp
Distribution
most supply in LP
Success
fee stream modellable
Now we plug Pool.fans into that last part.
Recommended Configs by Archetype
These are starting templates, not doctrine. Adjust based on your specific needs.
Miniapp Token
- • 40% Treasury/Vault
- • 40% User rewards / quests
- • 20% LP incentives
Goal: Make your fee stream a subsidy for usage, not a creator tip jar.
Creator/Community
- • 60% Creator treasury
- • 25% Community pool
- • 15% Partners/incentives
Goal: Reward loyal flow, not just the loudest spike.
Meme Token
- • 40% Creator
- • 40% Community/strategy router
- • 20% Partners
Goal: Get through the first hour without bleeding all cheap supply to bots.
Full v4 SDK Example
Complete TypeScript example with 7 ranges, multi-recipients, dynamic fees, sniper auction, and extensions:
import { deployTokenV4, ClankerTokenV4 } from "@clanker/sdk";
// Example: Miniapp-style deployment
const tokenConfig: ClankerTokenV4 = {
name: "PoolFans",
symbol: "FANS",
image: "ipfs://<cid>",
// Pool config
pool: {
pairedToken: "WETH", // default if omitted
initialMarketCap: "50", // denominated in paired token
tickSpacing: 200,
},
// Liquidity curve: 7 ranges
liquidity: {
tickLower: [-887220, -600000, -350000, -150000, 0, 120000, 250000],
tickUpper: [-600000, -350000, -150000, 0, 120000, 250000, 887220],
positionBps: [500, 900, 1400, 1900, 2200, 1600, 1500], // sums to 10000
},
// Fees: dynamic
fees: {
type: "dynamic",
baseFeeBps: 60,
maxFeeBps: 300,
},
// Rewards: 4 recipients, fixed bps
rewards: [
{ admin: "0xAdminA", recipient: "0xTreasury", bps: 4000 },
{ admin: "0xAdminB", recipient: "0xUserRewardsPool", bps: 4000 },
{ admin: "0xAdminC", recipient: "0xLpIncentives", bps: 1500 },
{ admin: "0xAdminD", recipient: "0xPartner", bps: 500 },
],
// MEV module: sniper auction w/ descending fees
mevModule: {
type: "sniperAuction",
startingFeeBps: 8000, // 80%
endingFeeBps: 500, // 5%
decaySeconds: 30,
maxAuctions: 5,
},
// Extensions (optional): vault + airdrop + dev buy
extensions: {
vault: {
bps: 2000, // 20% of supply
lockupSeconds: 30 * 24 * 3600, // 30 days (>= min)
vestingSeconds: 180 * 24 * 3600 // 6 months linear
},
airdrop: {
bps: 500, // 5% supply
merkleRoot: "0x<root>",
lockupSeconds: 7 * 24 * 3600,
vestingSeconds: 60 * 24 * 3600
},
devBuy: {
ethAmount: "0.5",
recipient: "0xDevMultisig"
}
}
};
async function main() {
const result = await deployTokenV4(tokenConfig);
console.log("Token deployed:", result.tokenAddress);
console.log("Pool:", result.poolId);
}
main();Important Notes
- •
positionBpsandrewardBpsmust each sum to 10,000 - • Dynamic fee min/max defaults apply if omitted
- • Sniper auction rounds max at 5; descending fee params follow V2 behavior
Pool.fans Clanker Rewards Tokenizer
Pool.fans sits downstream of Clanker's fee routing and turns Clanker fee streams into Fee Tokens (FTs). Each reward asset type gets its own vault and Fee Token supply.
Audited Contracts
Pool.fans Tokenizer contracts have been audited by 0xMacro, ensuring the highest security standards for fee tokenization.
1. What are "Clanker fees"?
Every buy/sell sends a small cut (e.g., 1%) into a fee bucket. Think of it as a jar of WETH that fills as trading happens.
2. What is a Fee Token?
ERC-20 that represents pro-rata claim on that fee stream. Behave like standard tokens: trade, LP, stake, integrate.
3. How it rewires fees
Each reward asset type (e.g., WETH, WETH+YourToken) gets its own vault and Fee Token. Vault mints 100 FTs = 100% of that stream. Holders claim pro-rata.
Pool.fans Revenue Tokenization Flow
Clanker Token
Trading Volume
Fee Bucket
WETH/ETH
Revenue Vault
Pool.fans Contract
Fee Tokens
100 FTs = 100%
What Creators Do With Fee Tokens
Initial Revenue Offering
Sell FTs for capital
Staking Rewards
Reward long-term holders
LP Incentives
Pay LPs in Fee Tokens
Trade / DeFi
FTs are standard ERC-20
Fee Token holders claim pro-rata share of vault revenue
Protocol Fee Distribution
Pool.fans takes a small 1% protocol fee across all tokenized-fee projects and routes it into the $FANS vault for stakers.
Net effect: Creators keep most of the fee stream but convert part into a programmable asset. $FANS stakers get a thin slice of all tokenized projects in WETH + Clanker tokens + $FANS.
Tokenizing an Existing Clanker Token
Take an existing Clanker token that already has creator fees configured. $FANS itself is a clean example.
Confirm Clanker fee routing
On clanker.world token admin, check reward recipients. Decide what fraction to tokenize (e.g., 60% tokenized, 40% direct revenue).
Point a recipient to the Revenue Vault
Go to Pool.fans Tokenize Revenue, connect admin wallet, select token. Pool.fans deploys/links a Revenue Vault. Update reward recipient address in Clanker admin to vault address.
Mint Fee Tokens
Each reward asset type gets its own vault with 100 Fee Tokens (100 FTs = 100% of that stream's claim rights). If you have 2 reward types, you'll get 2 separate Fee Token supplies. You, as creator, start holding them all.
Run an Initial Revenue Offering (IRO)
Set flat price per Fee Token, amount to sell (e.g., 20%), duration of sale. Users deposit at flat price and receive Fee Tokens directly. You raise capital against future fees without touching base token supply.
Launching a New Token With Tokenized Fees Baked In
You can wire this in at day one instead of retrofitting.
Choose deployment path
clanker.world for full control, or Pool.fans tokenizer UI for Clanker deployment + fee recipient pre-set to revenue vault + IRO/staking primitives on top.
Configure fees and splits
Choose dynamic fees if you want stream to scale with volatility. Define recipients: X% → Revenue Vault (for Fee Tokens), Y% → Creator multisig, Z% → Interface/partner. All encoded at deploy time.
Deploy with vault already wired in
UI creates a Revenue Vault for each reward asset type you configure. On deploy: Clanker factory mints token and pool, reward recipients pointing to vaults are baked in. From first swap, fees flow straight into their respective vaults.
Run an IRO at launch
Pair your token launch with a revenue launch. Announce both: "Base token: 100B supply, dynamic fees" + "Fee Tokens: selling 20% of fee rights at X WETH each over 48 hours." Buyers get two ways to get exposure.
What Creators Can Do With Tokenized Fees
Once you tokenize, you will have your Clanker token (narrative + usage) and Fee Tokens (right to future fees). Each reward asset type gets its own Fee Token and vault. For example, if you deploy with 2 reward asset types (WETH and WETH+YourToken), you'll mint 2 different Fee Tokens—each with its dedicated vault and ERC20 supply.
1. Initial Revenue Offering (IRO)
- • Set flat price per Fee Token
- • Choose amount to sell (e.g., 10-30%)
- • Define sale duration (e.g., 3-7 days)
- • Users pay flat price, receive Fee Tokens directly
Raise capital without dumping base token. Market prices fee stream separately from meme/governance.
2. Other Coordination Patterns
Buyback & Burn
Use vault revenue to buy base token and burn it
LP Incentives
Pay LPs in Fee Tokens instead of base token emissions
Access / Gating
Require Fee Tokens for features, governance, or private pools
Composable DeFi
Fee Tokens as collateral, index components, or yield-bearing assets
Token-Only Clanker Launch vs Clanker + Pool.fans Fee Tokenizer
| Perspective | Token-Only Launch | + Pool.fans Fee Tokenizer |
|---|---|---|
| Creator - Economics | Earns fees directly to wallet; future fee rights are off-chain promises | Fees routed to vault, wrapped into Revenue Share Tokens - sell, stake, or distribute |
| Creator - Capital | Must sell base tokens or run OTC deals | Run Initial Revenue Offering - sell fee rights, leave base token untouched |
| Creator - Coordination | Hard to share fee upside with LPs, partners transparently | Revenue Share Tokens = clean unit to pay contributors with direct fee exposure |
| Traders - Exposure | Only base token (price = narrative + usage + fees blended) | Two-layer exposure: base token for narrative, Revenue Share Tokens for fee throughput |
| Traders - Information | Fee stream hidden as wallet inflows; hard to model | Vault UI shows fee accrual and claims per token - cashflow is legible |
| FANS Stakers - Exposure | Indirect via $FANS price only | Index-like exposure to many Clanker fee streams via 1% protocol fee |
| FANS Stakers - Yield | Rely on speculative upside and ad-hoc utility | Earn stream of WETH + Clanker tokens + $FANS from many Revenue Vaults |
| Complexity | Simpler; everything ends at creator wallet | One extra step: point fees to vault, configure IROs/staking for Revenue Share Tokens |
Upcoming Features
Stake token → Earn token's fee rewards
Time-limited staking pools where holders earn trading fees
For Holders
- •Stake Clanker tokens
- •Earn fee rewards during period
For Creators
- •Incentivize without permanent loss
- •Time-boxed, full control
Create post-deployment liquidity
Add new Clanker-style LPs using vaulted tokens