Solana hackathons have launched some of the most-used protocols in the ecosystem. Marinade Finance, Phantom, and Drift all started as hackathon projects. The Solana Foundation has distributed millions in prizes across its events, and ecosystem partners frequently run their own hackathons with substantial prize pools.
Winning is not just about technical skill. It is about picking the right idea, presenting it clearly, and building something that actually works within the time constraints. This guide covers what separates winners from the hundreds of submissions that get forgotten.
Where to Find Solana Hackathons
The Solana Foundation runs its flagship hackathons periodically -- these are the largest events with the biggest prize pools. Past editions (Ignition, Riptide, Grizzlython, Hyperdrive, Renaissance, Radar) have offered hundreds of thousands of dollars in prizes across multiple tracks.
Beyond the flagship events, look for:
- Superteam hackathons -- Superteam runs regional events across Asia, Africa, Europe, and Latin America. Smaller prize pools but less competition.
- Ecosystem partner hackathons -- Projects like Jupiter, Marinade, and Tensor occasionally sponsor their own hackathons focused on building within their ecosystems.
- Colosseum -- The team behind Solana's Radar hackathon now runs Colosseum, which combines hackathons with an accelerator program. Winners get funding alongside prizes.
- ETHGlobal and cross-chain events -- Many multi-chain hackathons have Solana-specific tracks. These are worth entering because the Solana-specific competition is usually thinner.
Follow @solaboratory, @SuperteamDAO, and @ColosseumOrg on Twitter to catch announcements early.
Building Your Team
Solo submissions win occasionally, but teams of 2-4 have a clear advantage. Here is what a winning team typically looks like:
- One strong Rust/Anchor developer who can write and deploy on-chain programs
- One frontend developer who can build a usable demo quickly
- One person focused on design and presentation -- this role is underrated
You do not need all three from day one. Many successful teams form during the hackathon itself, in Discord channels or at in-person events. If you are looking for teammates, post in the hackathon's official Discord early with a clear description of your skills and what you are looking for.
Common Team Mistakes
- Too many developers, no one on product. You end up with impressive code and a confusing demo.
- Too large a team. Four people is the sweet spot. Five or more creates coordination overhead that kills momentum during a time-constrained event.
- No clear decision maker. Someone needs to make final calls on scope and direction. Agree on this before you start building.
Picking a Winning Idea
This is where most teams go wrong. They either build something too ambitious to finish or something too generic to stand out.
What Judges Look For
Having studied winning projects across multiple Solana hackathons, judges consistently value:
- Novelty -- Does this solve a problem in a new way, or is it the fifth DEX aggregator in the submissions?
- Working demo -- A deployed, functional prototype beats a polished pitch deck every time.
- Clear use case -- Can you explain in one sentence who this is for and why they would use it?
- Technical depth -- Judges can tell the difference between a wrapper around existing APIs and genuine on-chain innovation.
- Ecosystem fit -- Does this fill a real gap in the Solana ecosystem?
Idea Selection Framework
Ask yourself these questions:
- Is this possible in the hackathon timeframe? If you cannot build a working MVP in 2-3 weeks (or a weekend for shorter events), scope it down.
- Does this already exist? Search MadeOnSol's directory to check. If something similar exists, you need a clear differentiation angle.
- Is there a Solana-specific advantage? The best Solana hackathon projects leverage Solana's strengths -- speed, low fees, composability. A project that could work just as well on any chain will not impress judges.
- Can you demo it live? Projects that require complex setup to demonstrate lose impact. Build something a judge can try in their browser in 30 seconds.
Winning Idea Patterns
Some patterns that consistently perform well:
- Developer tools that make building on Solana easier
- Novel DeFi primitives that enable new financial behaviors
- Consumer apps that bring non-crypto users onto Solana
- Infrastructure that solves known pain points (RPC reliability, data indexing, transaction simulation)
- Integrations between existing protocols that create new functionality
The teams that win Solana hackathons share a few traits: they scope aggressively, they deploy early, they communicate clearly, and they build something that fills a real gap. Technical brilliance matters, but it is not sufficient on its own.
