Campaign Flow
How a funded campaign runs, in order, from the sponsor locking the budget to a trader claiming a reward.
A campaign is the one place zaps convert into a token. Everywhere else in Zaps a zap is standing. Here it is the share key for a real pool that a protocol has funded.
This page walks the whole flow in order.
The three roles
| Role | What they put in | What they get |
|---|---|---|
| Sponsor | The reward pool and a volume target | The volume delivered, plus every unspent token back |
| Trader | The trading they already do | 95% of the unlocked pool, split by score |
| Creator | The clan they brought | 5% of the unlocked pool, split by clan contribution |
The pool is one number, locked before anything starts.
The flow
The sponsor funds the pool
The sponsor picks the token, the pools to track, the size of the reward pool, and a volume target. The full pool moves into an onchain distributor contract before registration opens. No funded distributor, no campaign.
The tracked pools are published. Anyone can check the set.
Registration opens
One button. Press Register and you are in.
A clan leader's single press registers every current member of their clan at the same time, credited to that clan, and tells the leader how many came in with them. Nobody is registered twice. A member who already left the clan is never swept in.
Registration runs for about two days and closes before trading starts.
Your history is read
This is the part most people expect to work differently.
Registering does not start your record. It claims it. From that moment Zaps reads your whole history with the sponsor's protocol and puts it on the board. You do not have to do anything new to rank.
What counts depends on the protocol. Where a protocol has vote-escrow, it is what you traded, what you locked, and how many weeks you turned up to vote. On some protocols more than half the supply is locked rather than traded, so a leaderboard built only on swaps cannot see those people. This one can.
Your row reads being read until the numbers land, usually within a few minutes.
The trading week
Trade as you normally would, in any of the tracked pools. Nothing to install, no special router, no permission to grant.
The leaderboard moves in near real time. Your row shows each signal with its raw number, your volume for the week split into traded, removed and counted, and your projected share of the pool.
Volume is verified
Not all onchain volume is real. A wallet can trade against itself and produce a large number that means nothing.
So a campaign pays on qualified volume:
qualified volume = what you traded − what was removedA real trade takes risk. The price moves while you hold it and you can lose. A wash trade is built to avoid exactly that, so that is the thing being measured. Volume that carried no real market risk is removed before anyone is paid, and wallets funded from one source count as one identity.
Your row shows all three numbers. Nothing hides behind a single score.
Zaps reads the chain itself. There is no third-party indexer, no subgraph, and no vendor between your trade and your row.
The campaign ends and the numbers freeze
Trading stops at the campaign's end block. The chain is given time to settle, then a final pass reconciles, filters and scores everything once more. The numbers stop moving.
That takes about 24 hours.
The payout is published
Every entitlement is written into one published summary onchain, which anyone can check independently.
Then it waits. The distributor holds a mandatory delay before a published payout can pay, so a wrong result can be challenged before any money moves. The delay belongs to the contract, not to Zeru, and cannot be shortened.
From the end of trading to claims opening is about 36 hours.
You claim
Claiming is your own transaction against a public contract. Once your payout is in the published summary, Zeru cannot withhold it.
The claim window is 30 days. Anything unclaimed after that returns to the sponsor.
How your share is worked out
Your share is your score divided by everyone's score. That is the whole rule.
- No caps, no tiers, no multipliers. A few signals, weighted, added up.
- Each signal is scaled so one very large wallet cannot own the board. The result ranks people, not balance sizes.
- Every trade in your history is priced at the block it happened, from the trade itself or from an onchain price feed. Never a daily average.
- More participants means a smaller slice each. The pool is fixed and your share is a fraction of it. If a thousand people register instead of a hundred, every slice shrinks.
Zaps ranks registered wallets. A wallet that never registered is never on the board, whatever its history.
How much of the pool opens
The pool does not all unlock automatically. It opens in proportion to the volume the campaign delivers.
unlocked = pool × (volume delivered ÷ target), capped at the full poolReach the target and the whole pool opens. Deliver half and half opens, and the rest returns to the sponsor. That is why a sponsor funds one at all: they pay for volume actually delivered, not for a promise.
Two things about that volume, and both matter:
- Only the campaign week counts. Your lifetime history decides how the pool is divided. It never decides how much of the pool opens. Nobody arrives with three years of trades and unlocks the pool on day one.
- Only registered wallets count. A stranger's swap in a tracked pool is indexed and visible, but it neither earns a share nor moves the unlock.
The pool size is never a guaranteed payout. If a campaign underdelivers, the pool everyone splits is smaller.
Clans and creators
A trader can be credited to a clan. The clan leader earns from the 5% leader pool, in proportion to what their clan contributed.
The clan snapshot is taken once, at registration. Switching clans mid-campaign cannot move credit already earned. If a trader has no clan, that 5% is not paid to nobody; it returns to the sponsor.
You can still belong to many clans on the platform. Inside one campaign you count toward the clan you registered with.
Why the payout is safe to trust
- The distributor is owned by a multi-signature wallet. No single Zeru key can drain the pool.
- The automation that runs unattended can only submit a payout into the delay and accept it after the delay. It cannot publish one instantly and it cannot skip the wait.
- The published summary is onchain. You can verify your own entitlement without asking us.
- Claiming is your transaction, not our transfer.
Zaps never holds your funds at any point in a campaign.
Timings
| Stage | How long |
|---|---|
| Registration | 2 days |
| Trading | 7 days, set per campaign |
| End of trading to claims open | 36 hours |
| Claim window | 30 days |
Trading length is set per campaign. The rest is fixed.
Before you register
- Your share is a fraction, and it shrinks as more people join.
- The pool size is not a promise. It opens with the volume delivered.
- Volume that carried no market risk earns nothing.
- Your reward is claimed, not sent, and you pay the gas for your own claim.
- The first campaign runs with a test reward token that carries no value. This run proves the machine end to end, not the money.
The first campaign is live on Base. Registration is open, and its trading window runs to 17 September 2026. Traders, Creators and Protocols cover the rest of the network.
Join Zaps