Orca Crypto
Menu
Start Here
Learn
Chains
Exchanges
Markets
Tools
Safety
Glossary
More
Our tokens Book a session
Web3 term

Sybil resistance

Stopping one person from pretending to be thousands.

Loading live prices
All terms
All termsAddressBlockBlock timeBlockchainConfirmationGasGweiHashMempoolNodePrivate keyPublic keySeed phraseTransactionWalletAll time high (ATH)Bear marketBull marketBundlerCandlestickCapitulationChart patternsCliffDollar cost averaging (DCA)Funding rateLeverageLimit orderLiquidationLiquidityMarket capMarket orderOrder bookPerp (perpetual futures)Position sizingPresaleRisk managementSlippageSniperSpreadStealth launchStop lossSupport and resistanceTrendUnlockVestingVolatilityVolumeWhaleAMMBonding curveBridgeBurnCEXDAODeFiDepegDEXFarmingFlash loanGovernance tokenGraduationImpermanent lossLiquidity poolLP (liquidity provider)LP tokenOraclePerpetual (perp)PointsRestakingRWAStablecoinTVLWrapped tokenYield farmingAirdropAlphaAnonApe (to ape in)Ape inBagholderBagsChadCope / copiumCrypto Twitter (CT)DegenDevDiamond handsDiscordExit liquidityFloor priceFOMOFUDGMHODLJeetKOLLARPLoreMaxiMeme coinMoonNFTNGMINo coinerNormiePaper handsPFPRaidRektSerShillSnapshotTelegram (TG)TradFiWAGMIWenAddress poisoningCold storageCustodyDue diligence (DYOR)Dusting attackExit scamFront runningHardware walletHoneypotHot walletMEVMultisigPhishingPump and dumpRug pullSandwich attackSelf custodySIM swapToken approvalTwo factor authenticationWallet drainerWash tradingAccount abstractionAppchainBlock explorerCirculating and total supplyConsensusData availabilityEVMFaucetFinalityForkFully diluted valuation (FDV)Gas warHalvingLayer 1Layer 2Layer 3MainnetMiningName serviceOptimistic rollupProof of stakeProof of workRollupShardingSidechainSlashingSmart contractStakingTestnetToken standardTokenomicsValidatorZero knowledge proofZK rollupArweave and the permawebComposabilityCross chain messagingdAppDecentralized identity (DID)DePINGameFi and play to earnIndexerInteroperabilityIPFSOnchain and offchainSession keysSmart accountSocialFiSoulbound tokenSybil resistanceToken gatingWeb2 vs Web3Web3
By the Orca Crypto teamUpdated 2026-09-28How we check this3 min readDefinition
Definition

Stopping one person from pretending to be thousands.

A Sybil attack is one actor creating many identities to gain disproportionate influence: farming an airdrop with a thousand wallets, swinging a governance vote, or gaming a reputation system.

Because creating a wallet is free and instant, every open system needs some answer to this. Options include proof of personhood, staking capital, reputation history and social graph analysis. None is perfect and all involve a privacy tradeoff.

In practice

Airdrop teams now spend significant effort filtering Sybil farmers, and the filtering regularly catches genuine users too.

What people get wrong

That wallet counts measure people. One person can run thousands of wallets cheaply, which is exactly what airdrop farming is, and most user numbers you see have not been filtered for it. Unique wallets and unique humans are very different figures.

Common questions

Why does it matter if one person has many wallets?
Because airdrops, votes and rewards all assume one participant per share. Without resistance, whoever automates hardest takes most of it.
How do protocols detect sybils?
Funding patterns, timing, identical behavior across wallets and shared endpoints. It works partially. Large airdrops routinely remove thousands of addresses and still miss many more.

Where this comes up on the site

The guides that actually use this word, rather than a list of everything we have written.

Where to go next

More web3 terms

Back to the full encyclopedia

Want this explained out loud?

Some of these land faster in conversation than in writing. Sessions are one to one and you can ask anything, including the things that feel too obvious to ask.

Share this page

Was this page useful?