Updated September 2026
Reward people for completing an action and some participants will optimise for the reward rather than the intended behaviour.
Web3 quest campaigns are no exception.
Bots, duplicate accounts and Sybil farming can inflate participation figures and make a campaign appear more successful than it really was.
The solution is not simply to make quests harder.
It is to design campaigns where meaningful behaviour is progressively more valuable than superficial activity.
What does Sybil farming mean?
In Web3, a Sybil participant generally refers to one person controlling multiple identities, accounts or wallets.
Imagine a campaign rewarding every wallet that completes a transaction.
One genuine participant might use one wallet.
Another person might create or control dozens.
Looking only at wallet addresses could make the second participant appear to be dozens of separate users.
This creates an obvious problem for campaign measurement.
Wallets are not necessarily the same thing as people.
Why quest campaigns attract farming
Quest campaigns often introduce incentives.
Those incentives might include:
- points;
- XP;
- tokens;
- NFTs;
- allowlist positions;
- rankings;
- eligibility for future rewards.
Incentives can be useful because they provide a reason to explore something new.
But they also change participant behaviour.
As soon as a reward has measurable value, some users begin asking:
What is the minimum action required to receive it?
If the campaign only measures completion, optimisation around the minimum requirement can quickly distort the results.
The completion problem
Consider two users.
Participant A:
Discovers the protocol, reads about it, connects a wallet, uses two product features and returns several days later.
Participant B:
Completes only the minimum qualifying transaction and never interacts again.
Both may technically appear as:
1 completed participant.
But the quality of those two participants is clearly different.
Now imagine Participant B repeating that minimum behaviour across twenty wallets.
A headline participation figure becomes even less useful.
This is why campaign measurement needs to move beyond binary completion.
Verification helps — but verification alone is not enough
On-chain verification is useful because it can establish whether an eligible blockchain action actually occurred.
That is substantially stronger than relying entirely on self-reported completion.
But a valid transaction proves a transaction occurred.
It does not prove:
- that every wallet represents a separate person;
- that the participant understood the product;
- that they will use it again;
- that they generated meaningful economic activity;
- or that the campaign created retention.
Verification therefore needs to sit inside a wider measurement framework.
Measure patterns rather than isolated actions
One way to improve campaign quality is to evaluate sequences of behaviour.
Instead of asking users to complete one qualifying transaction, a campaign can introduce progression.
For example:
Learn → Verify → Use Feature A → Unlock Feature B → Return → Complete Final Challenge
The more varied and sequential the behaviour becomes, the harder it is for simple farming activity to resemble genuine exploration.
More importantly, it gives the project better information.
The campaign can see where participation deepens and where it stops.
Progressive quest design changes the economics of farming
Low-effort actions are naturally easier to farm.
A follow can be automated.
A simple wallet connection can be repeated.
Even individual blockchain transactions can be reproduced.
But campaigns can increase the informational value of participation by requiring combinations of meaningful activity.
That does not mean creating unnecessary friction.
The objective is to make campaign progression correspond with actual product exploration.
Good difficulty comes from genuine engagement.
Bad difficulty comes from making users jump through arbitrary hoops.
XP can provide another behavioural signal
XP systems allow different actions to carry different weights.
Instead of treating every participant identically, a campaign can recognise the depth of their journey.
A participant who completes introductory tasks might earn a small amount of XP.
Someone progressing through multiple verified stages may earn considerably more.
This creates a richer representation of campaign engagement than a single completion flag.
XP itself does not solve Sybil behaviour.
But when XP reflects verified and progressively meaningful actions, it becomes another useful layer in understanding participant quality.
Look beyond the campaign window
One of the strongest signals arrives after the initial incentive.
Did participants come back?
Did they continue interacting?
Did they explore another part of the ecosystem?
Did previously activated wallets become repeat users?
A campaign dominated by incentive farming may generate an impressive launch spike followed by an equally dramatic collapse.
Retention analysis helps separate temporary activity from behaviour that continues.
There is no perfect anti-Sybil metric
Projects should be cautious about claims that a single technology can perfectly identify one human behind every wallet.
Different verification systems provide different signals and involve different trade-offs.
For campaign teams, the practical approach is often to combine signals:
- verified activity;
- behavioural depth;
- wallet history where appropriate;
- progression;
- repeat participation;
- campaign-specific eligibility criteria;
- and relevant humanity or identity signals where available.
The objective is not necessarily to determine someone’s identity.
It is to improve confidence that campaign results represent meaningful participation.
Better campaigns produce better data
Sybil resistance is often treated as a security problem.
For marketers, it is also a measurement problem.
If campaign activity cannot distinguish shallow farming from deeper participation, acquisition figures become less useful.
This is why the structure of the campaign matters so much.
A well-designed Web3 quest campaign should make it possible to analyse:
who entered → what they completed → what was verified → how deeply they progressed → whether they returned.
The result is not perfect certainty about every user.
It is something more practical:
better evidence about the quality of the behaviour the campaign generated.