All systems operationalโ€ขIP pool status
Coronium Mobile Proxies
Airdrop Farming
Sybil Defense
April 2026
Technical Guide

Sybil Defense for Multi-Wallet Airdrop Farming (2026)

LayerZero filtered 803,000 wallets. zkSync Era dropped 60 percent of eligible addresses. Starknet cut 27,000 before distribution. This is how Trusta Labs, Nansen, Bubblemaps, and Chaos Labs actually find Sybils, and how serious farmers build opsec that survives the filter.

803K
LayerZero Sybils filtered
60%
zkSync addresses flagged
27K
Starknet wallets cut
5+
Detection firms in market
Case Studies

Major Sybil Filters of 2024

Four airdrops that publicly filtered hundreds of thousands of Sybil wallets, and what the numbers actually mean for farmers building opsec today.

LayerZero ZRO (June 2024)

The landmark Sybil filter of the cycle

803,000 filtered

The numbers

  • Initial eligible snapshot: ~2.1M wallets
  • Full Sybils excluded: 803,093 wallets (~38 percent)
  • Self-reported Sybils: ~1.3M wallets accepted at 15 percent allocation
  • Final qualified non-Sybil wallets: ~1.28M

Detection stack

  • Trusta Labs: primary ML clustering vendor
  • Nansen: wallet labeling, smart money exclusion
  • Chaos Labs: behavioral simulation
  • Internal LayerZero heuristics on bridge patterns

Key lesson: LayerZero published its criteria openly. Sybil cluster indicators included wallets funded from the same source within 30 days, wallets transacting through the same bridges with similar amounts, and wallets with overlapping transaction timing windows. Every one of these is a defeatable signal with proper opsec.

zkSync Era ZK (June 2024)

The most aggressive Sybil filter to date

~60% excluded

The numbers

  • Initial interaction snapshot: ~6.9M wallets
  • Roughly 60 percent excluded as low-effort or Sybil
  • Final eligible: ~695K wallets received tokens
  • Community pushback was immediate and loud

Detection stack

  • Trusta Labs MEDIA algorithm
  • Activity duration thresholds (30+ days)
  • Minimum USD volume requirements
  • Unique dApp interactions (10+ protocols)

Key lesson: zkSync did not publish full per-wallet Sybil scores. Instead they combined explicit Sybil detection with quality thresholds: a wallet could be excluded for being a Sybil OR for being a genuine low-effort farmer. This dual filter is now standard.

Starknet STRK (February 2024)

Pre-distribution Sybil cut and retroactive adjustment

27,000 cut

The numbers

  • Initial eligible wallets: ~1.3M
  • Pre-distribution Sybil cut: 27,000 wallets
  • Average allocation per eligible: ~1,800 STRK

Detection stack

  • Trusta Labs clustering
  • GitHub developer weighting
  • Bridge volume thresholds

Blast BLAST (June 2024)

Point-based airdrop with Sybil-weighted distribution

Suspicious flagged

Blast took a different approach: instead of binary exclusion, they reduced allocations for wallets flagged as suspicious. Users with clear Sybil indicators received 50 percent or less of their point-accrued share, while obvious farmers (batch-created wallets, identical funding patterns) were zeroed out entirely.

Key lesson: The trend in 2025-2026 is toward graduated penalties rather than binary cuts. A wallet can be partially flagged and receive a reduced allocation, which makes appeals harder and maximizes retained value for the project.

Detection Methodology

How Detection Actually Works

Five core techniques that modern Sybil detection firms combine. Understanding each one is the prerequisite to designing opsec that defeats them.

Technique 1

IP Correlation

Projects correlate wallet addresses with IPs logged by dApp frontends, centralized bridges, and RPC providers. If 200 wallets connected from the same IP or the same /24 subnet, they cluster as one operator.

Real example:
LayerZero Sybil report identified clusters where 50+ wallets shared a single datacenter IP across bridge requests. Entire clusters were zeroed.
Technique 2

