The Sui Overflow Hackathon (the “Hackathon”) organized and sponsored by the Sui Foundation (the “Organizer”) is a community driven hackathon intended for collaboration and learning in the Sui ecosystem. The overarching goal of the Hackathon is to foster developer engagement with the Sui blockchain network (the “Network”) resulting in the deployment and launch of high quality and durable projects on the Network (each, a “Project”) and the secondary goal is to foster the growth of the Network’s global developer community while embodying the Sui Foundation’s values of openness, fairness and competition through tangible action and a demo day contest that involves participants from the entire ecosystem.
By applying to or participating in the Hackathon, you agree to the following Hackathon Terms and Conditions (these “Terms”), the Event Participation Terms and Conditions [LINK], Sui Foundation Terms of Service [LINK], and Privacy Policy [LINK] (collectively, the “Event Terms”) as they all apply to your participation as a host, speaker, guest, sponsor or other type of participant at the Hackathon. Capitalized terms used herein shall have the meanings ascribed to them in the Event Participation Terms and Conditions unless otherwise defined herein.
Key Information and Dates
*Registration Period: Feb 12th - May 11th
Shortlisting Period (Rolling): May 12th - May 19th
Hackathon Duration: 6 weeks (“Hackathon Duration”)
Demo Day: May 23rd to 25th
Results Announcement: May 31st
Hackathon Eligibility
We only allow Teams to submit pre-existing code or projects that were started as of the date and time that is [___], approximately two (2) months prior to the start of the Hackathon (the “Hackathon Effective Date”) as determined by the Organizer (and such work, “Pre-existing Code”). You may use any Pre-existing Code in your Project only after you have notified the Organizer in writing about the nature of such Pre-existing Code and have received the Organizer’s written approval therefor.
You may not work on your Project before the Hackathon Effective Date. This includes coding, designing assets, etc. Each submitted Project (“Submission”) will be judged solely on the quality of the work completed during the duration of the Hackathon and/or completed after the Hackathon Effective Date.
If there is a situation where a Team is porting or continuing an existing Project developed prior to the Hackathon Effective Date, the Team must obtain explicit permission from the Organizer in writing before continuing to work on or submitting the Project for eligibility. Otherwise, by using any pre-existing work developed before the Hackathon Effective Date, you forfeit the right to be considered as a participant for the Hackathon.
In order to ensure that no unauthorized pre-existing work makes its way into a Submission, each Team must also use version control for its code throughout the course of the Hackathon. Any code repositories with single commits of large files without proper documented history will by default be assumed to be disqualified unless proven otherwise to the satisfaction of the Organizer in its sole discretion.
Further, you must disclose all relevant information in your submission video, Project description, and during judging clarifying what specifically was done before the Hackathon. You represent and warrant that all information relating to Pre-existing Code that you provide in your Application and during the Hackathon is accurate, complete and does not contain any misrepresentations or omissions.
If, upon inspection (during or after the event), you present work that appears to have been completed before the Hackathon Effective Date, or does not accurately reflect your Project description/video, or extends unauthorized pre-existing work that was not disclosed, in each case, in the sole discretion of the Organizer, your Project is subject to immediate disqualification with full revocation of any prize amounts along with a permanent ban from other Organizer community events.
Demos; Judgment of Submissions; Selection of the Winners; Prizes
Each Team may enter their Submission in one of the following vertical tracks and one of the following Sui technology tracks (each, a “Track”):
All Submissions will be judged by a panel of nine (9) judges (the “Panel”) according to the rubric (“Rubric”) made available by the Sui Foundation at [https://suifoundation.notion.site/Sui-Hackathon-General-Rubric-a11a73996e8c427982470107a48355d8 (the “Rubric Site”). You understand and acknowledge that the Sui Foundation may update the Rubric at any time in its sole discretion before the Hackathon Effective Date. Please check the Rubric Site for the last updated Rubric.
Each Team will be assigned to a demo session (“Session”). Each Team will be given five (5) minutes to present their Submission to the Panel during their assigned Session. If the Panel or audience has questions regarding a Team’s Submission, an additional two (2) minutes of time will be allotted to Q&A. Time limits will be strictly enforced by the Sui Foundation. Teams who are not present when called to present during their assigned Session will be immediately passed. Teams who were passed previously will be called again at the end of the respective Session. Teams who fail to be present when called a second time will be withdrawn from the Hackathon.
A prize will be awarded to four (4) Teams in each Track whose Submission earns the highest total overall score as determined by the Panel. The decision of the judges will be final. If any ties must be broken to determine the winner, the judges will choose the tied Submission that scores the highest in the “Project Evaluation” category as set forth on the Rubric. The Track-specific prizes are as follows:
In addition to the Track-specific prizes, ten (10) Teams will win each of the following prizes:
The winning Teams will be notified by email on or around one week following the Hackathon Effective Date. In order to receive the prize, one member of the winning Team must confirm acceptance of the prize via email. If a selected winning Team cannot be contacted, is ineligible, fails to claim a prize, or fails to pass any required KYC or background check, the prize may be forfeited and an alternate winner may be selected from the remaining eligible Submissions as determined in the sole discretion of the Panel.