What gets you in
01Build AI-native on 0G. AI-native apps, agents, companions, or games using 0G — storage, compute, or chain. 0G has to do real work in your app: if it runs the same without it, that's a bolt-on and it doesn't qualify.
02Vibe coding is the point. This is a vibe coding tournament — prompts, copilots, agents, build with whatever ships. AI assistance isn't cheating here; entering someone else's project or claiming your app does things it doesn't is.
03Your work, this window. The build is your team's own work, made during the tournament window — June 15 onward. Open-source libraries are fair game; a pre-existing product or a thin fork is not.
04Public repo, working demo. You enter with a public repo URL plus a description — if we can't open it, we can't judge it. Prove it runs with a live build or a demo video, and make the demo match the code; faking it counts as misrepresentation.
What keeps you in
05Deadlines lock a snapshot. Every round's deadline locks a snapshot of your repo, and that exact snapshot is what gets judged — first cut is June 23, final lock July 8. Pushes after a buzzer roll to the next round; no snapshot at the deadline means nothing to judge, you're cut.
06Improve and resubmit. Survive the cut and your project unlocks — polish, rebuild, resubmit before the next deadline, that's the meta. The last lock is July 8: from the quarter finals on, one build rides through to the final.
07One team, one project. Each team enters one project, and each builder rides with one team — the platform enforces both. Judges never score a team they belong to; conflicts of interest are blocked automatically.
08Cheat and you're out. Plagiarized work, a faked demo, a repo taken private mid-tournament, or gaming the bracket gets a project pulled at any stage, prizes included. If you disagree with a call, file an appeal — organizers have final say.
That covers what can enter. How the bracket, judging, and prizes work is in the competition rules.