How to Run a Crypto Airdrop Campaign Without Wrecking Your Token

What a Crypto Airdrop Campaign Actually Has to Achieve

This guide covers running the campaign. For the underlying allocation and unlock design, see how to design a token airdrop.

A crypto airdrop campaign distributes free tokens to a defined set of wallets, usually to reward past usage, bootstrap a holder base, or seed decentralised governance. That is the textbook description. In practice, an airdrop is the single largest uncontrolled supply event most projects ever run, and it lands on the same day your token starts trading. Design it as a marketing campaign alone and you will get a spike in wallet count, a spike in sell pressure, and a chart that never recovers.

The teams that get this right treat the airdrop as three problems at once: a growth problem (who do we want here in six months?), a distribution problem (how much supply hits the market and when?), and a liquidity problem (can the order book absorb claim day?). This guide walks through each, with the decisions you need to make before you announce anything.

Step 1: Decide What the Airdrop Is Buying

Before you pick criteria, write down the outcome you are paying for. Different goals produce genuinely different designs.

The mistake is picking "all of the above". A campaign that rewards farmers, holders, LPs and social participants equally rewards none of them well, and the group easiest to fake — social task completion — will dominate the claimant list.

Be honest about the awareness goal in particular. A quest-based campaign will reliably deliver large wallet counts. It will not reliably deliver holders. If awareness is the goal, budget for it as a marketing cost and keep the token allocation small.

Step 2: Set Eligibility Criteria That Are Hard to Fake

Eligibility design is where an airdrop is won or lost. The core principle: reward behaviour that costs something real to produce, and cannot be produced cheaply at scale by one actor across many wallets.

Criteria that hold up reasonably well:

• Cost-weighted activity — fees paid, gas burned, or volume traded, rather than raw transaction count
• Duration — activity sustained across multiple months or across distinct market conditions
• Capital at risk — time-weighted balances or LP positions, not a single snapshot balance
• Cross-behaviour consistency — wallets that used several parts of the product in a way that resembles real usage
• Off-chain verification — where your jurisdiction and product permit it, KYC or proof-of-personhood for larger tiers

Criteria that break down quickly:

• Transaction count alone (trivially farmed with dust transactions)
• Single-block snapshot balances (borrow, snapshot, repay)
• Social follows, retweets, and Discord roles as primary weighting
• Anything you publish in advance in precise numeric form

That last point matters more than it looks. The moment you announce "wallets with 10 or more swaps qualify", you have written a specification for farmers. Announce that an airdrop is planned and describe the spirit of eligibility. Keep exact thresholds, weightings and snapshot dates undisclosed until after the snapshot has been taken.

Step 3: Plan Sybil Defence Before the Snapshot, Not After

A sybil attack is one actor running many wallets to multiply their share of a distribution. Every meaningful airdrop attracts them. Your defence is a layered filter, applied to snapshot data before you publish an allocation list.

Layer 1 — funding-graph clustering. Wallets funded from a common source, or that consolidate back to a common address, are strong cluster candidates. This is the highest-yield single check.

Layer 2 — behavioural fingerprinting. Look for near-identical transaction sequences, timing patterns, identical gas settings, and round-number amounts repeated across wallets.

Layer 3 — economic thresholds. Set a minimum meaningful activity level below which a wallet earns nothing. This alone removes the long tail of low-effort farms without any clustering analysis.

Layer 4 — curved allocation. Use a piecewise or logarithmic curve rather than a linear one, so splitting activity across 50 wallets yields less than concentrating it in one. Curved allocation makes sybil farming structurally less profitable rather than just harder.

Two operational points. First, publish an appeals process with a fixed deadline, and expect false positives — legitimate users share funding sources too, and being wrongly excluded is a public relations event. Second, decide in advance what happens to reclaimed sybil allocation: burned, returned to treasury, or redistributed to confirmed users. Deciding this after the list is published invites accusations that you moved the goalposts.

Step 4: Size the Allocation Against Float, Not Total Supply

The percentage of total supply allocated to the airdrop is the number teams debate. The number that determines your chart is different: how much of your circulating supply on day one is airdropped, unlocked, and immediately sellable.

An airdrop that is a modest share of total supply can still be most of the initial float. If claimants can sell everything on day one and your other day-one supply is thin, the airdrop effectively is the market. Work the arithmetic in the other direction: decide what launch float and market structure you want, then size the immediately claimable portion to fit inside it.

