How to stop hackathon promo credits being claimed twice
One public code, credits gone by Sunday and half the room locked out. Why hackathon promo codes get claimed twice and which basic fixes break.
"Our nightly embedding run normally takes 40 minutes. We kicked it off last night and it still hasn't started. We pay you $1,200 a month so we don't have to babysit this, and two of our own customers are now asking why their search results are a day old. Did something change over the weekend? I need to know today whether to move this job somewhere else."
That lands in your inbox at 7:20 a.m. on a Monday. It's a scenario, and so is the rest of this section. Rerun the arithmetic with your own numbers.
Say you run a GPU API. Developers send you inference and fine-tuning jobs, you rent the GPUs, and you charge by the GPU-hour. Assume you charge $5 and pay $3. This weekend you sponsored a 48-hour hackathon, Friday 9 p.m. to Sunday 9 p.m., with 120 registered builders and $100 in credits each. To spare the organizer a spreadsheet, you made one code, BUILD100, limited to one redemption per account and 160 in total so walk-ins had room. It was a sensible setup. One claim is worth:
- $100 of credits ÷ $5 = 20 GPU-hours
- 20 GPU-hours × $3 = $60 in rented GPU time
Assume a builder spends about $25 of credits in a weekend. That's 5 GPU-hours, or $15 to you, so you budgeted 120 × $15 = $1,800.
The organizer pinned the code in the event's public Discord at kickoff, and by 11 p.m. a screenshot was sitting in a GPU deals channel. Most teams spend Friday night arguing about what to build, so they don't touch a GPU until Saturday. At 10:40 a.m. on Saturday the 160th redemption went through. Only 60 of those 160 belong to people on your roster, and that's hackathon promo credits abuse at its most expensive: the reward has already gone out, and the people you built the program for are the ones left without it.
The other 60 builders type the code at their tables and read "This code has reached its limit" under a banner with your logo on it. Then the organizer messages you: "Half the room can't use your credits."
An illustrative version of that weekend:
The 100 outside accounts don't stop at $25. They queue batch jobs until the balance reads zero, and by Sunday night it does. In the email list you find nine addresses that are one Gmail inbox with the dots moved around, which is 9 × $60 = $540 to a single mailbox. The other 91 give you nothing to go on.
- 100 outside accounts × $60 = $6,000
- 60 builders × $15 = $900
- Total: $6,900 against a budget of $1,800, nearly four times what you planned
You can't pull any of it back. The GPU-hours are used, the fine-tuned weights have been downloaded, and your provider bills you either way. If paying customers keep 20 GPUs busy around the clock, a 730-hour month brings in $73,000 and costs $43,800 to rent, leaving $29,200. That $6,000 is about a fifth of a month's gross profit, gone in one weekend.
Now to that customer. Say your provider lets you run 50 GPUs:
- Available: 50 GPUs × 48 hours = 2,400 GPU-hours
- Wanted: 2,000 by outside accounts (100 × 20) + 960 by paying customers (20 × 48) + 300 by builders (60 × 5) = 3,260
- Shortfall: 860 GPU-hours ÷ 50 GPUs = 17.2 hours of backlog by Sunday night
So the $1,200 customer waits behind jobs from people who've never paid you, and the builders with credits watched their demo jobs sit in the same line. You also still owe the organizer an answer, and each option is bad. Raise the cap by 60 with the code still public, and you've put another 60 × $60 = $3,600 at risk. Leave it, and you've paid to have 60 developers form their first opinion of your product from an error message. The organizer's already asked if you're in for the spring event.
Why hackathon promo codes get claimed twice
A hackathon code has to reach a whole room in minutes, so it goes wherever everyone can see it. Anyone who can read that channel can use the code.
A $100 code is also worth twenty $5 signup bonuses, and it turns into GPU time the moment it lands. By the time anybody looks at a report, the weekend's over.
Most real builders show up as brand new accounts, signing up at an odd hour and running heavy jobs straight away. On any other weekend that would look strange. During an event, it's exactly what you asked for.
The obvious fix is the one you'd already made, a limit per account and a cap on the total. They just count accounts, and accounts are free to make:
The cap also turns redemption into a race, and the people who win are the ones who saw the code first.
How to cut hackathon promo credits abuse yourself
Start with the program, because these changes make a leak cost less.
Give every builder their own code. One single-use code per roster row, sent to the registered address. A screenshot now costs you one claim, where it used to cost 160. It breaks on walk-ins and on teams that registered as one row. There's more in single-use or multi-use promo codes.
Tie each code to the roster email. Reposted codes stop working. It refuses anyone who signed up with a different address from the one they registered with. And if registration is open to anyone online, the roster proves very little.
Split the reward. Give $20 on redemption and $80 when the team submits a project. An outside claim now costs you 4 GPU-hours × $3 = $12 up front instead of $60. A builder who needs a big training run on Saturday has to come and ask, and an empty submission still unlocks the $80.
Give promo credits their own GPU pool. Cap promo jobs at 15 of your 50 GPUs and run paying jobs first. The most the weekend can cost is 15 × 48 × $3 = $2,160, and 720 GPU-hours still covers 120 builders at 5 hours each. This protects the customer at the top, but it doesn't stop a single claim, so builders share those 15 GPUs with everyone who got in first. A hard spending cap works the same way.
After that come the signup basics. Gmail ignores dots, and plus-tagged mail reaches the same inbox, so a unique-email rule can pass one mailbox several times over.
| Basic fix | What it catches | What it misses | Who it wrongly blocks | What it costs to keep working |
|---|---|---|---|---|
| Email verification | Typos and dead addresses | Any real second inbox | Builders whose code lands in spam | Deliverability work |
| Unique emails | The same address twice | Every different address | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | New domains and ordinary mailboxes | Builders using privacy forwarding | A list someone updates forever |
| Gmail dots and plus addressing | One Gmail inbox written several ways | A second real mailbox | People who sort their mail with plus addresses | Upkeep as mail services change |
| CAPTCHA | Simple scripts | People redeeming by hand | Screen reader users | Fees and lost claims |
| Phone requirement | Casual second accounts | Anyone with another number | Builders traveling without a local number | A charge for every text |
| Card requirement | Casual second accounts | Anyone with another card | Students with no card | Fewer claims, from the people you came for |
| One per IP address | Repeat claims on one connection | Any other network | Your entire venue | Exceptions on the day |
| VPN blocks | Known VPN ranges | Everything off your list | Builders on a campus or company VPN | Another list to maintain |
| Manual review | What a person can spot | Anything overnight | Whoever looks odd to a tired reviewer | Hours you don't have that weekend |
All 120 builders share the venue's connection, so a one-per-IP limit stops the very people you're sponsoring. And at two minutes a claim, reviewing 160 redemptions by hand takes 320 minutes, more than five hours, on a code that had already run out.
What you wanted on Saturday morning was to stop a repeat claim before the $100 went out. Stack every row and you still can't, and you've asked a builder with a demo due to confirm an email, solve a puzzle, add a phone number and enter a card first. Your roster knows which emails were invited, and your database knows which accounts redeemed. Neither one knows whether the claim in front of you looks like a repeat.
Evaluate the claim before the credits land
You don't have to build your own abuse prevention system. AbuseZero takes one API call at the moment a code is redeemed and returns a clear allow or deny, under rules you control. The table above is full of fixes that each look at one thing. AbuseZero's multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, and signals are read together, never one at a time. Its proprietary algorithm comes with AI that checks the claim again. AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing. The domain list nobody updated before the event is covered too, since it checks mailbox aliases, disposable domains and mail routing, and it sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. Creating a fresh account isn't enough to erase previous activity, and a fresh account was all the second account in that diagram had going for it.
Each benefit keeps its own claim history and eligibility, so one event's credits don't count against your signup bonus. Observe mode shows you what would be denied before anyone is blocked, so try it on a smaller event first. Your app still issues the codes and delivers the credits, so keep the individual codes and the separate GPU pool. The quickstart gets your first benefit protected.
Frequently asked questions
Should hackathon promo codes be single-use?
Yes, whenever you have a roster. Where you can't collect names, pair a shared code with a low value and a capped GPU pool.
What do I do if a hackathon code has already leaked?
Turn off the code, don't raise the cap, and send individual codes to the builders still waiting. Then move promo jobs off your paying customers' GPUs. This guide to leaked codes has the full order.
Can I take back credits that were already spent?
Only the unspent balance. Spent GPU time is gone, so taking back free credits is about limiting what's left.
Is a second account from a hackathon builder always abuse?
No. Some builders keep work and personal accounts, and some teams split up mid-event. Decide before the event whether credits are per builder or per team, and put it in writing.
Keep the credits for the builders in the room
Start with Builder
Pay as you go. Protect your first benefit today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.