A Sybil attack is an attempt to earn outsized rewards by operating many fake identities (wallets, accounts, devices) that pose as independent participants. Anti-Sybil design (wallet reputation, device caps, activation gates, referral caps) is a core requirement for any platform distributing rewards, since undefended pools are reliably drained by Sybil clusters.
An operator creates many identities that appear independent, has each perform the minimum qualifying activity, and collects a share of the reward pool for every one. Where rewards are distributed per participant, controlling a hundred identities returns roughly a hundred times what one does.
By raising the cost per identity rather than trying to prove intent. Wallet reputation pays fresh addresses less. Device and IP caps limit how much one machine earns. Activation gates require real activity before anything pays. Referral caps limit what a cluster can extract from inviting itself.
Because undefended pools are reliably drained. Any reward pool is a standing incentive to attack, so the question is not whether a campaign will be targeted but how much of the pool reaches real participants when it is.
The term comes from computer security, where it describes an attack on distributed systems through forged identities. It predates crypto and applies anywhere a system assumes participants are distinct people.
A Sybil attack is about identity: one operator posing as many independent participants to multiply a share of the pool. Bot activity is about automation: non-human traffic inflating metrics. The two overlap, since Sybil clusters are usually automated, but the defences differ. Identity caps address one, session and traffic analysis the other.
Perfect defence is not the goal, and no platform claims it. The goal is raising the cost per identity until running a cluster stops paying, so the pool reaches enough real participants for the campaign to have been worth running.
An attempt to earn outsized rewards by operating many fake identities, such as wallets, accounts, or devices, that pose as independent participants. Because rewards are typically distributed per participant, controlling many identities multiplies what one operator collects. Anti-Sybil design is a core requirement for any platform distributing rewards, since undefended pools are reliably drained.
Through signals rather than proof of identity: wallet reputation weighting fresh addresses down, device and IP caps, activation gates requiring real activity, referral caps, and anomaly review looking for patterns that independent participants would not produce. No single check is sufficient, which is why platforms layer several and review anomalies on top.
A requirement that a participant complete meaningful activity before rewards, particularly referral rewards, become payable. It defends against Sybil clustering by ensuring that creating an identity costs something more than the act of creating it. Without one, creating an identity costs nothing more than the act of creating it.
Well-designed systems weight rather than block. A fresh wallet typically earns at a reduced rate until it establishes history, rather than being excluded, which keeps genuine newcomers able to participate while raising the cost of running identities at scale. The aim is raising the cost per identity, not proving intent.