Wallet Graph Analysis

Trace funds backward 3-5 hops from airdrop wallets to identify common funding sources. If 40 wallets all trace back to the same Binance withdrawal within 72 hours, they are a cluster.

Real example:
Trusta Labs published clusters with 2,000+ wallets linked by funding. One cluster was funded from a single OKX withdrawal over 6 weeks.
Technique 3

Timing Correlation

Flag wallets that repeatedly transact within the same narrow time window. A 5-minute correlation across 20 actions is a near-zero probability event for independent users.

Real example:
zkSync Era MEDIA flagged wallets executing bridge-swap-lend sequences within 5 minutes of each other repeatedly across 10+ days.
Technique 4

Gas Fingerprinting

Wallet software personalizes gas prices and limits based on user history. Scripts often override with identical values, creating a gas fingerprint that links wallets.

Real example:
Clusters identified where 300 wallets all used identical 25 gwei priority fee on every Arbitrum transaction for 3 months.
Technique 5

Bridging Pattern Analysis

Projects map bridge flows: which source chain, which destination chain, which amounts, which bridge providers. Wallets that all bridge the exact same amount from the exact same chain using the exact same bridge in the same week are obvious clusters.

Real example:
LayerZero internal analysis found clusters where 500+ wallets bridged exactly 0.05 ETH from Ethereum to Arbitrum via Stargate within the same 48-hour window. Entire cluster zeroed.
Detection Vendors

Tools Projects Actually Use

Five firms dominate Sybil detection services in 2026. Knowing their methodology is essential to defending against it.

Trusta Labs

Tier 1 vendor

The dominant airdrop Sybil detection firm. Served LayerZero, zkSync Era, Starknet, Blast, and dozens more. Their MEDIA algorithm combines ML clustering with on-chain identity signals (TrustScore). Proprietary methodology but published whitepapers confirm funding graph analysis, timing correlation, gas fingerprinting, and behavioral clustering are all components.

LayerZero
Primary vendor
zkSync Era
MEDIA algorithm
Starknet
Clustering vendor
Blast
Point weighting

Nansen

Wallet labeling

The wallet analytics standard. Nansen labels 300M+ addresses (CEX hot wallets, whales, smart money, MEV bots, smart contracts, exploited contracts). Projects feed their airdrop candidate list to Nansen and receive cluster reports based on transaction patterns, counterparty overlap, and funding flows. Nansen does not sell Sybil scores per se, but its cluster exports are a core input to many project-side filters.

Priced at enterprise tiers typically $150K+ per engagement for airdrop analysis.

Bubblemaps

Visualization

Bubblemaps renders wallet relationships as literal bubble graphs. Each wallet is a bubble sized by balance, and fund flows between wallets draw connecting lines. Clusters that look like a star with 50 satellites orbiting a single hub are instant Sybil flags. Projects use Bubblemaps both for automated filtering and for manual review of edge cases.

Public tool (bubblemaps.io) available free for basic analysis. Enterprise API for bulk airdrop review.

Chaos Labs

Simulation

Chaos Labs focuses on smart contract and airdrop simulation. They simulate how an airdrop distribution would play out under different Sybil thresholds, showing projects what percentage of TVL retention they can expect at each filter strength. Used by LayerZero and others for pre-launch distribution modeling.

More consulting than direct detection, but their simulations drive which Sybil thresholds projects actually adopt.

ScopeScan

On-chain forensics

ScopeScan provides forensic-grade wallet tracing used increasingly in 2025-2026 for airdrop Sybil review and post-launch dump analysis. Specialty is tracing mixer-obscured flows and identifying clusters that evade simpler graph analysis by using Tornado Cash or cross-chain bridges as intermediaries.

Used by several L2s for post-launch Sybil claw-back where allocations are revoked from clusters identified after distribution.
Signal #1

