Most articles about finding hackathons online hand you five big directories and stop. This page treats the list as something you assemble and keep alive: five generic source types worth watching, a six-box fit checker to run before you commit a weekend, and four opinions on picking. No platform or event names appear anywhere, because directories change and the method carries over. A list starts the process; acceptance, judging, and outcomes belong to each event's organizers, and nothing here promises either.
These are types of places, not specific sites. Each row says what to check before you trust the source for your list.
| Source type | What to check |
|---|---|
| Developer communities | Chat servers and forums around programming languages and frameworks carry recurring event announcements. Check whether events repeat; a community that has run several online editions has a working format. |
| University programs | Campus tech clubs and engineering faculties open some of their online editions to outside participants. Check the eligibility line first; some events restrict entry to enrolled students. |
| Open-source project ecosystems | Larger projects run community build events around releases and milestones. Check the project's own community hub rather than third-party summaries, which lag or garble dates. |
| Blockchain and protocol communities | Multi-chain ecosystems publish event rounds and hacker houses on their community pages. Check which network each event targets, so the tooling you learn matches the chain you want to build on. |
| Local meetups with online branches | City tech groups increasingly run hybrid editions. Check whether remote participants can submit and demo too; some hybrid events limit judging to the room, which changes what the weekend is worth to you. |
Two or three of these sources, checked weekly, produce a steadier list than any single directory.
An event that fits someone else can still wreck your month. Print this sheet or copy it into your notes, one block per candidate event, and fill the write-in lines before registering.
| Check | Fill in | |
|---|---|---|
| Team size. Solo, pair, or squad? Write the headcount and which roles you still need. Some events match teams at kickoff; most expect you to arrive formed. | write-in | |
| Remote-ok. Online-only, or in-person with an online track? Write “online” or the city. Travel changes the cost of a weekend more than any entry fee. | write-in | |
| Prize-vs-learning. Write which one you are there for. Prize pools concentrate in a few projects; learning compounds for everyone who ships something. | write-in | |
| Time-zone overlap. Write the event's timezone and your workable build hours. An online event nine hours away turns into night shifts fast. | write-in | |
| Deadline distance. Write the registration deadline and the days left. Late registration plus timezone math is how weekends get lost before they start. | write-in | |
| Skill match. Write the one stack you would build on. If the event forces a framework you have never touched, the weekend becomes a tutorial instead of a build. | write-in |
Print this sheet (Ctrl+P / Cmd+P) and tick boxes with a pen, one column per candidate.
Building a list by hand means opening organizer pages, copying dates, and re-checking them, because deadlines move. Our companion product did that sweep once for the web3 slice of the calendar, and its README describes the result better than a paraphrase would. Quoted verbatim:
“Curated calendar of 45 web3 hackathons, conferences and popup cities from September 2026 through Q1 2027, plus 2 bonus entries for mid-2027. Multi-chain coverage: Ethereum, Solana, Bitcoin, Base, Algorand, Decentraland, stablecoins and more.”
“Every entry was checked against an official organizer page or a major event aggregator (Devpost, DoraHacks, ETHGlobal, ethereum.org, Coinpedia, organizer sites) on September 5, 2026.” … “No dates or prize pools were invented.” … “Hackathon deadlines shift; always confirm on the registration URL before committing.”
That is the shortcut version of everything this page teaches: 45 entries, dates and prize fields swept by hand, shipped as CSV you can sort and Markdown you can skim. The README's own line applies to it the same as to any list you build yourself — confirm on the registration URL before committing. Joining is the point; the calendar exists so the participating starts sooner and the hunting takes minutes instead of evenings. If you want the prep side instead of the list side, read the hackathon preparation checklist.
Opinions, not rules. Disagree freely.
| Item | Value |
|---|---|
| Where-to-look sources | 5 generic source types, 0 platform or event brands named |
| Fit checks | 6 checkboxes, write-in style (team size, remote-ok, prize-vs-learning, timezone, deadline, skill match) |
| Opinion tips | 4, each labeled (opinion) |
| Event claims on this page | None. No guarantees of acceptance, placing, or results; outcomes belong to each event's organizers |
| Source | README of the Web3 Events & Hackathons Calendar, quoted verbatim |
| Companion product | 2026 Web3 Events & Hackathons Calendar, 45 entries |
| Last updated | September 8, 2026 |
one-time · CSV + Markdown · checkout on Getly
More on this site: the free hackathon preparation checklist, the printable hackathon tracker, and the full catalog.