How to deter bots from entering
How to configure your PREMINT project to reduce bots
Require a minimum wallet balance PREMINT allows you to require that the user has a certain balance in their wallet during registration. We also check to make sure that the balance is maintained between the time they register and the mint date.
Effectiveness: Very high
How to set: When setting up a project, add a minimum balance requirement (Project settings > Registration flow > Required ETH balance). This need not be related to your mint price. We recommend using a minimum balance of 0.3 eth or higher even for free mints.
Why this works: Bots tend to register for a list, then send the ETH to a new address, register again, etc… By requiring that every wallet maintains the balance, bots will need significantly more currency to use.
Require users to own a token (NFT or POAP) PREMINT lets you require that users connects a wallet that holds specific assets from a contract. All you need to do is enter the contract information into PREMINT and we’ll check on registration if the user owns the NFT.
Effectiveness: Very high
How to set: When setting up a project, add discord requirements (Project settings > Registration flow > Require user to own an NFT from specific collections).
Why this works: Bots will need to buy an NFT for every entry they want, because we check to make sure the user keeps the NFT in that wallet after entering. If we find that the token is re-used for a different entry, we will disqualify the original entry.
Require users to have a NFT-gated role in your Discord server Sometimes you want to verify a user owns an NFT, but you don’t want to ask them to connect their wallet. Typically, that’s done by using Discord roles.PREMINT lets you require that users have a specific role in your Discord server in order to register. Using tools like Vulcan, you can have those roles assigned only if users have a specific NFT.
Effectiveness: Very high
How to set: When setting up a project, add discord requirements (Project settings > Registration flow > Discord verification and a couple of settings just below it).
Why this works: This is very hard for bots to get around because they need to verify with the NFT, and typically these tools will remove the role if the NFT is it leaves the bot’s wallet.
Require users to have a CAPTCHA-role in your Discord server Instead of gating your signup with a token-gated role (because maybe you don’t have a token yet), you can gate with a role that the user had to pass a CAPTCHA experience to get. You can install a bot like Vulcan, Server Supervisor, or Pandez Guard. Note: "React to get role" bots aren't helpful and a ton of other captcha bots can be bypassed easily.
Effectiveness: High
How to set: When setting up a project, add discord requirements (Project settings > Registration flow > Discord verification and a couple of settings just below it). Please ensure that this role is assigned to your users by a strong captcha bot.
Why this works: Bots find it easy to join discord servers, add emojis (for roles) or solve some types of captchas. But most still can’t solve complex or multi-step captchas.
Require a user has joined your Discord server by a certain date If you want to reward your existing community and only give them access to an allowlist, then the best way to do it is require that they were a part of your server by a specific date.
Effectiveness: Very high.
How to set: When setting up a project, add discord requirements (Project settings > Registration flow > Discord > Require user joined your server by a certain date
Why this works: Bots can’t time travel. If they weren’t already in your server, they can’t get access. If you’re a new project, this might not be a possibility but for established communities looking to do a new giveaway, it’s rock solid (anecdote: This is how VeeFriends Series 2 stopped their PREMINT from being botted).
Set Twitter account filters Botters spend lots of money buying unused Twitter accounts. The cheapest accounts are the ones that are pretty bare: no followers, no tweets, etc… You can set your project to disqualify any Twitter account that has less than a certain amount of followers, or was created on a recent date.
Effectiveness: Medium.
How to set: Require that users connect their Twitter account, and then set the filters before launching the raffle here ____. You can also use these metrics to clean the list after people have joined.
Why this works: Accounts with incredibly low Followers are probably mostly not real people. This is a blunt tool, but can be used to trim lots of bad accounts.
Require users to follow you on Twitter Following users on Twitter is quite easy for bots but the way allowlist botters use it is against Twitter’s terms of use. Twitter usually detects this behavior and suspends these accounts but unfortunately for creators, by this time the user would have registered for the allowlist. As a result, this is not as effective as previous measures, but this can still yield good results.
Effectiveness: Low.
How to set: When setting up a project, add Discord requirements (Project settings > Registration flow > Twitter verification and the setting just below it). Please ensure that this role is assigned to your users by a strong captcha bot.
Why this works: This makes it harder for botters to retain active accounts making it difficult for them to register for your project as well as others.
Collabs Projects often offer their allowlist spots to different high quality projects. This results in a win-win situation as your project would be exposed to a wider user base and holders of the other project would get allowlist spots for a promising project.
Effectiveness: High
How to set: When You will see a button called “Collabs” on the left hand side of your project dashboard in PREMINT. You can create a collab with any of the projects mentioned in the short list on that page or click on “Create new” on top right of the page and enter the other project’s OpenSea slug.
Why this works: Holders of high quality collections usually avoid transferring and reusing their NFT for allowlists or splitting their holdings across multiple wallets as this is often explicitly disallowed by projects. Because of this, this method is quite effective and we strongly recommend offering allowlist spots to as many high quality projects as you can.
Note: While there are different types of collabs (owning an NFT, being a member on a discord, following someone on Twitter), PREMINT only supports the first type currently.
PREMINT’s “Remove bots” tools
We often saw creators downloading their user list and performing some cleanup in Excel and disqualifying users. We found out that most of these cleanup activities involved filtering users by the frequency of IP address use, number of Twitter followers, the age of Twitter account etc. So we added this feature to allow them to perform these within PREMINT. This is a reasonably new feature and we will add more levers for creators to disqualify bots or low quality users.However, please note that unlike previous steps, this feature comes in plan only after a user has registered for your list.
Effectiveness: Very high
How to set: You can access this from Entry List > Remove bots from your project dashboard. You can change the settings to control which users are disqualified and remove them. Or you can hit the “Reset disqualified” link to reset the disqualified flag from users.
Why this works: This gives the creator the option to spot check their registration list for any suspect pattern and then precisely target the kind of users they wish.
Last updated