An in-depth guide to how Web3 teams design and apply eligibility criteria for airdrops, exploring theoretical foundations, anti-sybil mechanisms, and practical, step-by-step practices for real-world participation.
# Airdrop Eligibility Criteria: What Teams Actually Look At
In Brief (TL;DR)
Airdrops rarely hinge on a single action or metric. Most programs blend on-chain activity, wallet longevity, and interaction diversity to separate genuine users from bots or sybil farms. This multi-factor approach helps projects reward meaningful participation over time. (passiveblocks.io)
Sybil resistance is a core design constraint. Teams deploy layered defenses (e.g., funding-source clustering filters, time-weighted activity, and cross-protocol engagement) to minimize shortcut allocations. (orcalayer.com)
Real-world examples show how criteria are implemented in practice: Merkle-tree based claims (proofs on-chain), weightings tied to wallet behavior, and post-snapshot exclusions when patterns look artificial. (github.com)
Tools and public documentation from protocols (Treehouse, Handshake, Polymarket, etc.) reveal a spectrum of approaches—from proxy metrics (Nuts balance) to multi-week usage patterns and cross-ecosystem participation. (docs.treehouse.finance)
“Sybil filters cut wallets on funding-source clustering and activity compressed into a short window.” — OrcaLayer Research. (orcalayer.com)
1. Theoretical Foundations & Invariants
Airdrop design sits at the intersection of incentives, security, and user experience. The core task is to reward genuine, long-horizon engagement while keeping the distribution resistant to manipulation. Several recurring invariants emerge across programs:
Fairness vs. efficiency: Projects must balance broad reach with precise targeting. A naive, universal “everyone gets something” approach can dilute value, while overly harsh criteria risk disenfranchising active community members. This tension is a recurring theme in research and practitioner writings on airdrops. Sybil resistance as a first-order constraint: If it’s cheap to create many identities, an airdrop can be gamed. A variety of anti-sybil techniques—ranging from time-weighted activity to cross-protocol signals—are deployed to elevate the cost of farming. (passiveblocks.io)Activity depth over bursts: Programs tend to penalize short-lived, high-frequency bursts and reward sustained engagement, multi-protocol usage, and varied interactions. This principle is echoed in public analyses of multiple programs and in academic work on reward attribution frameworks. (passiveblocks.io)Transparent, verifiable signals matter: Airdrops increasingly rely on on-chain signals that can be audited by the community—e.g., Merkle-tree proofs, on-chain snapshots, and public scoring methodologies—so participants can verify eligibility. (github.com)Key sources and concepts that shape these invariants include: a Merkle-tree-based distribution mechanism (a tangible example of cryptographic proof of eligibility), treatments of on-chain activity scoring, and the need to deter “airdrop farming” without sacrificing genuine participation. See the Handshake Merkle-tree approach for redemption, and the broader discourse on anti-sybil and gas-efficient scoring for airdrops. (github.com)
Blockquote: A practical summary from program documentation and research notes:
“The Merkle-tree-based airdrop allows the owner of an eligible private key to publish a signed merkle proof on chain in order to redeem their airdrop.” — Handshake Airdrop docs. (github.com)
Broadly, the literature also emphasizes that many programs publish their criteria publicly to allow audits and external critique, even if exact weightings remain implicitly tuned by the protocol. Treehouse’s documentation on eligibility criteria and airdrop checkers, for example, demonstrates a governance-like approach to eligibility where wallets are evaluated against explicit, measured conditions. (docs.treehouse.finance)
Researchers have also begun to model these systems as adversarial reward programs, highlighting how composite scoring (rather than single metrics) can mitigate manipulation while preserving differentiation across users. The ZAPs framework and related work explore robust scoring with anomaly detection to resist manipulation—precisely the kind of design pressure that shapes modern airdrops. (arxiv.org)
2. Step-by-Step Tutorial (Practice)
This section translates theory into practice for participants who want to understand how to approach airdrops with integrity, while respecting the security and ethics of the ecosystem. The steps below blend general best practices with concrete signals used in known programs.
A. Prerequisites & Security
Protect your keys and verify official channels. Projects warn participants about phishing and scams, and recommend using official redemption tools rather than ad-hoc scripts or third-party services. Always confirm you’re interacting with the project’s legitimate domain and tooling. A strong example is Handshake’s explicit warning about scam attempts and the recommendation to use their official airdrop tool only. (github.com)
Understand what a “proof” means in practice. Some airdrops rely on cryptographic proofs (Merkle proofs) published on-chain to verify eligibility without exposing private data. This pattern is central to Merkle-tree based airdrops and is described in Handshake’s redemption flow. (github.com)
On-chain traceability for due diligence. Etherscan provides context on how to explore a wallet’s activity, which is essential when evaluating whether a wallet’s behavior aligns with expected, human-like usage versus automated bots. This is useful for participants who want to audit their own activity before snapshot or claim windows. (info.etherscan.com)
Accept that many programs publish anti-sybil filters publicly or semi-publicly, but exact weights may remain opaque. Public writeups and checker tools (e.g., Treehouse airdrop checker) illustrate how wallets are evaluated against criteria and how eligibility is communicated to users. (docs.treehouse.finance)
Use this as a learning exercise, not a trigger for speculative behavior. Academic and industry analyses emphasize that airdrops can attract “airdrop farmers” who optimize for claims, which can distort the distribution if not properly guarded. This is a recurring caution in arXiv analyses and reviews of multiple programs. Blockquote: A succinct callout from the literature on sybil and dynamic reward design:
“Sybil filters cut wallets on funding-source clustering and activity compressed into a short window.” — OrcaLayer Research. (orcalayer.com)
B. Executing the Steps
1) Audit your on-chain footprint over time
The design of airdrops rewards signals that are observable on-chain, such as the variety and longevity of activity. Rather than producing a single burst of transactions, strive for a steady, multi-week pattern across different protocols. Public analyses consistently highlight the value of depth and diversity in wallet activity. (passiveblocks.io)Keep a scalable log of your activity: interacting with multiple ecosystems, using a mix of features, and maintaining regular engagement reduces the risk that your wallet looks like a bot or a “farm.” The anti-sybil literature emphasizes that long-horizon and varied engagement patterns tend to fare better in scoring schemas. (arxiv.org)2) Build genuine cross-protocol presence
Programs increasingly reward multi-protocol usage and non-trivial interaction sequences. A wallet that only interacts with a single protocol or executes repeated boilerplate actions is more likely to be filtered. Public analyses of Polymarket’s approach show explicit, publicly documented filtering for the most sybil-prone patterns, including clustering and short-horizon activity windows. (orcalayer.com)As a practice, explore a spectrum of protocol actions (e.g., swaps, liquidity provision, governance participation) spread over weeks rather than concentrated into a single snapshot window. This aligns with observed patterns across several programs and with the user-behavior signals emphasized in air-drop research. (passiveblocks.io)3) Mind your wallet hygiene and identity signals
Some programs use proxy signals that aim to detect “meaningful engagement” rather than cookie-cutter activity. For example, Treehouse uses wallet-level proxies like Nuts balance to reflect engagement depth and excludes certain wallets after sybil screening. Review their public documents and airdrop checker to see how this translates into user-facing eligibility. (docs.treehouse.finance)Prepare for potential post-snapshot adjustments: airdrops can exclude wallets that appear to game the system after initial eligibility checks, based on ongoing auditing and analytics. This pattern appears in multiple program writeups and is a common outcome of anti-sybil measures. 4) Track and verify eligibility proofs before claiming
When a Merkle-tree-based approach is used, eligibility proofs are validated on-chain at claim time. This means you should ensure that your wallet’s leaf in the tree corresponds to your address and that you possess the required proof material. Handshake’s documented flow is a canonical illustration of this approach. (github.com)If your wallet passes the criteria, you’ll typically see an explicit eligibility status in a checker or on a claim portal (e.g., Treehouse’s airdrop checker). These tools help users confirm whether they qualify and what allocation they might expect. (docs.treehouse.finance)5) Learn from concrete examples and keep expectations grounded
Academic and industry analyses show that many airdrops end up with a substantial portion of tokens exiting quickly, as a result of “airdrop farming.” This lens is important for participants—understanding that even legitimate winners may strategically plan around claim windows and markets. (arxiv.org)Real-world tooling demonstrates a spectrum of implementation choices—from explicit anti-sybil filters to multi-asset and multi-week reward schedules. For practitioners, this means there is no universal recipe; you should study the specific criteria of each program and align your participation strategy with the signals that protocol designers publicly emphasize. (passiveblocks.io)6) Use official sources and maintain ethical participation
Rely on official docs and tools rather than secondary analyses if you want to understand the exact steps to eligibility. Treehouse’s public airdrop documentation and the Handshake Merkle-tree narrative are instructive anchors for how credible programs describe the process. (docs.treehouse.finance)Remember to avoid attempting to game mechanics with proxies, centralization, or bot-like behavior. The literature warns about the incentives for “airdrop farming,” and several programs explicitly state their anti-sybil goals and their willingness to disqualify suspicious wallets. Blockquote: A closing reminder from the research community:
“The distribution often rewards legitimate, sustained engagement and penalizes short-lived, bot-like activity.” — Airdrops: Giving Money Away Is Harder Than It Seems.
Closing note: Airdrop eligibility is a dynamic design space where protocol goals, security constraints, and participant behavior intersect. While the exact scoring formulas are frequently not public in full, the public signals, tooling, and case studies available across Handshake, Treehouse, Polymarket, and related analyses give a robust picture of what teams value: sustained, varied, and verifiable on-chain activity balanced with anti-sybil safeguards. By studying these sources and aligning your activity with the documented signals, you can participate in a manner that is both responsible and aligned with how these programs are designed to function. (github.com)
References and Further Reading
Handshake Airdrop: merkle-tree-based redemption and on-chain proofs. https://github.com/handshake-org/hs-airdrop (hs-airdrop README). (github.com)
Treehouse Protocol: Eligibility Criteria and Airdrop Checker, including Nuts balance proxy and sybil screening. (docs.treehouse.finance)
Polymarket Airdrop Criteria and Sybil Filters (OrcaLayer analysis). (orcalayer.com)
Airdrops: What on-chain activity qualifies you (general guidance). (airdrops.io)
Airdrops: Giving Money Away Is Harder Than It Seems (academic analysis of multiple large drops and farming dynamics).
ZAPs: A Reward Attribution Framework for DeFi Ecosystems (robust scoring with anomaly detection). (arxiv.org)
Etherscan: Exploring an EOA address and on-chain activity signals. (info.etherscan.com)
L2BEAT: General FAQ on scaling and data considerations for layer-2 ecosystems (identity, data availability). (l2beat.com)Sources & Factual References
passiveblocks.io
orcalayer.com
github.com
docs.treehouse.finance
arxiv.org
info.etherscan.com
docs.treehouse.finance
arxiv.org
airdrops.io
l2beat.comFurther Reading
Anti-Sybil Detection Techniques Deployed by Project Teams Reshape Airdrop Eligibility in the US Market
A Complete Guide to Farming Airdrops Without Sybil Risk