All prices in this guide are illustrative sample ranges, not quotes. They move with the market and with the individual account.
Choosing between online, in person, and hybrid
The format decides who shows up. An online hackathon gets you volume and reach into Asia, Latin America and Eastern Europe, which is where a lot of the cheap, hungry developer talent is. An in person event gets you fewer teams but better ones, because flying somewhere and sleeping badly for two nights filters out people who were only going to submit a landing page. Hybrid means you run the submission process online and hold a finals weekend in one city for the shortlisted teams, and it is the format I recommend for most projects because you get the reach of online and the commitment of in person without paying for 400 hotel nights.
| Format | Typical submissions | Typical all in cost | Best for |
|---|---|---|---|
| Online only | 80 to 400 projects | $40k to $90k | New chains and SDKs that need first users |
| In person | 30 to 120 projects | $120k to $400k | Established projects that want a recruiting pipeline |
| Hybrid | 100 to 500 online, 10 to 25 finalist teams | $90k to $250k | Most projects, most of the time |
Those cost figures are typical ranges from agency and sponsor budgets, not published prices. Every organizer quotes differently and the number moves with the city.
Platforms to host on
You do not have to build submission infrastructure. Four platforms cover almost every crypto hackathon, and they differ mainly in which developer population they already have.
| Platform | Developer base | How it works | Notes |
|---|---|---|---|
| DoraHacks | Large and global, heavy in Asia | You run your own hackathon on the BUIDL platform and fund the prize pool, with quadratic funding available for community voting | Best reach for a chain or infrastructure project running its own event |
| Devfolio | Very strong in India | Hosted hackathons with built in judging, team formation and sponsor tracks | ETHIndia runs here. Go here if you want Indian developer volume |
| ETHGlobal | Ethereum developers, the highest quality pool in the space | You do not host, you sponsor. You buy a partner slot at an existing event and fund a prize track | Most expensive per developer, best signal per developer |
| HackQuest | Newer, learning first | Courses plus hackathons, so developers arrive having already done a tutorial on your stack | Good when your product has a learning curve |
The decision is simple. If you want to own the event and the mailing list, host it yourself on DoraHacks or Devfolio. If you want quality developers and do not care about owning the audience, sponsor a track at an ETHGlobal event instead. Partner slots at ETHGlobal events commonly run in the $25,000 to $100,000 range depending on tier and event, which is a typical range and not a published rate card, so ask for their current deck.
Prize pools that actually work
Prize money is the single number developers filter on, and there is a threshold effect. Below about $25,000 in total prizes you get students and weekend projects. Above about $100,000 you start getting teams that were already building something and are willing to re point it at your stack. Past roughly $500,000 the extra money buys very little extra quality, because at that point the constraint is how many good teams exist, not how much you are paying them.
| Total prize pool | What you get | Who this is for |
|---|---|---|
| $10k to $25k | 40 to 100 submissions, mostly tutorial level | Small projects testing the format |
| $50k to $100k | 100 to 250 submissions, 5 to 15 genuinely usable | The normal range for a funded project |
| $250k to $500k | 300 plus submissions, real teams, media coverage | Chains and large protocols running a flagship event |
| $1M plus | Diminishing returns on quality, strong returns on attention | Chains in a land grab for developers |
Split the pool rather than concentrating it. A structure that works is roughly 40 percent to a small number of grand prizes, 40 percent spread across sponsor tracks so more teams win something, and 20 percent in follow on value such as grants, accelerator interviews or credits. Follow on money matters more than headline prizes. Colosseum, which now runs the Solana hackathons, pairs its events with an accelerator that invests in winning teams, and that structure is a large part of why Solana hackathon winners keep shipping after the event.
Sponsor tracks and judging
Sponsor tracks are how you sell parts of the event to other companies and how you point teams at problems you actually want solved. Write each track as a problem statement with a dollar amount attached, not as a category. "Best use of our oracle" produces slop. "Build a liquidation bot that reads our price feed and settles in under two blocks, $15,000" produces code you can read.
For judging, use two rounds. Round one is a paper screen by your own engineers against a fixed checklist: does it compile, does it run on the target network, is the repository public, is there a working demo under three minutes. That usually removes 50 to 70 percent of submissions. Round two is live demos in front of five to seven judges scoring on a written rubric, with technical difficulty and whether the thing actually works weighted highest. Publish the rubric before submissions open. Hackathons get accused of being rigged mainly when the criteria were never written down.
Put at least two outside judges on the panel. Investors and well known developers make the results credible and give you a reason to talk about the event afterwards.
An eight to twelve week timeline
| Week | Work |
|---|---|
| Weeks 1 to 2 | Lock the budget, pick the platform, write the tracks and the judging rubric, sign co sponsors |
| Week 3 | Announce. Landing page, registration open, first press push, KOL briefing |
| Weeks 4 to 6 | Registration drive. Workshops, office hours, documentation fixes, developer Telegram or Discord staffed daily |
| Weeks 7 to 9 | Build period. Mentor hours, mid point check in, reminder emails at seven days and 48 hours before the deadline |
| Week 10 | Submissions close, paper screen, finalists announced |
| Weeks 11 to 12 | Demo day, judging, prizes paid, winner announcements, follow up on the retention program |
Do not compress below eight weeks. Registration builds slowly for the first three weeks and then most signups arrive in the last ten days before the deadline, so a short window means you never get the late surge. Twelve weeks is the ceiling because attention decays and teams forget they registered.
What it costs
| Line item | Online | Hybrid or in person |
|---|---|---|
| Prize pool | $25k to $100k | $50k to $250k |
| Platform or partner fee | $5k to $30k | $25k to $100k |
| Venue, food, AV | Not applicable | $30k to $150k |
| Travel stipends for finalists | Not applicable | $15k to $60k |
| Marketing, KOLs and press | $10k to $40k | $20k to $60k |
| Developer relations staffing | $10k to $25k | $15k to $40k |
| Design, video and content | $5k to $15k | $10k to $25k |
The line people underfund is developer relations staffing. Somebody has to answer questions in the chat every day for six weeks, and if nobody does, half your registrants never submit. Budget a real person, not a bot. Our KOL budget planner helps size the marketing line against the rest.
Promoting it through KOLs and developer communities
Developer marketing and token marketing are different jobs. A KOL with 400,000 followers who posts about price will send you zero developers. The accounts that move registrations are mid size technical accounts, roughly 20,000 to 150,000 followers, who write about code and whose replies are full of other builders. Pay them to actually read your documentation and post an honest first impression, and accept that some of that feedback will be critical.
The channels that work, in order: university blockchain clubs and existing hackathon mailing lists, technical Telegram and Discord servers, mid size developer accounts on X, a Spaces or livestream with the engineers who built the SDK, and developer newsletters. Paid ads on X and Google are close to useless here. See how to vet crypto KOLs for the screening process, and running a Twitter Spaces AMA for the format that works best during registration week.
Press releases are worth doing twice, once at announcement and once at winners. They will not drive registrations but they create the search results that exist afterwards. See crypto press release distribution.
What to measure after demo day
Registrations and submissions are the metrics organizers report and they are close to meaningless. Measure these instead, at 30 and 90 days after the event:
- Deployed projects. How many submissions have a live contract or a running service on mainnet or testnet that you can query today.
- Retained developers. How many participants pushed a commit to a repository using your SDK in the 90 days after the event. A typical range is 10 to 20 percent of submitting teams, and anything above 25 percent is a good event.
- Developer accounts still calling your API. Pull the API keys issued during the event and check activity monthly.
- Follow on funding. How many teams raised, got a grant or joined an accelerator afterwards. This is the number investors and your board actually care about.
- Documentation issues filed. A hackathon is the cheapest usability test you will ever run on your own docs. Count the issues and fix them.
Track all of it against cost per retained developer. Dividing total spend by the number of people still building 90 days later usually lands somewhere between $2,000 and $10,000, which sounds expensive until you compare it with recruiting fees.
Hackathons worth studying
ETHGlobal runs the highest quality events in the space, with several hackathons a year in different cities plus online editions, and its alumni list includes projects that went on to raise serious money. Its model is worth copying: tight scope, strong judging, and partner tracks funded by sponsors rather than a single giant prize.
The Solana hackathons, now run by Colosseum, are the best example of pairing an event with capital. Winning teams get an accelerator path and investment rather than just a check, and several well known Solana companies started as hackathon submissions.
Chainlink's hackathons show what scale looks like for an infrastructure company. They have run with prize pools in the high hundreds of thousands of dollars and thousands of registered participants, structured around integrating one specific product, which is the right shape when you have a single SDK you want people to use.
If you want help running one, that is what our hackathon launch service does, and crypto event marketing covers the conference side.
Questions
How much does it cost to run a crypto hackathon?
An online hackathon typically runs $40,000 to $90,000 all in, and an in person or hybrid event runs $90,000 to $400,000. The prize pool is usually the largest single line, followed by venue costs if you are gathering people in one place.
How big should the prize pool be?
Below roughly $25,000 you mostly get tutorial level submissions. The normal range for a funded project is $50,000 to $100,000, and flagship chain events run $250,000 to $1M. Follow on grants and accelerator access matter more to strong teams than the headline prize.
Should I host my own hackathon or sponsor ETHGlobal?
Host your own on DoraHacks or Devfolio if you want to own the event, the branding and the developer mailing list. Sponsor an ETHGlobal track if you care more about developer quality than ownership and are comfortable paying more per participant.
How long should a crypto hackathon run?
Eight to twelve weeks from announcement to demo day. Most registrations arrive in the last ten days before the deadline, so a shorter window loses the late surge, and anything longer than twelve weeks loses attention.
What should I measure after the hackathon?
Count deployed projects, developers still committing code at 30 and 90 days, API keys still active, and teams that raised money or got grants afterwards. Registrations and submission counts look good in a recap and tell you almost nothing.
Do KOLs help promote a hackathon?
Technical accounts with roughly 20,000 to 150,000 followers do, because their audiences are builders. Large price focused accounts send traffic that never registers, so screen for whether the audience writes code.
