What Is an Airdrop (and How Farming Works)
An airdrop is a distribution of free tokens to wallet addresses, usually to reward people who used a project before it had a token. The mechanics are simple; the judgement involved is not.
Here is what actually happens, and where people waste money.
What an airdrop is
A project reserves a portion of its token supply for early users. At a snapshot, it reads on-chain history and records which addresses showed activity, then distributes tokens based on that record.
The best-known examples rewarded wallets that had used a protocol for months before any announcement was made. That is the pattern: the reward follows genuine use, not a single transaction made after the project started paying attention.
Nothing is free at the start
The tokens may be free, but qualifying is not. Every interaction costs gas, and most farms pay nothing.
Treat each farm as a small bet with a budget rather than a free opportunity. The useful question is not whether an airdrop is free, but what the total gas cost is if nothing arrives.
How projects choose recipients
Allocation methods vary, but the common signals are recognisable:
- Time spent, measured across months rather than days
- Variety of actions, rather than many identical ones
- Self-custody, and a visible history of interacting with the protocol directly
- Absence of links between the wallets you control
Sybil filters are specifically built to catch the second pattern. A single wallet doing varied things over months reads very differently from fifty wallets running the same script.
What usually goes wrong
Doing everything on a testnet when only mainnet activity counts, or claiming the distribution is guaranteed when the project has not announced a token at all.
A points programme is not an allocation. A testnet is not the mainnet. A project that has never announced a token may never distribute one, and the tokens can sit unreleased indefinitely.
A sensible approach
Pick the projects you would actually use, spend modest gas on sustained activity, and keep a record of what you did and what it cost.
That last part matters more than people expect. After a few months you will know your true cost per airdrop, which is the only number that lets you decide whether continuing is worth it.
What the announcement actually tells you
When a project announces its token, it also usually publishes the allocation criteria. That is the moment to compare against what you did, and it is the moment to accept that some farming was wasted.
Allocations are rarely proportional to effort. A wallet with modest, sustained activity often receives more than a wallet with one large transaction, because the latter is indistinguishable from a bot.
Keeping records
Write down the wallet, the protocol, the actions, the date, and the gas cost. This takes seconds at the time and is only possible later if you have kept it.
After a few months that record answers the only question that matters: what did each airdrop actually cost you, and what did it return. Without it, every farm feels equally worthwhile because none of them have a number attached.
The one-wallet rule
Multiple wallets are the single clearest automation signal. Projects running sybil detection have seen every script farm ever built, and they weight accordingly.
If you already have several wallets, consolidating activity into one and letting the history build is usually worth more than continuing to spread.
Frequently asked questions
Are airdrops really free?
The tokens usually are. Qualifying is not: every interaction costs gas, and most farms distribute nothing. The useful calculation is total gas spent divided by what you received, which is why tracking costs matters.
Do I need multiple wallets?
No, and running several is often a negative signal. Projects filter for patterns that automation produces, so many wallets doing identical actions reads worse than one wallet doing varied things over time.
Can a project take away an airdrop after I qualify?
Yes. Finality is typically not guaranteed until the claim period closes, and some projects screen out recipients after the snapshot. Qualifying is a claim, not a guarantee.