Overview: Clanker + PoolFans
How Clanker Works (Mechanics)
Token Archetypes That Fit
Liquidity Lifecycle and External LPs
PoolFans: Tokenized Creator Rewards
Playbooks for Creators
Investor Lens: Why This Stack Matters
Resources
💦 Homepage: pool.fans
📚 Docs: pool.fans/docs
🧭 Clanker Guide: pool.fans/clank
✅ Deployment Cheatsheet: pool.fans/cheatsheet
🏦 Clankernomics: pool.fans/clankernomics
⚙️ Tokenizer: tokenizer.pool.fans
Clanker is a modular, multi-chain token launchpad built on top of Uniswap v4–style pools (factory + hooks + LP locker). It turns “launch a token” into a repeatable onchain pattern instead of a one-off bespoke contract.
A Clanker deployment gives you:
A fixed 100B ERC-20 token.
A Uniswap v4 pool backed by a locked “liquidity staircase” of single-sided token liquidity.
Configurable swap fees that generate ongoing creator rewards.
Reward routing to up to seven recipients, including PoolFans’ Rewards Vaults.
PoolFans sits downstream of Clanker’s reward routing and turns a slice of those creator rewards into ERC-20 Rewards Tokens. That creates a separate, composable layer for owning, selling, and aligning around the fee flows from a token’s market.
Together:
Clanker = launch + liquidity + creator rewards wiring.
PoolFans = control plane for those creator rewards and the incentives built on top.
Traditional launches assume the creator brings quote-asset liquidity (ETH, stables). Clanker inverts that.
On deploy:
The factory mints a fixed 100B ERC-20.
The LP locker posts that token into a set of Uniswap v4 positions as single-sided liquidity across up to seven price bands (the “liquidity staircase”).
These positions are protocol-locked.
You supply tokens, not ETH. Buyers bring the quote asset when they trade. As price climbs through ranges, more of your supply unlocks into the market.
Implications:
No upfront ETH/stables required for a credible market.
Locked, non-ruggable liquidity.
A deterministic launch curve, encoded in how you distribute supply across ranges.
You give up some flexibility in exchange for trust and clarity around how supply exits.
Each Clanker pool has its swap fees wired through a hook:
Every swap pays a configurable fee into the pool’s fee logic.
The protocol takes a fixed cut.
The remainder becomes creator rewards, split immutably across up to seven recipients (basis-point splits).
Simple example:
Pool fee: 1%.
Daily volume: 100k notional.
Raw fees: ~1k.
After the protocol cut, the rest flows as creator rewards to whichever recipients you configured:
Treasury or dev wallet.
Community rewards address.
PoolFans Rewards Vault that mints Rewards Tokens.
Instead of fees accruing to anonymous LPs, Clanker routes them directly into creator rewards rails that you can design around.
Clanker’s hook layer supports different fee styles:
Static fees: fixed basis points for buys/sells when you want predictability.
Dynamic fees: base fee plus a volatility component, skimming more during turbulent periods and less during calm periods.
Fee conversion: creator rewards can arrive as WETH, WETH + token, or token-only, depending on configuration.
You get real levers:
Low static fees if you want frictionless volume.
Dynamic fees if you want to protect depth and harvest more creator rewards when markets are wild.
A choice of what asset your creator rewards accumulate in.
Launches on a public mempool usually devolve into a latency and MEV race. Clanker inserts a MEV-aware module between “deploy” and “open trading.”
High-level flow:
After deployment, swaps are gated for a short protection window.
During this window, the pool runs a sequence of sniper-auction rounds with a descending fee curve.
Aggressive early takers pay elevated fees, which are redirected as creator rewards rather than pure external MEV.
You get:
A staged ramp from protection mode into normal trading.
Early demand partially recycled into creator rewards.
A more legible starting environment for humans instead of a single-block snipe.
Lifecycle: intent → config → deploy → MEV window → open distribution, with the MEV window explicitly designed, not ignored.
The contracts don’t care about narrative, but three archetypes map cleanly to this structure.
For mini-app builders (Farcaster, Base-native apps, and other ecosystems as Clanker expands):
The app has a clear onchain loop: tips, boosts, access levels, in-app actions.
A Clanker token sits at the center of that loop.
Swap fees from trading the token generate ongoing creator rewards.
Those creator rewards are routed to a mix of treasury, community programs, and possibly a PoolFans Rewards Vault.
Creator rewards become the app’s “cash register”:
They scale with real usage and volume.
They can be tokenized as Rewards Tokens and used for aligned incentives (staking, quests, loyalty programs).
They avoid inflationary emissions on the base token.
Creators use Clanker when they want:
Fixed supply + credible, transparent launch rails.
Built-in creator rewards from swap fees.
Optional PoolFans integration for tokenized reward claims.
These tokens can represent:
Access to communities or content.
Participation in a project’s upside.
Membership or reputation inside a graph.
Routing examples:
Some creator rewards to a dev wallet.
Some to a community pool or staking contract.
Some to a PoolFans Rewards Vault that issues Rewards Tokens.
You wire creator rewards onchain at deploy time instead of promising to “share upside later.”
Meme coins are high-throughput users of the system:
Priority: fast, low-friction launch.
The liquidity staircase gives a shaped supply curve without manual LP games.
Swap fees turn volatility into creator rewards while the narrative plays out.
Even if you never touch PoolFans:
Liquidity is locked and transparent.
Fees are configurable and explicitly routed as creator rewards.
Onchain history is clean and easy to integrate with tools and explorers.
Memes and serious applications share the same launch rails and rewards surface.
The core mental model: factory + hooks + LP locker → token + pool + creator rewards wiring. The nuance is how liquidity and creator rewards evolve over time.
At deploy:
The LP locker spreads your token across up to seven price bands, forming the liquidity staircase.
Most non-reserved supply (not set aside for vaults, airdrops, dev buy, etc.) lives in that staircase.
Positions are locked; the only way tokens leave them is when traders buy.
In Phase 1:
Traders bring the quote asset, walk the staircase, and pull tokens out.
Quote asset accumulates behind the remaining tokens in each band.
Swap fees accrue as creator rewards into the fee locker, then out to your reward recipients.
From the creator’s perspective:
If you’re the only reward recipient, you effectively own 100% of the pool’s liquidity and creator rewards (minus protocol cut).
You cannot withdraw or reshape the staircase after deploy.
Price and holder distribution are driven entirely by flow, not treasury decisions.
The bottleneck here is attention and usage. Weak orderflow means most of your supply sits idle in the staircase and creator rewards grow slowly.
If the token catches a bid:
Volume grows.
Holder count grows.
External LPs start adding their own positions around the active ranges.
Now:
Your locked staircase still exists.
Additional LP positions overlay it.
Routers split trades across all positions based on best execution.
Example:
Total liquidity: 80% your staircase, 20% external LP ranges.
Daily volume: 100k notional.
Pool fee: 1%.
Roughly:
About 80k of volume routes through your staircase.
About 20k routes through external LP positions.
Your creator rewards now correspond to ~80% of volume instead of 100%. As successful pairs mature, the share of liquidity controlled by the original staircase usually declines.
Clanker’s range layout and dynamic fees make the staircase harder to dominate, but in a permissionless AMM, creator rewards naturally dilute as more external capital arrives.
The point is not to prevent dilution, but to observe it and decide what to do with that signal.
PoolFans plugs into Clanker by replacing a plain reward address with a Rewards Vault that mints ERC-20 claims on creator rewards.
Baseline: Clanker routes creator rewards to normal addresses. With PoolFans:
In your Clanker configuration, you assign one reward slot to a PoolFans Rewards Vault.
That slot’s share of creator rewards (for example, WETH from swap fees) flows into the vault.
The vault mints a fixed supply of Rewards Tokens, where 100 tokens = 100% claim on that vault’s creator rewards.
Anyone holding Rewards Tokens can claim their pro-rata share via PoolFans contracts.
You now have:
The underlying Clanker token (used and traded by your community).
A separate Rewards Token (claims on the creator rewards generated by that token’s market).
Both are ERC-20s and can move independently.
Without tokenized rewards:
The only way outsiders can tap into creator rewards is to compete with your staircase as LPs, which dilutes your share.
With Rewards Tokens:
You can sell or allocate part of your creator rewards as direct onchain claims, without changing the token supply itself.
Rewards Token holders earn more as volume and creator rewards increase.
They don’t need to post LP capital to share upside.
This changes the incentive landscape:
Fragmented liquidity and mercenary LPs reduce aggregate creator rewards and the value of Rewards Tokens.
Coordinated activity around the canonical Clanker pool increases creator rewards for all Rewards Token holders.
Creator rewards become a shared coordination primitive rather than an internal line item.
Tokenized rewards give you a lever for the hardest part: going from “fresh launch sitting in the staircase” to a live market with sustained activity.
Simple design:
Your Clanker config routes some defined share of creator rewards (say 60%) into a PoolFans Rewards Vault.
That vault mints 100 Rewards Tokens.
Treasury keeps a portion; the rest are sold or allocated to early supporters.
Proceeds from selling a portion of Rewards Tokens can:
Fund development and operations without dumping your main token.
Seed non-inflationary rewards programs for stakers, users, or LPs.
Underwrite PoolFans engagement pools and campaigns.
For Rewards Token buyers and recipients, upside is tied to:
Creator rewards, which track sustained trading and usage.
The health of the canonical pool and the integrations built around it.
Over time, you get a loop:
Tokenized rewards attract aligned supporters instead of purely speculative flow.
Those supporters drive integrations and volume.
Creator rewards increase; Rewards Tokens re-rate.
You gain more room to experiment with PoolFans-powered incentives.
Choose archetype: mini-app, creator/social, or meme.
That choice sets fee levels, staircase shape, and when/if tokenized rewards come in.
Configure fees and reward routing:
Apps: balance user friction vs runway.
Creator/social: design how creator rewards are surfaced back to holders.
Memes: lean into volatility but keep fees meaningful enough to fuel creator rewards.
Treat the first week as a lifecycle, not just an announcement:
Content and casts lined up in advance.
At least one concrete use case or integration live at launch.
Clear, legible story about where creator rewards go and whether there is a Rewards Vault.
Watch three curves:
Your share of total liquidity across ranges.
Volume flowing through your staircase vs external LPs.
Creator rewards per unit of volume.
Introduce or scale tokenized rewards once you have evidence, not just theory:
Real volume and sustained interest.
Historical creator rewards as proof points.
A plan for how Rewards Tokens will be sold, distributed, and used.
Aim rewards at growth behaviors, not passive holding:
Onchain actions that deepen your market and graph.
Bots, mini-apps, and dashboards that integrate your token.
Liquidity that strengthens the canonical pool rather than fragmenting it.
Keep a clear canonical pool and rewards configuration:
One obvious “main” market.
Transparent creator rewards routing.
Simple explanation of any Rewards Vault.
Treat fee config and reward splits as parameters:
Revisit static vs dynamic fees as the market evolves.
Adjust total fee take vs user friction.
Update splits between treasury, community, and tokenized rewards as needed.
Put creator rewards on your mental balance sheet:
Over time you’ll have:A liquid token with trading history.
A visible onchain stream of creator rewards.
A layer of Rewards Tokens and vaults tied to that stream.
That is a composable structure you can plug into treasuries, auctions, lending, indexes, and strategy contracts.
From an investor perspective, Clanker + PoolFans is interesting on three axes: standardization, structural fee capture, and composability.
Clanker provides a repeatable launch primitive across multiple EVM chains.
Projects plug into the same contract pattern instead of rolling their own.
This standardization makes it easier for wallets, explorers, and dashboards to integrate.
Swap fees (and part of the launch-time MEV) are hard-routed into creator rewards.
PoolFans lets those creator rewards be fractionalized into liquid ERC-20 Rewards Tokens.
Over time, every successful Clanker token accumulates a measurable onchain history of rewards flow.
This unlocks:
Protocol-level cuts on creator rewards.
Infra around Rewards Tokens (vaults, auctions, strategy contracts) as additional fee surfaces.
Baskets and indices of fee claims across many Clanker launches.
Without tokenized rewards, external LPs are the only way for outsiders to share upside from trading fees, which dilutes creator rewards.
With Rewards Tokens, creators can sell or allocate fee rights directly to aligned users who don’t need LP capital.
Communities then have a direct incentive to route volume and integrations into the canonical pool where creator rewards are maximized.
The pattern is chain-agnostic: once the factory, hooks, and lockers are deployed on a chain, the same launch and rewards logic applies.
Each new chain adds:
A new surface for Clanker deployments.
A new universe of creator rewards streams.
A larger pool of Rewards Tokens for PoolFans-powered strategies.
More tokens launched on Clanker → more creator rewards streams → more interesting things to build on.
More tools and strategies built on Rewards Tokens → more demand for Clanker-style launches.
The full stack (factory, hooks, staircase design, sniper logic, rewards vaults, and strategies) is opinionated and interlocking, making it harder to clone piecemeal.
Over time, the goal is for “Clanker + PoolFans” to be the canonical way EVM-native tokens launch, own their liquidity, and share creator rewards with aligned holders.
Sources:
Clanker Documentation — Introduction
https://clanker.gitbook.io/clanker-documentationClanker Documentation — v4 Core Contracts (factory, hooks, LP locker)
https://clanker.gitbook.io/clanker-documentation/references/core-contracts/v4Clanker World — Main interface and token deployment surface https://clanker.world
Dish — “Introducing Clanker v4” (Paragraph)
https://paragraph.com/@dish/introducing-clanker-v4unblocked — “Keep the Rewards Flowing: How External LPs Affect Your Clanker Rewards” (Paragraph)
https://paragraph.com/@unblocked/how-external-lps-affect-your-clanker-rewardsUniswap Docs — v4 Overview
https://docs.uniswap.org/contracts/v4/overviewUniswap Docs — v4 Hooks Concept
https://docs.uniswap.org/contracts/v4/concepts/hooks
💦 Homepage: pool.fans
📚 Docs: pool.fans/docs
🧭 Clanker Guide: pool.fans/clank
✅ Deployment Cheatsheet: pool.fans/cheatsheet
🏦 Clankernomics: pool.fans/clankernomics
⚙️ Tokenizer: tokenizer.pool.fans
No posts
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.