Dates:
Hackathon Start (Opening): July 11, 2026
Submission Deadline (Closing): September 21, 2026 (Insert Global Time)
Judging Period: To Be Announced (TBA)
Winners Announced: To Be Announced (TBA)
Eligibility:
The Global Innovation Build Challenge (GIBC) V2 is open to all builders, hackers, and creators globally. To participate, you must meet the following criteria:
-
Open to Everyone: Anyone—including professionals, hobbyists, independent developers, and students alike—is welcome to register and compete.
-
Team Size: You can participate as an individual solo developer or collaborate in a team of up to 6 members.
-
Original Work: All projects, code, and designs submitted must be newly developed during the 10-week hacking period (July 11 – September 21, 2026). Pre-existing commercial projects or recycling identical work from past hackathons will result in disqualification.
-
Single Track Limit: A team or solo developer may submit only one project to one specific track (Track 01, Track 02, or Track 03). Multiple submissions across different tracks are not permitted.
Project and Submission Requirements:
Technical Standards:
-
Track Alignment: Your project must cleanly fit the technical definition of your chosen track. Submissions to Track 01 must respect the strict 50-million parameter ceiling; Track 02 must demonstrate utilization of empirical datasets; Track 03 must showcase an original functional prototype.
-
Working Implementation: We do not accept theoretical papers or static presentation slides alone. The project must have a functioning backend, running code, or a physical schematic that operates as described.
Submission Guidelines:
-
Deadlines are Final: All six required submission components (Description, Repository, Demo Video, Tech Stack List, Team Info, and Screenshots) must be fully uploaded to Devpost before September 21, 2026. Late submissions or post-deadline edits will not be reviewed.
-
Code Transparency: Your repository must be public, unrestricted, and include clear execution files. If special dependencies, paid API tokens, or unique environments are required, they must be thoroughly documented in your README.
-
Media and Video Access: Ensure your demo video and repository are not set to "Private." If judges cannot view your video or access your code during the evaluation period, the project will be disqualified.
-
Language: All written descriptions, repository documentation, and video demonstrations must be submitted in English to ensure our international panel of 10–15 industry judges can properly evaluate your work.