submit-to-hackathon

Structure it in five short paragraphs: the problem, the solution, why Solana is required, technical highlights, and what is next. Keep it 200-500 words, lead with what the project does, and make it scannable since judges review over 100 submissions.

Keep the demo video under 3 minutes. Structure it as a 20-second problem hook, 20-second solution overview, 100-second live demo of the core flow, 30-second technical highlight, and a 10-second wrap-up with a call to action.

Pick the least competitive track that genuinely fits your project rather than the most prestigious one. DeFi tracks tend to be overcrowded, while infrastructure and tooling tracks typically have fewer entries.

No, devnet is acceptable for hackathon submissions and makes it easier for judges to test without spending real SOL. The demo must be live and accessible, clearly labeled as devnet, with test credentials or a pre-funded wallet.

Judges weigh functionality at about 30%, innovation at 25%, technical execution at 20%, potential impact at 15%, and presentation at 10%. A working demo is the single biggest differentiator since judges spend only 2-5 minutes per submission initially.