IP Correlation: The Biggest Sybil Signal

Every detection vendor starts with IP clustering. Understanding how they get the data and how CGNAT mobile IPs defeat it is the single most important opsec concept for farmers.

How projects get your IP

dApp frontend logs:

Every dApp (Uniswap, Stargate, Arbitrum Bridge) logs IP + connected wallet address in its analytics pipeline.

Centralized bridges:

Stargate, Hop, Across, deBridge log source IP of every bridge request for fraud prevention and regulatory compliance.

RPC providers:

Infura, Alchemy, Ankr, QuickNode log API key + IP + every wallet address signed. Some sell anonymized logs.

Project-owned RPC:

Starknet, zkSync, Scroll all run their own RPC endpoints as default. If you used the default endpoint, they have your IP.

Wallet software telemetry:

MetaMask telemetry (on by default) sends IP + wallet data to Consensys infrastructure.

Why mobile CGNAT defeats it

Shared IP pool:

A single AT&T mobile IP is shared by 500-5,000 real subscribers via Carrier-Grade NAT. Any flag would hit thousands of genuine users.

ASN whitelisting:

Detection vendors whitelist AS7018 (AT&T), AS21928 (T-Mobile), AS22394 (Verizon Wireless) because blocking them blocks millions of real users.

Rotation on demand:

Mobile proxies rotate IPs on airplane mode cycles. Each wallet can have a fresh IP when it matters (bridge activity, LP, etc.).

Genuine human cover:

Mobile traffic dominantly is genuine humans browsing. Your farming activity is buried in the background noise.

Geographic diversity:

Different mobile proxies in different cities (NYC, LA, Miami, Chicago) create geographic spread that mirrors a genuine global user base.

The one-IP-per-wallet rule

The non-negotiable foundation of airdrop opsec: every wallet gets its own dedicated mobile proxy with its own carrier ASN and its own rotation cycle. No exceptions. No sharing. No using the same proxy for wallet A one day and wallet B the next.

At scale this means you are running 20, 50, or 200 dedicated mobile proxies. The cost is real, but the math works: even a single successful airdrop (LayerZero at $3.77 per token launch, zkSync at $0.20, Starknet at $2+) covers years of proxy infrastructure for a well-run farm.

Signal #2

Wallet Graph Analysis: Funding Source Tracing

Every wallet that exists was funded from somewhere. Detection firms trace that funding back 3-5 hops looking for common sources.

The naive pattern (gets flagged)

Binance hot wallet
ย ย โ†’ Single withdrawal 5 ETH
ย ย ย ย โ†’ Farmer master wallet
ย ย ย ย ย ย โ†’ 0.05 ETH to wallet 1
ย ย ย ย ย ย โ†’ 0.05 ETH to wallet 2
ย ย ย ย ย ย โ†’ 0.05 ETH to wallet 3
ย ย ย ย ย ย โ†’ ... (100 identical sends)

Every wallet traces back to one master in one hop, with identical amounts and near-simultaneous timestamps. Bubblemaps draws a star. Trusta Labs flags the cluster in 10 minutes.

The safe pattern (survives graph analysis)

Binance w/ KYC1 โ†’ wallet A
Coinbase w/ KYC2 โ†’ wallet B
OKX w/ KYC3 โ†’ wallet C
Kraken w/ KYC4 โ†’ wallet D
P2P Bisq/LocalCoinSwap โ†’ wallet E
DEX swap from pre-existing โ†’ wallet F
(different amounts, different weeks,
ย intermediate dApp activity before farming)

Each wallet traces to a distinct funding source. Amounts vary. Time gaps between funding and farming are weeks not minutes. No master wallet exists to cluster on.

