> Smurfs enter brackets twice and dodge bans. Use RestoreCord alt detection, VPN blocking and auto-blacklisting at verification so every player signs up once.

Source: https://restorecord.lol/stop-smurfs-in-tournaments

# How to keep smurf accounts out of Discord tournaments

One player with three accounts can enter three times, dodge a seeding penalty and scout your teams. Here's how to make every bracket one account per person.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)

Short answer

Put registration behind RestoreCord verification, turn on alt detection and VPN blocking with warnings to a staff channel, enable Auto-Blacklist on Ban, then switch to Block Alts once you trust the matches.

## Why smurfs break community brackets

Open tournaments run on trust. Seeding assumes each entrant is who they say they are, prize pools assume one payout per player, and disqualifications assume the player stays out. A smurf breaks all three. Discord itself does nothing to stop it, because an account is free to create and a server invite works for anyone.

The fix is to check the **person** at the moment they register, not the account. That's what verification gives you.

## Step one: gate registration

Make your sign-up and check-in channels visible only to a verified role, and make RestoreCord verification the only way to get that role. Now every account that wants a bracket slot goes through the same checks, at the same door, before it can type a team name.

RestoreCord's Set up verification flow proposes the verify channel and the channels to protect, and only changes Discord permissions once you confirm. Staff and log channels are left alone.

## The signals that catch second accounts

| Check                 | What it stops                                                                       | Plan           |
| --------------------- | ----------------------------------------------------------------------------------- | -------------- |
| Alt detection         | A second account from the same IP or browser fingerprint as an earlier verification | Premium and up |
| Anti VPN and proxy    | Players hiding their real connection to dodge an IP match                           | Premium and up |
| Auto-Blacklist on Ban | A banned player verifying again on the same account                                 | Premium and up |
| Minimum account age   | Accounts registered minutes before sign-ups close                                   | Enterprise     |
| Captcha               | Scripted sign-ups flooding your bracket                                             | Every plan     |

## Decide what a match means

Every match can warn, block or ban. For a first event, send matches as warnings to a private #verify-log channel through webhook logs. Your tournament admins see each match with the signal that triggered it and decide case by case. Once you've seen a full event's worth of matches, switch on **Block Alts** so linked accounts are refused at verification, or **Auto Ban Alts** if your bracket is under active attack.

Bootcamps, LAN venues, siblings and esports clubs share connections. An IP match on its own is a lead. A fingerprint match plus an IP match is much stronger. Review before you disqualify.

## A pre-event checklist

1. 1Publish the verify message in a channel new members can see
2. 2Hide #sign-ups and #check-in from everyone without the verified role
3. 3Turn on alt detection with warnings, plus VPN and proxy blocking
4. 4Point webhook logs at a staff-only channel for tournament admins
5. 5Enable Auto-Blacklist on Ban so disqualifications carry over
6. 6After the event, review every flagged account and decide whether to move to Block Alts

## What verification won't solve

It can't tell that a player borrowed a friend's account on the friend's own machine, and it doesn't police behaviour in matches. Keep your game's anti-cheat and your rulebook for those. What it removes is the easy route, which is the one most smurfs take.

Running tryouts as well? Read [how to lock tryouts behind a password](https://restorecord.lol/password-protected-tryouts). Need several admins reviewing matches? Set up [scoped staff access](https://restorecord.lol/tournament-staff-access), or head back to [RestoreCord Esports](https://restorecord.lol/).

## Smurf-proof your next bracket

1. 1  
### Lock registration behind verification  
Only the verified role can see #sign-ups and #check-in, so every entry passes the same checks.
2. 2  
### Turn on alt detection and VPN blocking  
Start with warnings to a private webhook channel so admins see every match with its context.
3. 3  
### Blacklist disqualified players automatically  
Enable Auto-Blacklist on Ban so a banned player can't verify straight back in on the same account.
4. 4  
### Switch to Block Alts for the next event  
Once matches look right, deny verification to linked accounts before they reach registration.
[Alt detection on restorecord.com](https://restorecord.com/alt-detection)

## Questions about smurf accounts

### 

### 

### 

## Give every player exactly one entry

Add verification to your tournament server and catch second accounts before seeding is locked.

[Get started free](https://restorecord.com/register)[View pricing](https://restorecord.com/pricing)
