Airdrop Reality Check — the honest scanner that admits most farmers are net negative

Most airdrop tools are dishonest by design. They sell you "you're 92% eligible!" and route you to bridges they earn affiliate commissions on — without ever telling you the bridging itself usually costs more in gas than the drop is worth.

I spent the last weeks building one with the opposite philosophy. The headline number on the overview tab isn't your eligibility score. It's the dollar amount you've already spent on gas.

The reality check most tools refuse to surface

I asked 12 friends running multi-wallet airdrop farms to scan their setups. Every single one was net negative on lifetime gas spent versus airdrop USD received. Including the people who got into Hyperliquid early.

The era when bridging once to Arbitrum got you UNI-tier money is over. Three things happened in 2024–2025 that killed the easy retail farming era:

• Sybil filters got aggressive. Berachain wiped 30–60% of farmed wallets at TGE. ZK was similar. Scroll, less drastic but still meaningful.
• Per-wallet allocations shrunk. What used to be $500–$5,000 per wallet is now $30–$300 for most chains.
• Gas got expensive. Mainnet ETH at $3,200+ means every L2 bridge costs $5–15. Multiply by 5 chains × 50 transactions over 6 months.

What this scanner does differently

1. Gas cost reality, in USD, headlined

For every outgoing transaction, the scanner computes gasUsed * gasPrice, multiplies by live native-token prices from CoinGecko, sums across all your wallets and chains. That's the headline number on the overview tab. Most users see a number they're not happy about. That's the point.

2. Pairwise Sybil clustering detection

Protocols increasingly cluster wallets by day-overlap. If your 5 wallets all show activity on the same days — even if you tried to vary transaction types — they look like one farmer. The Berachain TGE filter explicitly used this signal.

The scanner does pairwise comparison: for each pair of wallets, counts shared active days as fraction of the smaller wallet's total. If overlap > 65%, it warns you with the actual day count and recommendation to stagger.

Not a perfect proxy for protocol-side clustering (they also use IP, transfer graph, behavioral fingerprints), but day-overlap is the easiest leak to detect locally and easiest to fix.

3. Pattern-aware scoring, not volume-only

Volume-only scoring is exactly what Sybil farmers optimize for, and exactly what protocols penalize. So I added two multipliers on top of base score:

• Diversity multiplier: unique counterparties / 50, capped at 1.2x
• Consistency multiplier: if activity spread > 30 days, +10%

So 500 transactions to one contract score worse than 200 transactions across 20 contracts. Which matches how actual allocations work.

What's curated for May 2026

Most "famous" airdrops have already happened. Listing them as "active opportunities" would be dishonest. So the protocol list is honestly curated:

S-Tier (genuinely pre-token, real upside)

• Symbiotic — restaking primitive, TGE expected late 2026
• Mira Network — AI output verification layer
• Monad testnet — mainnet not yet launched as of May 2026
• Etherealize — institutional ETH onramp

A-Tier (post-token but live points seasons)

• HyperEVM — Hyperliquid native L1 ecosystem (HypurrFi, HyperLend)
• Berachain S2 — BGT delegation, Infrared / Kodiak vaults
• Sonic S2 — Rings + Beethoven X + SwapX
• Linea S3 — LXP-L farming continues post-LINEA
• Scroll S3 — Marks farming on Ambient / Rho / SyncSwap

Demoted to lower tier (already airdropped — most other tools still list as A-tier)

• HYPE (Nov 2024), BERA (Feb 2025), ZK (Jun 2024), SCR (Oct 2024), MODE (May 2024), S (Dec 2024), INIT (Apr 2025), ES (Oct 2025), MON (likely by mid-2026)

How it's built

The whole thing is a single HTML file:

• React 18 + Babel standalone via unpkg CDN — no build step, no bundler
• 1,500 lines of code, 83KB on the wire
• Deploys to GitHub Pages on git push
• localStorage for API keys + wallet addresses — they literally never reach the server
• CSP locked to explorer endpoints + CoinGecko + email-capture form
• Parallel batched scan (5 in-flight with Promise.allSettled and 429/503 backoff) → 3-wallet × 13-chain scan in ~30 seconds

Why a single HTML file instead of a Next.js app? Trust signal. A tool that handles wallet history should fit in one browser tab and be auditable in 15 minutes. No build step means no opportunity for malicious npm dependencies to slip in.

Honest about monetization

The bridge action items use affiliate-tracked URLs (deBridge, Orbiter, CoinDCX for the India onramp). They're labeled in code, source is public. The scanner stays free forever. No premium tier, no subscription. The closest thing to a paywall is an optional email signup for a weekly newsletter.

What I'd love feedback on

• The Sybil overlap threshold (currently 65%) — too aggressive? Too lax? I picked it from intuition + a few public TGE post-mortems. Empirical calibration would be better.
• The scoring weights per protocol — heuristic. If you've actually been allocated by one of these protocols, your input would improve the calibration.
• Missing protocols — there are several pre-token plays I almost certainly missed. Send names.
• Failure modes — if the scanner shows wrong data for your wallet, I want to know. Privacy is preserved (your data never reaches me) but I'd love a screenshot of the per-criterion breakdown.

Source: github.com/LuciferForge/mcp-directory · Built solo. Single HTML file. Auditable in 15 minutes.