Funding diversity checklist

  • Use 4+ different exchanges for funding. Binance, Coinbase, Kraken, OKX, Bybit, Bitstamp, Gemini each have different hot wallet infrastructure.
  • Mix funding methods: some wallets from CEX withdrawals, some from P2P trades (Bisq, LocalCoinSwap, HodlHodl), some from DEX swaps from pre-existing on-chain balances.
  • Randomize funding amounts: instead of 100 wallets each with 0.05 ETH, use 100 wallets with amounts from 0.02 to 0.15 ETH spread naturally.
  • Insert time gaps: fund a wallet, let it sit 2-4 weeks, do some unrelated activity (a swap, a mint), then begin airdrop farming.
  • Never fund through a master wallet: the single most toxic pattern. If you must consolidate, use mixers (where legal) or CEX round-trips to break the graph.
  • Use chain-native funding where possible: buy USDC on Coinbase, send directly to Base. Buy on OKX, withdraw directly to zkSync. This avoids bridge-based funding graphs.
Signals #3 and #4

Timing and Gas Fingerprints

The two signals that catch scripted farming operations regardless of IP and funding opsec. Randomization is non-optional.

Timing randomization

A 5-minute window correlation across 20 actions makes your cluster statistically obvious. Defeat it with layered randomization.

Micro (action-level)
Delay between each transaction in a wallet: 2-90 minutes, uniform random.
Meso (wallet-level)
Delay between wallets running the same action: 10 minutes to 48 hours, avoid batching.
Macro (week-level)
Only half your wallets active on any given week. Rotate active set to avoid cluster synchronization.
Time-of-day variation
Real users have diurnal activity patterns. Tag each wallet with a preferred "active window" (morning, evening, late night) and stick to it.

Gas fingerprint defenses

Clusters where 300 wallets all used 25 gwei priority fees have been flagged in published reports. Variation is required.

Use different wallet clients
MetaMask, Rabby, Frame, Keplr, Phantom each compute gas differently by default. Vary wallet client across your farm.
Vary priority fees
Some wallets pay market rate, some pay slow tier, some pay aggressive tier. Real users optimize cost differently.
Occasional failed transactions
A wallet that never underprices gas and never has a failed tx looks scripted. Real users fail sometimes.
Vary gas limit overrides
Some wallets use default estimates, some override with 20 percent buffer, some with 50 percent. Pattern variation matters.
Signal #5

Bridging Pattern Defense

For bridge-dependent airdrops (LayerZero, Hop, Across), bridge pattern diversity is critical. This is a separate signal from wallet graph and timing.

What projects map

Source chain distribution
Which chain did the wallet bridge from? All Ethereum? Mix of Ethereum and Arbitrum? Real users use whatever they hold.
Destination chain distribution
Did the wallet bridge to 10 chains over 6 months? Or only to zkSync/Starknet/Base in the month before airdrop?
Bridge provider mix
Stargate only? Or Stargate + Hop + Across + Connext + deBridge? Real users try different bridges.
Amount distribution
Always exactly 0.05 ETH or varied amounts? Exact-round numbers flag scripts; 0.0473 ETH looks like a user.
Round trip frequency
Real users often bridge back. Farmers bridge one-way to farm then exit. Include some round trips.
Time between bridges
10 bridges in 48 hours looks like farming. 10 bridges over 6 months looks like user behavior.

Bridge diversification template

A defensible bridge history for a single wallet across a farming season might look like:

  • Stargate: 3 bridges, varied amounts, varied chains (Arb, Optimism, Base)
  • Hop: 2 bridges, small amounts, Arbitrum only
  • Across: 4 bridges across Ethereum, Optimism, Polygon
  • Native L2 bridge (zkSync portal, Starknet bridge): 2 bridges each
  • deBridge or Connext: 1-2 exotic bridges for variety
  • Total over 6+ months, not 6 weeks
Production Opsec

The Complete Defense Stack

Five layers. Missing any one is a correlation vector that survives everything else. This is what a 2026-grade farm actually runs.

Layer 1: Network Isolation

Critical

