How to avoid being witched when taking airdrops

ARB will be launched on March 16, 2023. It was supposed to be a happy day, but there was a lot of wailing on all the major social platforms. The airdrop that everyone had been looking forward to turned out to be a waste of time. Even big names like Hebi and IceFrog have been witched. When everyone was venting, I took the cases of my friends who were counter-swept and referred to them. I figured out how to prevent accounts from being witched? The following behaviors are REDFLAG (witch)

1. Asset collection

In the project's documents, if there are multiple accounts, any act of aggregating the assets of the accounts into one account will be classified as a suspicious account and excluded.

2. Single protocol B

In the case presented by the project party, there are multiple accounts, which use a parent account to directly distribute coins to multiple wallets. This behavior is highly recognizable and can be easily identified as a wooling account.

3. Transfer between multiple accounts

Referring to the last point in the project plan example, he agrees that a person has multiple accounts, but if he frequently interacts with more than 5 accounts, they are most likely accounts for stealing, so the number of wallets that frequently interact with each other should be kept within three.
Note: (It is best if there is no connection between wallets), this situation is likely to occur if there is crossover.

4. Provide low-cost packaged interactions

In the ARB airdrop case, we can find that the project has divided the airdrop objects into different amounts by exchanging BNB for WBNB and ETH for WETH. If the amount of interaction does not meet the requirement, the number of airdrop tokens will be greatly discounted.

5. Too few interactions

How can the total number of interactions of a wallet be less than 50? Although there may be only a few interactions with the project party, in order to prove that the wallet is used by real people, it is still necessary to maintain a certain level of activity, which is commonly known as account maintenance. (There are interactions with multiple projects, and there are also some interactions outside of daily hair.)

6. Single interaction

Some friends may use each wallet only for specific interactions for the sake of convenience, but this will be considered by the project party as having no normal transaction records and cannot be regarded as a real user. Referring to the previous point, it is too deliberate to behave like a real person.

7. Too little wallet assets

They are all players in the circle, and the money in each wallet is very low. How can it be considered a valid wallet?

8. Do small project transactions

This type of transaction may be considered as filtering, so the project party selects transactions with large volume – accounts with a total transaction amount of more than 1,000 or more

9. Cram at the Last Minute
Many project parties have snapshots in advance, one month before the airdrop, etc. So it is recommended to be cautious if you cram for the last minute. Although some group members said that they cram for 2 days, it is purely luck. Many will be directly excluded.

10. Multiple accounts with the same IP

IP is the difficulty of airdrops, and it is also the most important thing. The project owner can find all the accounts under the same IP at once, and if they are found, the whole army will be annihilated.

How to avoid being a witch???

1. Do not distribute/collect funds on the chain, use exchanges instead

Avoiding the association between wallets is the most important thing. Compared with using methods such as obfuscation to cover up the transfer relationship between wallets, cex is the best solution.

20 sub-accounts. That is to say, if you open an OKX account, you can have up to 21*20=420 different deposit addresses.

2. Avoid short-term concentrated batch operations and achieve randomization of operations

The so-called randomization includes two aspects:

• Interaction : randomization of interaction time; randomization of interaction amount; randomization of interaction route
• Wallet : randomization of wallet creation time; randomization of fund transfers; randomization of ENS names

3. Prepare multiple IPs or virtual machines

At present, risk control is also being upgraded, and IP behavior may also be recorded. Therefore, it is best to consider using multiple IPs for one wallet, and fingerprint browsers can be considered. It is best to use a static IP. Dynamic and shared IPs are unstable, and can be used by multiple people, making them easy to be targeted.

4. In-depth use

The project party considers multiple factors when issuing airdrops, including the total number of deliveries, the amount delivered, and the types of cross-chains, etc. Therefore, the interaction must be comprehensive and not too single. This situation will occur if the interaction is too single.