Vesting the airdrop is the obvious lever, and it involves a real trade-off. Fully liquid claims maximise goodwill and minimise complexity, but concentrate sell pressure into a few days. Vested or milestone-linked claims spread that pressure out, but reduce perceived generosity and add contract surface area to audit. A common middle path is a liquid portion at claim, with the remainder vesting over months, sometimes with a forfeiture rule for unclaimed or early-exited allocations.

Whatever you choose, model it against your broader unlock schedule so the airdrop tail does not land on top of a team or investor cliff. Our guide to token unlocks and managing sell pressure covers how to sequence these events, and tokenomics design covers how the airdrop fits the wider supply plan.

Step 5: Design the Claim Mechanics

Claim design is unglamorous and causes most of the day-one incidents.

• Claim window. A window that is too short punishes users in other time zones; too long leaves a permanent supply overhang. Several months is a reasonable default, with a stated policy for unclaimed tokens.
• Gas and chain choice. If claiming costs more than the smallest allocations are worth, small recipients cannot claim. Consider claiming on a low-fee chain or sponsoring gas for the lowest tier.
• Contract audit. The claim contract holds a large token balance and is a live target. It needs the same audit rigour as your core protocol, not a rushed review the week of launch.
• Front-end resilience. Claim pages fail under launch load and attract phishing clones. Publish the canonical URL early, everywhere, and repeat it.
• Allocation checker. Let users verify eligibility before claim day. It absorbs support load and surfaces criteria disputes while you can still respond to them.

Step 6: Prepare the Market for Claim Day

This is the step most airdrop guides skip, and it is where campaigns quietly fail. On claim day you have a large cohort of holders with zero cost basis, arriving simultaneously, many of whom intend to sell immediately. That is an entirely predictable liquidity event.

What matters:

• Depth, not just price. The question is not where the token opens but how far the book absorbs sell flow before slippage becomes severe. Thin books turn ordinary claim selling into a chart that looks like a collapse.
• Venue coverage. If claiming happens on-chain and your only depth is on a centralised exchange, claimants route through whatever thin DEX pool exists. Liquidity has to sit where the sellers actually are.
• Concentration risk. Model the top allocation tiers. If a handful of wallets hold a large share of claimable supply, one decision by one holder is your day-one market.
• Timing. Where you can, avoid stacking claim opening, exchange listing and an unlock cliff onto the same 24 hours.

This is the point where airdrop design stops being a marketing exercise and becomes a market structure exercise. Fibonacci Capital works with token teams on exactly this junction — sizing claimable supply against realistic launch float, and providing the order book depth to absorb the flow a distribution event creates. Our PreTGE programme is built around getting these decisions made before launch, when they are still cheap to change.

Airdrop Campaign Checklist

Run this before you announce anything publicly.

Design

• Written statement of what the airdrop is buying
• Eligibility criteria weighted by cost, duration, and capital at risk
• Exact thresholds and snapshot timing kept confidential
• Allocation curve chosen (non-linear, sybil-resistant)

Sybil defence

• Funding-graph clustering method defined and tested on historical data
• Minimum activity threshold set
• Appeals process and deadline published
• Policy for reclaimed allocation decided in advance

Supply

• Airdrop sized against day-one circulating float, not total supply
• Vesting or forfeiture structure modelled
• Claim tail checked against team and investor unlock dates

Execution

• Claim contract audited by an independent firm
• Allocation checker live before claim opens
• Canonical claim URL published widely; phishing monitoring in place
• Gas cost viable for the smallest allocations

Market

• Order book depth sized against modelled day-one sell volume
• Liquidity present on the venues claimants will actually use
• Top-tier holder concentration modelled
• Claim, listing, and unlock events deliberately separated

The Honest Summary

Most airdrops do not fail because the criteria were slightly wrong. They fail because a large volume of zero-cost supply met a thin order book on a pre-announced date, and nobody had modelled what that would look like. The eligibility work protects the quality of your holder base. The liquidity work protects the price those holders see. You need both, and the second one is usually the afterthought — which is a large part of why tokens fail after launch.

If you are planning a distribution event and want the supply and liquidity side modelled before you commit to a structure, get in touch with Fibonacci Capital while the design is still on paper.