Airdrop Season Playbook: Farmers vs Real Users

Every airdrop attracts two populations: people who would use your product anyway, and people optimising for the drop. You cannot eliminate the second group, and trying to usually damages the first. The goal is a distribution where the majority of tokens land with users who still show up a quarter later. This playbook covers eligibility design, sybil resistance, timing, and what to do the week after tokens hit wallets.

TL;DR

• Define the behaviour you want to reward before you define the snapshot.
• Sybil filtering is a ranking problem, not a binary one — score wallets, do not just ban them.
• The retention work happens after the claim, not before it.

Step 1: Decide What the Airdrop Is Actually For

Airdrops get used for at least four incompatible goals. Pick one primary:

Goal	Reward shape	Failure mode if mismatched
Bootstrap usage	Reward depth of use over time	Rewards one-shot transactions
Decentralise governance	Cap per wallet, reward tenure	Whales dominate the DAO
Reward early believers	Weight by first-interaction date	Latecomers feel excluded
Generate attention at TGE	Broad, shallow distribution	Immediate sell pressure

Most disappointing airdrops are a goal-three design being judged by goal-one metrics.

Step 2: Design Eligibility Around Costly Behaviour

Farmers optimise whatever is cheap to fake. Skew criteria toward behaviour that costs something real:

• Duration held or staked, not a single snapshot balance.
• Multi-epoch activity — active in at least N distinct weeks, rather than N transactions.
• Behaviour that only makes sense if you use the product (repaying a loan, closing a position, voting on a proposal that affected your position).
• Off-chain contribution where it is verifiable: merged pull requests, translated docs, moderated channels.

Avoid raw transaction counts, raw volume, and referral counts as primary criteria. All three are cheap to manufacture.

Step 3: Sybil Resistance as a Score

Treat sybil detection as a ranked signal stack rather than a blacklist. Common signals: funding-source clustering, near-identical action timing across wallets, gas-source overlap, dust distribution patterns, and wallets whose only counterparties are each other. Weight them into a score, apply a haircut band rather than a cliff, and publish the methodology before the snapshot.

Publish an appeals window too. Some legitimate users — multisig treasuries, custodial users, teams sharing a funding wallet — will trip clustering heuristics. An appeals process costs a few days and prevents the loudest post-drop grievance category.

Step 4: Distribution Shape and Timing

• Cap the top end. A per-wallet cap costs you little and dramatically improves distribution optics.
• Use a floor. Tiny allocations that do not cover claim gas generate complaints and no goodwill.
• Vest the largest tier, not the smallest. Vesting small allocations creates thousands of unhappy users for a trivial reduction in sell pressure.
• Announce the claim window length up front and honour it. Rolling deadlines read as manipulation.

For the mechanical side of getting tokens out, see Crypto Airdrop Strategy 2026 and Token Distribution Models.

Step 5: The Week After the Claim

This is the part most teams skip. The claim page is the largest traffic event your product will have that quarter, and it is a conversion surface:

1. Put a genuine next action on the claim confirmation — stake, vote, try the core flow — not just a link to a DEX.
2. Segment claimers by prior behaviour and message them differently. First-time wallets need onboarding; long-tenured users need a reason to go deeper.
3. Instrument retention at day 7, 30 and 90 by eligibility tier. This tells you which criteria actually predicted real usage, which is the input to your next distribution.
4. Publish a transparency post: totals claimed, tiers, sybil haircuts applied, unclaimed treatment.

See Retention Strategies for Web3 for the follow-through and Designing Community Rewards That Don't for ongoing programs.

Working With Metamoonshots

We help teams design distributions that survive contact with farmers — criteria design, sybil methodology, claim-flow conversion and the post-claim retention program. If you are planning a drop, talk it through with us before you set the snapshot date.

🔗 Related reading from the Metamoonshots Journal

• 27 Growth Hacks for Web3 Projects
• Viral Loop Design for Crypto Projects
• The Launch Week Playbook: 7 Days
• Web3 Retention: Patterns That Keep Holders

FAQ

Should we announce eligibility criteria in advance?

Announce the principles in advance and the exact thresholds after the snapshot. Publishing exact thresholds early turns your criteria into a farming spec.

What percentage of an airdrop typically goes to farmers?

It varies enormously by criteria design, and any single published figure is unlikely to transfer to your project. Measure it for your own drop by tracking day-30 retention per eligibility tier.

Is a retroactive airdrop better than an ongoing points program?

Retroactive drops reward genuine past behaviour and are harder to game. Points programs are easier to farm but give you a live lever. Many teams run a retroactive first season and a points-based second.

Should unclaimed tokens be burned or returned to treasury?

Decide and publish before the claim opens. Either is defensible; changing the answer afterwards is not.