One dedicated mobile 4G/5G proxy per wallet. Unique ASN (mix AT&T, T-Mobile, Verizon). Unique carrier. Rotation on demand for IP refresh. Never reuse an IP across wallets. Prefer US mobile carriers for US-facing projects, EU mobile for EU projects.

Typical cost: $95-110 per month per proxy at Coronium. Amortized over successful airdrops, under 1 percent of allocation value.

Layer 2: Browser Identity

Critical

Antidetect browser with unique fingerprint per wallet profile. Options: Multilogin ($99/month), GoLogin ($24/month entry), AdsPower (free tier available), Dolphin Anty ($89/month). Each profile ships a unique Canvas, WebGL, audio, and font fingerprint and ties it to the profile's proxy.

Never use the same browser profile for two wallets. Never use a fresh Chrome install without antidetect-level randomization.

Layer 3: Funding Diversity

Critical

Fund each wallet from a different source. 4+ CEXs in rotation. Mix of P2P trades (Bisq, LocalCoinSwap), DEX swaps from pre-existing balances, and occasional intermediate wallet trips to break graphs. Time gaps of 2-4 weeks between funding and first airdrop-targeted activity.

Never fund 50+ wallets from a single master. Never batch-withdraw identical amounts.

Layer 4: Behavioral Randomization

Critical

Randomized timing at micro, meso, and macro scales. Varied gas prices (mix of market, slow, aggressive). Different wallet clients (MetaMask, Rabby, Frame). Different bridging patterns (Stargate + Hop + Across + native). Different amounts. Different dApps visited beyond just airdrop farming.

Scripting is fine, but the script must emit randomized output. Never use a cron job that fires identical transactions from 50 wallets at 6 AM every Sunday.

Layer 5: Long-Tail Activity

Advanced

Wallets that only interact with airdrop-eligible protocols look like farmers. Defensive wallets have genuine-looking holding periods, occasional losses, NFT mints, governance votes, Lens/Farcaster activity, random Uniswap trades. Multi-chain presence (Ethereum, Solana, Cosmos) strengthens legitimacy.

This is the layer most farmers skip. It is also the layer that separates surviving 100 percent of airdrops from being filtered 40 percent of the time.

The compounding rule

A single correlation vector exposes the whole farm. If your 50 wallets pass IP, pass funding graph, pass timing, pass gas, but all bridge through Stargate on the same day with the same amount, that single signal kills everything. Every layer must hold.

The Compromise

The Self-Reporting Option

LayerZero pioneered it: self-report as a Sybil for a guaranteed 15 percent allocation instead of gambling on 100 percent or 0 percent. The math is non-trivial.

The LayerZero program (May 2024)

Farmers who self-identified as Sybils before the snapshot received 15 percent of their initial allocation. The remaining 85 percent was redistributed to non-Sybil users. Approximately 1.3 million wallets self-reported and were accepted at reduced allocation. An additional 803K were flagged post-snapshot by detection and zeroed.

Best case (passed filter)
100%
Full allocation received
Self-report
15%
Guaranteed reduced
Worst case (flagged)
0%
Zeroed allocation

Stay silent if:

  • Each wallet has unique dedicated mobile proxy
  • Funding graph has no common parent within 5 hops
  • Antidetect browser profiles are unique per wallet
  • Timing and gas are randomized
  • Bridging patterns are diversified
  • Wallets have long-tail legitimate activity

Expected value of staying silent: 85 percent pass rate ร— 100 percent = 85 percent. Versus self-report at 15 percent. Silent wins ~6ร—.

Self-report if:

  • Wallets share a single residential or datacenter IP
  • Funded from single CEX withdrawal to master wallet
  • Copy-paste transaction patterns across wallets
  • Batch-created wallets with identical timestamps
  • Same gas price used across all wallets
  • Zero long-tail activity (airdrop protocols only)

Expected value of staying silent: 10 percent pass rate ร— 100 percent = 10 percent. Versus self-report at 15 percent. Self-report wins.

