Fair Discord giveaways, one ticket per human.
Your giveaway bot is good at picking winners and blind to the fact that six entrants share one browser. RestoreCord checks every account at verification, so only real, separate members ever hold the role that lets them press Enter.
Verification and captcha are free. Alt detection starts at Premium, €5 a month.
#giveaways
Your giveaway bot runs the draw as usual
Confetti BotAPPToday at 18:00
@everyone the summer drop is live!
Summer drop: 3 game keys
Press Enter to join. Entries need the Verified role, and duplicate accounts are removed before the draw.
Required role
@Verified
Winners
3
One person, one ticket
Who got a ticket
RestoreCord verification feed, last 20 minutes
maple.sketch verified
No earlier account, Verified role given
maple.sketch2 blocked
Same browser fingerprint as maple.sketch
orbit_fox verified
Passed captcha, Verified role given
quietkoi blocked
Proxy connection at verification
jun.bakes verified
Same Wi-Fi as a member, logged as a warning
The door your giveaway bot doesn't have
Leave the draw to the bot you already use. RestoreCord decides who earns a ticket in the first place.
Duplicate accounts caught before they enter
Each new verification is compared by IP address and browser fingerprint with everyone who verified in your server before. A match can warn staff, block the role or ban the account, and the Blocked Log Embed tells you which signal fired.
Why entrants were turned away
Example breakdown for one weekend draw
Blocked at verification
Matched an earlier account
AltVPN or proxy connection
VPNNever finished the captcha
CaptchaCaptcha on the Free plan
Scripted account farms stall at a challenge long before they reach your entry role.
No connection hopping
Anti VPN & Proxy on Premium stops one entrant from cycling IPs to look like a crowd.
Brand-new accounts wait
Enterprise sets a minimum Discord account age, so accounts made for today's prize can't verify yet.
Invite contests where the leaderboard tells the truth
Trackers count joins through a link. RestoreCord tells you which of those joins are separate people, so a contestant's own spare accounts fall off their total on their own.
- Self-invites from the inviter's own browser show up as alt matches
- Invitees blocked at verification never get the role, so they can't count
- Every verified invitee is a member you can pull back later
Invite contest: rowan_02
Tracker count versus what RestoreCord let through
- Joins through the link
- 14
- Verified, no match
- 9
- Blocked as rowan_02's alts
- 4
- Blocked for VPN
- 1
- Counts toward the prize
- 9
Which plan covers which kind of giveaway
Every row comes from RestoreCord's plan list. Most weekly key drops are fine on Premium; collabs and stream codes need the higher tiers.
| Free | Premium | Business | Enterprise | |
|---|---|---|---|---|
| Price per month | €0 | €5 | €10 | €20 |
| Verification and captcha | ||||
| Webhook logs of blocked entrants | Advanced | Advanced+ | ||
| Alt detection | — | |||
| Anti VPN & Proxy | — | |||
| Firewall rules (country, IP, username and more) | — | |||
| Partner-server membership rules | — | — | ||
| Auto kick if verification isn't finished | — | — | ||
| Minimum account age | — | — | — | |
| Verification passwords with roles | — | — | — |
Event night checklist
Run through this the day before a big prize goes live. Unticked items are the ones hosts forget most.
Verified role is the entry requirement
Set it in the giveaway bot before you announce, not after the first wave of entries.
Captcha is switched on
Free on every plan, and the cheapest way to slow a scripted farm.
Fresh server snapshot saved
A big prize pulls in trolls too. With a recent snapshot, a mid-event raid is a restore.
Alt matches set to block, not ban
Blocking keeps duplicates out without banning siblings who share a router.
Staff log channel is private
Blocked Log Embeds include the matched accounts, so keep them out of public view.
Rules line in the announcement
Say that duplicate accounts are removed. Most farmers give up before they start.
Set it up once, every draw benefits
Three steps in the RestoreCord dashboard and your giveaway bot.
Connect your server
Add your bot and server in the RestoreCord dashboard and publish the verification message to your verify channel.
Make verified the entry ticket
In your giveaway bot, require the role RestoreCord hands out after a member passes verification.
Tune the duplicate filters
Switch on captcha, then decide whether alt matches warn your staff, block verification or ban the account.
Giveaway hosts ask us
Give the prize to someone who earned it
Collab drops, stream codes, invite races or a plain weekly key: put RestoreCord in front and every ticket belongs to a different person.