Reading Airdrop Eligibility Criteria Before You Waste Months
Every season it plays out the same way. A thread goes viral claiming to have cracked the exact eligibility criteria for some protocol’s upcoming drop, a confident list of tasks with numbers next to them, and thousands of people read it, believe it, and start grinding against a formula the team never actually published. Months later the real criteria come out, and half of what everybody optimized for was never counted. The people who did well were usually the ones who went and read the protocol’s own words instead, slowly, before committing a single month to it. This is about how to actually read what a program rewards, so you spend your effort on what’s real rather than on what read well on a timeline.
Reading before doing
I run real proxy and cloud phone infrastructure for a living, and I treat airdrop farming the same way I treat any operation: a reading problem before it’s a doing problem. Before I spend gas or time on a protocol, I want to understand what it actually rewards and how much I’m allowed to trust that. Reading eligibility criteria well isn’t a trick and it isn’t insider access. It’s the boring discipline of separating what a team has said from what the internet has guessed, and weighting the two accordingly.
What criteria actually means
Start with what the phrase even refers to, because people use it loosely. A program’s eligibility criteria is the whole answer to one question: what does this reward? That answer lives in a few places at once. Some of it is written down plainly by the team. Some of it is implied by a points system quietly counting in the background. Some of it only becomes clear after the fact, once a formula is published. Reading the criteria means assembling that answer from real sources, not adopting the first confident version somebody hands you, and holding it loosely enough to update when the picture changes.
Start with the official docs
The first place to look is always the team’s own material: the documentation, the blog posts, the announcement of a points phase or a testnet, and any founder interviews. This is the primary source, written by the people who will eventually decide what counted, and it’s astonishing how few people read it before acting. Teams very often state, in plain language, what they want tested or used and what they consider meaningful participation. Following their stated intent is worth more than any secondhand list, because it points at exactly what they measure. Read it closely, more than once, before you touch anything.
What the points dashboard shows
When a protocol runs a live points dashboard, it’s telling you plainly that usage is being tracked, and roughly what’s being valued. That dashboard is one of the most honest signals you’ll get, so treat it as an experiment rather than a scoreboard. Do a real action and watch what moves your number and what doesn’t. The categories that earn points, the actions that earn nothing, the way points decay or compound: all of that is the criteria showing itself in real time. A program that counts and displays points is far more legible than one that stays silent, and that legibility is worth something.
Confirmed versus implied
As you read, keep two piles separate: what the team explicitly confirmed and what you’re merely inferring. An explicit statement about rewarding early users is a confirmed criterion. A points dashboard rewarding a certain action is strong but still implied, because points don’t always convert to an allocation the way people assume. A pattern from a prior season is a hypothesis. A forum thread is a rumor until proven otherwise. Labeling each source honestly stops you from treating a guess with the same confidence as a stated fact, which is the single most common reading error in this space.
Rumor and influencer hype
Most of what circulates as leaked criteria is inference dressed up as fact. A thread that promises the exact tasks, with a clean numbered checklist and a confident tone, is usually one person’s guess presented as an answer key. Treat it as a hypothesis to check against the primary source, never as the source itself. Understand why the loudest accounts are so often wrong, because it’s structural, not personal. Confident predictions get engagement, referral clicks, and follows whether or not they turn out accurate. The incentive rewards certainty, not correctness, so a claim being popular tells you it was compelling, not that it was right. I weight sources by how close they sit to the team itself, which usually means the flashiest take is the one I trust least, and the dull documentation nobody shared is the one I trust most.
Read the last season
Nothing here has to be guessed from scratch when a team has done this before. A protocol’s prior season tells you almost exactly what it counted and what it ignored, and almost every team tweaks its formula rather than reinventing it, which makes the last distribution from the same team the closest thing to a real answer key you’ll find. Read how they scored people, what they weighted, who they filtered, and what they said afterward about why. A published prior formula, however rough, is a confirmed data point about how this specific team thinks, and that’s far more reliable than any fresh prediction about the season in front of you.
Read the category, not just the project
Even a brand new team is rarely a blank slate, because categories tend to reward similar behavior. Competitor protocols in the same category that already launched a token, and published or leaked their formulas afterward, are some of the best pattern matching available. A lending market tends to value real borrowing and sustained positions. A bridge tends to value genuine volume moved and used on the far side. An appchain or a restaking layer has its own recurring shape. Reading three or four drops across a category teaches you what it consistently cares about, even when the specific team has said almost nothing yet.
Revealed after the fact
A pattern worth internalizing is that many teams publish the exact criteria only after the snapshot, deliberately, to stop people cramming qualifying activity in at the last second. That timing is a defense against gaming, not hostility. It also means that during the window itself you’re always reading with incomplete information, working from intent and prior behavior rather than a final rulebook. Accepting that up front changes how you act, because it pushes you toward genuine sustained use that holds up under whatever formula eventually lands, instead of a precise optimization against rules that don’t exist yet.
Vague on purpose
Learn to tell apart three kinds of vagueness, because they mean very different things. Some teams are vague because the criteria genuinely aren’t decided yet, which is normal early on. Some are vague on purpose, hiding the formula so it can’t be gamed, while still clearly intending to reward usage. And some are vague because there’s no real plan behind the noise at all. The first two are workable if the intent to reward users is signaled somewhere. The third is a warning. Telling them apart comes from reading whether the team talks concretely about rewarding early users, or just lets the ambiguity do its marketing for it.
Reading the silence
Silence is also a reading. A protocol with no live points system, no founder statement about rewarding usage, and a documented no-token stance is telling you something plainly: that continued activity there is a product decision, not a qualification decision. Take that at face value rather than as a formality, because plenty of teams mean exactly what they say. No amount of clever reading turns an explicit no-token stance into a reliable opportunity, and treating the absence of any signal as a hidden signal is how people talk themselves into grinding a protocol that was never going to reward them.
Weighting your sources
Once you’ve gathered everything, rank it, because not all of it deserves equal weight. An explicit current statement from the team sits at the top. Live points dashboard behavior comes next. A published prior season from the same team comes after that. A category pattern from competitors sits below that. And an untraceable forum or influencer claim sits at the very bottom, useful only as a hypothesis to test against everything above it. Reading the criteria well is mostly this act of weighting, not collecting claims and trusting the loudest or most recent one.
Criteria change
Hold all of it loosely, because none of what you read is locked. Seasons get repriced, thresholds move, actions that counted last time get discounted this time precisely because too many people optimized for them, and snapshots land on dates nobody announced. A formula leaked from a prior season guarantees nothing about the next one. This isn’t a reason to skip the reading, it’s a reason to keep it current and prefer strategies that survive a formula change. Genuine, varied, sustained use is robust to the criteria shifting under you. A narrow optimization against last season’s exact rules is the first thing to break when they move.
Mapping criteria to effort
Reading is only half the job. The other half is turning what you read into an honest estimate of cost. Once you understand what a program rewards, price it out: the gas per meaningful action, the weeks of sustained use it implies, the attention it pulls from everything else you run. Every action on a chain costs real money, and that cost doesn’t disappear because no token has launched yet and may never launch at all. Laying the likely criteria next to the real cost turns a vague sense of opportunity into a decision you can actually defend to yourself.
Worth it for you
Then decide honestly whether it’s worth it for you specifically, because that answer is personal. A program that rewards deep, sustained, gas-heavy use over many months might be right for a serious operation and wrong for someone with a few hours a week. Reading the criteria well means reading them against your own time, capital, and tolerance for an outcome that may be nothing. Walking away from a program after reading it honestly isn’t a failure of effort, it’s exactly the decision the reading was meant to help you make, and it’s often the right one.
Keep your own record
Keep a plain record of what the criteria said and when, because your reading is a moving target and memory doesn’t scale. A simple note per program, what was confirmed, what was implied, what the prior season did, dated as you learned it, turns a fuzzy impression into something you can actually revisit. That record helps twice: once when you’re deciding where to spend more effort, and again later if a program ever runs an appeal for users it filtered by mistake, because a dated account beats a vague memory of having tried.
The honest limits
Then the part that has to be said plainly every single time. Reading the criteria perfectly still guarantees nothing. Most protocols that run a points program or a testnet never launch a token at all. Most tokens that do launch never get allocated the way early reading suggested, and no formula from a prior season binds the next one. None of this is financial advice, none of it predicts what any token will be worth, and none of it promises an outcome of any size. Reading the criteria is worth doing because it stops you wasting months on the wrong thing, not because it delivers a payout at the end.
We farm these the boring, methodical way and write up what actually qualifies, with a source-by-source breakdown of how to read a program’s criteria and a notes template you can copy. No hype, no guaranteed numbers, just the process of reading before committing. You can find the rest of the guides at the Airdrop Farming home page.
Get new guides and videos first — join the Telegram channel.