Guides to Sybil resistance and campaign eligibility
Explore wallet farming, evidence layers, trusted claims, quadratic funding and fair participant review.
Evidence, implementation questions and buying trade-offs for teams evaluating application protection.
Latest guides
Sybil resistance in blockchain: identity, eligibility and consensus
Understand Sybil attacks, resistance and the difference between protecting consensus and limiting repeated campaign participation.
How to detect airdrop wallet farms before allocation
Combine funding graphs, wallet behavior and live device evidence while preserving legitimate new users and shared infrastructure.
Device intelligence vs wallet reputation vs proof of personhood
Compare the evidence, assumptions and user effort of three Sybil-resistance layers before choosing a campaign stack.
Design a Sybil-resistant Merkle claim and eligibility flow
Protect the trusted eligibility and redemption boundary, including wallet binding, direct calls, duplicate use and appeals.
Sybil attacks and collusion in quadratic funding rounds
Separate repeated donor identities from coordination among real people and review eligibility before final matching.
Evaluate Sybil detection without excluding genuine new users
Build independent labels, test sparse-history and shared-device cases and design an appeal path before irreversible allocation.
Explore checkers, demos and evaluation routes →
Summarize this page with
Practical research guides
Protect campaign accounts while preserving participant appeals
Protect campaign signup, login and recovery with named account-risk options, while keeping wallet control, participant eligibility and appeals distinct.
Control reward allocation and repeated promotional claims
Control repeated campaign rewards, trials and referrals with an allocation ledger, account relationships and clear eligibility or appeal evidence.
Evaluate device evidence in participant-uniqueness reviews
Evaluate browser and device evidence for participant relationships, with cookieless recognition, shared-equipment cases and a separate personhood model.
Use network evidence in campaign eligibility without IP exclusions
Use proxy, mobile, relay and location observations in campaign review, preserving provenance and uncertainty instead of excluding shared infrastructure.
Separate Sybil claims from payment, marketplace and traffic fraud
Separate Sybil allocations from payment, marketplace and acquisition fraud, with wallet and device relationships, eligibility records and appeals.
Procure campaign risk evidence and distinguish adjacent intelligence
Compare campaign-risk evidence, vendor outputs and self-serve costs, while distinguishing device, on-chain, asset and public-program intelligence.