Dates

September 8th - September 10th

Eligibility

Only hackers who have submitted an application to the Interchain Hackathon application will be able to submit projects to be considered for prizes and judging. This will be confirmed in the backend when judging projects!

Project and Submission Requirements

All hackers/teams will be required to submit a Github repo with a detailed Readme file describing how the code works if working on a technical product.

Teams should also submit a presentation that accompanies their code or work describing the project idea and any other relevant information such as work and technologies used, and lessons learned. 

Since hackathon projects will be judged virtually it is essential that your presentation and work is clearly defined and explained!

-  No pre-existing projects, you may start working on the project once hacking officially begins at event-kickoff.

- You should not be working on your project before the event officially begins. This includes coding, designing assets, etc. Each hack submission will be judged solely on the quality of the work completed during the duration of the hackathon.

- You may use any pre-existing code in your project only after you have notified the Interchain Hackathon (David or Bora) team in writing about the nature of previously done work and have gotten approval. Further, you need to disclose all relevant information in your submission video, project description, and during judging clarifying what specifically was done before the hackathon.

- In order to ensure that no pre-existing work makes its way into the submission, you must also use version control for your code throughout the course of the event.

Judging Criteria and Winner Selection 

All entries will be judged according to the same core criteria with select tracks having additional track specific judging criteria that may not be published.

Find Core judging criteria Below:

• Technical Depth

  • Did the team approach the problem by learning new technical skills?

  • Was the project solution well thought through?

  • How robust is the project?

  • Does it work beyond hardcoded values?

  • Does the project have the potential to scale?

• Design/Usability

  • Is the product safe?

  • Easy to use?

  • Is the project designed well?

  • Visually appealing?

  • Is the project intuitive?

  • Is it easy to understand how to use the project without explanations?

• Idea Novelness

  • Did the hackers think of an out of the box solution to a problem?

  • Is the project idea clever or compelling?

  • Does the project address a unique problem?

Code of Conduct

• gender
• gender identity and expression
• age
• sexual orientation
• disability
• physical appearance
• body size
• race
• ethnicity
• nationality
• religion
• political views
• previous hackathon attendance or lack of
• computing experience or lack of
• chosen programming language or tech stack

• hacks
• talks, presentations, or demos
• workshops
• any parties associated to the hackathon
• social media
• any other online media