Why projects include self-report

Self-report is economically rational for projects. It pulls farmers off the 0 percent boundary at 15 percent cost, but in exchange the project gets a clean training set for its detection models. Every self-reported wallet is a labeled positive example that improves Sybil detection for the next airdrop.

This is why self-report is increasingly common in 2025-2026. Expect LayerZero-style programs to become standard. Decide your threshold in advance.

Premium Mobile Proxy Pricing

Configure & Buy Mobile Proxies

Select from 10+ countries with real mobile carrier IPs and flexible billing options

Choose Billing Period

Select the billing cycle that works best for you

SELECT LOCATION

๐Ÿ‡บ๐Ÿ‡ธ
USA
$129/m
HOT
๐Ÿ‡ฌ๐Ÿ‡ง
UK
$97/m
HOT
๐Ÿ‡ซ๐Ÿ‡ท
France
$79/m
๐Ÿ‡ฉ๐Ÿ‡ช
Germany
$89/m
๐Ÿ‡ช๐Ÿ‡ธ
Spain
$96/m
๐Ÿ‡ณ๐Ÿ‡ฑ
Netherlands
$79/m
๐Ÿ‡ฆ๐Ÿ‡บ
Australia
$119/m
๐Ÿ‡ฎ๐Ÿ‡น
Italy
$127/m
๐Ÿ‡ง๐Ÿ‡ท
Brazil
$99/m
๐Ÿ‡จ๐Ÿ‡ฆ
Canada
$159/m
๐Ÿ‡ต๐Ÿ‡ฑ
Poland
$69/m
๐Ÿ‡ฎ๐Ÿ‡ช
Ireland
$59/m
๐Ÿ‡ฑ๐Ÿ‡น
Lithuania
$59/m
๐Ÿ‡ต๐Ÿ‡น
Portugal
$89/m
๐Ÿ‡ท๐Ÿ‡ด
Romania
$49/m
SALE
๐Ÿ‡บ๐Ÿ‡ฆ
Ukraine
$27/m
SALE
๐Ÿ‡ฌ๐Ÿ‡ช
Georgia
$69/m
SALE
๐Ÿ‡น๐Ÿ‡ญ
Thailand
$59/m
SALE
Save up to 10%

when you order 5+ proxy ports

Carrier & Region

USA ๐Ÿ‡บ๐Ÿ‡ธ

Available regions:

Florida
New York

Included Features

Dedicated Device
Real Mobile IP
10-100 Mbps Speed
Unlimited Data
ORDER SUMMARY

๐Ÿ‡บ๐Ÿ‡ธUSA Configuration

AT&T โ€ข Florida โ€ข Monthly Plan

Your price:

$129

/month

Unlimited Bandwidth

No commitment โ€ข Cancel anytime โ€ข Purchase guide

Money-back guarantee if not satisfied

Perfect For

Multi-account management
Web scraping without blocks
Geo-specific content access
Social media automation
500+Active Users
10+Countries
95%+Trust Score
20h/dSupport

Popular Proxy Locations

United Statesโ€ขCaliforniaโ€ขLos Angelesโ€ขNew Yorkโ€ขNYC

Secure payment methods accepted: Credit Card, PayPal, Bitcoin, and more. 2 free modem replacements per 24h.

FAQ

Frequently Asked Questions

Straight answers on Sybil detection, opsec economics, and 2026 best practices.

Mobile Proxies Built for Airdrop Farming

One Wallet. One Mobile IP. Zero Correlation.

Dedicated 4G/5G mobile proxies across AT&T, T-Mobile, and Verizon. Unique carrier ASN per proxy. CGNAT shielding that defeats IP correlation. Built specifically for the opsec requirements of modern airdrop farming.

Unique ASN
Per proxy, per wallet
IP Rotation
On-demand refresh
CGNAT Cover
Thousands of real users