Overflow 2026 Open Lab — Bring Your Build, Leave with a Plan Judges Can't Ignore
The difference between a competitive Sui Overflow submission and a forgettable one usually isn't the code — it's the framing. The team that practiced their 5-minute demo three times beats the team that didn't, every cycle. The team that read the judging rubric and noticed 50% of the score is "real-world application" pitches differently from the team that thought it was a technical contest. This is the day we make sure your build doesn't fall into the forgettable bucket. No lectures, no slides walking through SDKs. You bring your code, your half-written demo video, your unanswered architecture question — and we tear it apart together with judge-level honesty before judges get the chance. By the end of the session, you'll have a concrete punch list of what to fix before June 21, a sharper pitch, and clarity on which of the four Overflow tracks gives your project the best shot.
What You'll Learn
The Overflow judging mental model — why "Real-World Application" carries 50% of the score and how to win on that single axis
How to read your own GitHub repo the way a judge will — README, exposed secrets, commit timing, and deployment artifacts
The 5-minute demo video structure that consistently wins: problem, solution, live demo, why Sui, roadmap — with timing per beat
Mainnet vs testnet — when each makes sense, and how the 50/50 prize split rewards mainnet deployment by August 27
KYC, OFAC, and the legal mechanics that decide whether your team actually gets paid after winning
How to pick your one primary track when your project overlaps multiple — without weakening your strongest pitch
Who Should Attend
Teams already building toward an Overflow 2026 submission who want senior critique before the deadline
Solo builders who want a second pair of eyes on their architecture, repo, and demo flow
First-time hackathon participants who don't yet know what a competitive submission actually looks like
Anyone who attended Day 1 (Walrus + Seal) or Day 2 (DeepBook) and is now wrestling with shipping their build
What to Bring
Your laptop
A working — or working-ish — build to share on screen
Your public GitHub repo URL ready to share
A draft demo video if you have one (we'll critique it live)
Honest questions about where you're actually stuck
Join us at SuiHub to learn, build, and connect with fellow developers pushing the boundaries of the Sui ecosystem.