To start with, we need to understand what the word Sybil means... Sybil is a group of connected wallets doing activities in an attempt to receive airdrops.
There's two ways wallets can become linked together, on-chain and by metrics.
Think of Sybil detection as the connection between wallets, anything that can be used to identify a group of your wallets could be used against you.
How to avoid being a Sybil:
This guide below will show you the optimal approach to avoid being detected as Sybil using DropBeast.
How many wallets do you farm?
The more wallets the higher the risk.
It is essential to treat each wallet as unique in your strategy, otherwise, all of your wallets may get detected.
When did you fund your wallets?
Optimal:
Different days
Different times
Different amounts ($50, $100, $200 etc)
How did you fund your wallets?
Optimal:
Multiple CEX's
Multiple Apps such as SimpleSwap & HoudiniSwap
Ensure that the 'from address' is unique each time when funding wallets
What transactions did you complete before airdrop farming?
Optimal:
Wallet has been active for an extended period of time
Wallet has used other applications & chains (Real activity)
Wallet has activity that appears to be a real person
Each wallet is unique in it's activity
When was the first airdrop-related transaction made?
Optimal:
Different days
Different times
Have these wallets ever interacted?
Optimal:
Never send funds between farming wallets
Never interact
Have you withdrawn assets?
Optimal:
Repeat the funding process when withdrawing, multiple CEX's & Apps
Never send funds all to the same place
Have you completed KYC with any wallets?
Optimal:
One, or less of your wallets should have any KYC links.
This includes CEX's when you are withdrawing to your wallets.
This can also include Twitter & Discord Connections.
How unique are these wallets overall?
Optimal:
Wallets are highly diversified in their activity
Wallets are highly diversified in their funding
Wallets don't have an overlap of activity
Wallets have diversified metrics throughout the lifespan of the wallet
Is IP Detection a Concern?
All transactions that go through the ZkSync RPC End Point have their IP exposed directly to ZkSync.
This may or may not be a concern, depending on your risk portfolio, settings, and the attention of ZkSync.
It can be argued, that DropBeast will act as a human, therefore, even if IP is tracked there is less chance of becoming detected. At this stage, we don't provide Ankr support which would help mask your IP from ZkSync but it is on the roadmap.
We believe it's a lower priority (unless the community tells us otherwise using the feedback form) as ZkSync a) hopefully cannot detect we're using bots and b) they would delete 80%+ of their activity if they removed wallets from the same.
This may or may not be proof of the above:
https://twitter.com/anthonykrose/status/1685447041537937409
