Credits are not cash
AgentHacks 2025 listed $15,450+ in prizes, but the package mixed cash with Claude credits, Vercel credits, Mistral AI credits, gift cards, and office hours. That can still be useful. It is not the same as a cash purse.
Read every prize line as an actual payout, not as a headline number. Credits buy future usage. Office hours buy access. Gift cards buy tools or food. None of those pay rent after the weekend.
Trips are prizes, not prize money
xAI Hackathon 2025 listed 16 non-cash prizes. First-place track winners received all-expense-paid trips to a SpaceX launch, while second-place winners received swag.
That is not shady by itself. The red flag is when a listing sells the event as prize money while the actual award is travel, access, merch, or platform credit. Trips can be valuable. They are not liquid.
Prize value can hide the payout
DevNetwork AI + ML Hackathon 2025 listed a $12,500 prize value. Its first-place package was described as Amazon Echos, conference passes, and email announcement exposure.
Value packages need extra skepticism. Ask what you can spend, who pays it, when it arrives, and whether the award is split across tracks. If the page answers with exposure, treat it as marketing value, not builder income.
Escrow exists because trust is not automatic
JudgeBuddy, an ETHGlobal project, used onchain escrow so builders could verify prize funds before writing code. That exists because prize trust is a real failure mode, especially in web3 and sponsor-heavy events.
You do not need every event to use escrow. You do need a clear sponsor, clear prize owner, clear payout path, and rules that say what happens if a track changes. No source, no rules, no confidence.
Real organizers check winners
MLH says cheating is more common for digital events and recommends checking all winning projects before announcing prizes. Its checklist includes GitHub start times, one-big-commit patterns, old project references, team-member contributions, video timestamps, and Devpost history.
A serious hackathon has operational friction: eligibility, timestamps, submission links, judging checks, and a way to disqualify bad entries. A fake hackathon wants urgency without auditability. Slow down when the page skips the boring rules.
< source-linked guide · dated when published >
browse hackathons