@poolfans
⚡ANNOUNCING ZAPS — THE FINAL PIECE OF THE REVENUE MARKET STACK💦
Today we’re launching Zaps, the asset that completes PoolFans’ revenue-market architecture.
Some systems tokenize revenue. A few route liquidity. Almost none solve the coordination problem between cash flow, liquidity ignition, and governance.
This is the part we’ve been building toward.
The Stack:
💦 FANS → governance + revenue access.
⚡ ZAPS → market ignition + liquidity routing.
💸 Revenue Tokens → onchain cash flows.
Individually they’re useful.
Together they create the first complete revenue-market stack onchain.
The Role of Zaps:
Tokenized revenue doesn’t become an asset class until you can zap liquidity into tokenized revenue markets in a standardized way.
Zaps makes that possible.
Every revenue token launches with the same base pair:
Revenue Token / ZAPS
This forces:
• immediate liquidity
• shared depth
• unified routing
• real price discovery
And it gives stakers the ability to zap liquidity directly into the markets they want exposure to, instead of passively farming emissions.
How Zaps Flows Through the System:
1. A creator launches a Tokenized Revenue Stream.
2. Protocol allocates ZAPS from the Creator Vault.
3. A new Zaps market activates around that revenue token.
4. LPs earn both swap fees and ZAPS emissions.
5. FANS stakers can zap their stake into these markets to direct revenue exposure.
Liquidity becomes programmable.
Revenue becomes liquid.
Yield becomes aimable.
Distribution:
• 25% — FANS holders (genesis access to Zaps)
• 25% — Initial LPs
• 50% — Creator Vault for future liquidity ignition and market incentives
This is long-horizon infrastructure, not a one-block launch.
What This Unlocks:
For FANS holders:
You don’t just earn revenue. You zap liquidity into the revenue markets you believe in, shaping where depth forms and how yield routes.
For creators:
You don’t bootstrap liquidity manually. Zaps activates the market for you.
For LPs:
A unified routing layer with predictable structure, depth, and composability.
System Flywheel:
Revenue → tokenized
Tokenized → made liquid
Liquid → made routable
Routing → governed by FANS
Each layer reinforces the others.
Zaps is live on Clanker: https://clanker.world/clanker/0x914FBaCfDbC133cffD1e0A9e586cd92EaeBa0B07
Learn more: http://pool.fans/zaps