⚡️Introducing Zaps: Completing the Revenue Market Stack.
Today we’re launching Zaps, the final piece of PoolFans’ onchain revenue-market architecture.
Over the last cycle, a lot of effort has gone into tokenizing fees. Some protocols issue claims on cash flows. Others try to bootstrap liquidity around those claims with incentives. Very few systems treat revenue, liquidity, and governance as parts of a single coordinated stack.
Zaps exists to close that gap.
The Revenue Market Stack
At a high level, the system now has three distinct layers:
💦FANS → governance + revenue access
⚡️ZAPS → market ignition + liquidity routing
💸Revenue Tokens → onchain cash flows
Each layer solves a different problem. None of them works properly in isolation.
Revenue tokens without liquidity are illiquid claims.
Liquidity without routing fragments markets.
Governance without control over market formation is mostly symbolic.
Together, these three layers form a complete, self-reinforcing revenue market stack.
Why Zaps Exists
Tokenized revenue does not become a real asset class until liquidity formation is standardized.
Without a shared base layer, revenue tokens tend to:
launch as isolated markets
rely on mercenary incentives
suffer from weak price discovery
fragment liquidity across many pairs
Zaps fixes this by acting as the mandatory market ignition layer.
Every tokenized revenue stream on PoolFans launches paired with Zaps:
Revenue Token / ZAPS
This simple constraint forces:
immediate liquidity
shared routing across markets
consistent depth
real price discovery from block one
More importantly, it allows users to zap liquidity into tokenized revenue markets using a common, protocol-native mechanism instead of ad-hoc LP bootstrapping.
How the System Works
When a new revenue stream is created:
A creator launches a Tokenized Revenue Stream (fees, LP rewards, protocol revenue, etc.).
The protocol allocates ZAPS from the Creator Vault.
A
Revenue Token / ZAPSmarket is initialized.Liquidity incentives activate for LPs.
The market becomes immediately available inside the FANS staking router.
At that point, revenue is no longer just accruing — it’s trading.
Liquidity formation becomes protocol logic, not founder improvisation.
FANS → ZAPS → Revenue Markets
Staking FANS is no longer a purely passive action.
FANS holders earn protocol revenue, but they also gain the ability to route exposure into specific Zaps-based markets. Instead of receiving a blended yield, stakers can choose where their capital expresses conviction.
In practice, this means:
FANS governs access to revenue
ZAPS governs where liquidity forms
Revenue Tokens determine cash flow performance
Yield becomes directional.
Liquidity becomes aimable.
Markets form where participants actually want exposure.
Genesis Distribution
Zaps is being distributed to align long-term market formation with protocol ownership.
10% — FANS holders (genesis access)
At the moment Zaps is deployed, a snapshot of all FANS holders will be taken.
10% of ZAPS supply will be proportionally airdropped to those holders based on their FANS balance at the snapshot.
10% — Initial LPs
Used to bootstrap early liquidity and establish the initial price-discovery surface.
80% — Creator Vault
Reserved for long-term liquidity ignition, future revenue markets, and incentives to zap liquidity into new tokenized fee streams.
This allocation is designed for sustained market creation, not short-term emissions.
What This Unlocks
For FANS holders
You don’t just earn protocol revenue. You participate in deciding where liquidity forms by zapping exposure into the revenue markets you believe in.
For creators
You don’t need to manually bootstrap liquidity or negotiate incentives. Zaps provides a standardized ignition layer for your revenue streams.
For LPs and traders
Every new revenue token launches into the same routing fabric, with predictable structure and composability.
The Flywheel
The system compounds naturally:
Revenue → tokenized
Tokenized revenue → made liquid
Liquidity → routed through Zaps
Routing → governed by FANS
Governance → attracts more revenue
Each layer reinforces the next.
Closing
Zaps completes the stack.
For the first time, onchain revenue can be:
tokenized
made liquid
routed efficiently
and governed coherently
$ZAPS live on: https://www.clanker.world/clanker/0x04cAfd53eCfa6f6a9168dE3d6D2B837D04A51B07
Sweet! Love it!