<aside> ❗ Disclaimer: all the following requirements and criteria are related to the judging and evaluation process of the main track and do not necessarily apply to sponsor bounties. Each sponsor will have their own bounty description and requirements as well as an internal process to judge projects.

</aside>

Judging session

The official judging session for ETH Bishkek will start on October the 26th at 12:00 am and will last for 3 hours (till 3:00pm). In that time, teams will have to showcase their project live to the selected jury. After the submission deadline, each team will be assigned to a group of judges that will be responsible for evaluating their work.

During the same judging session, teams will also be able to showcase their project to each bounty sponsor they applied to. In this case, judging process, time and criteria are decided by the sponsors and ETH Bishkek is in no way involved in this process. What usually happens is that hackers visit the sponsor’s booth and showcase what they built. Not all the sponsors will be attending in person, but you can always reach them out on their dedicated Discord channel, as they may want to schedule a quick online meeting to see what you built.

This to say that we highly encourage hackers to stay at the venue up until the end of the closing ceremony to ensure you don’t miss your judging slots.

Minimum requirements to be judged

Your project is submitted on TAIKAI before the deadline & all the project details are included

Judging Criteria

The project score (out of 100%) is calculated from the following judging criteria:

💻 Code (40%) – Technical execution & functionality

• How well is the project implemented from a technical standpoint?
• Is the functionality proposed in the submission fully working?
• How effectively does the code leverage the chosen technology stack?
• Is there a stable, demonstrable version of the project?
• Is the application easy to understand and navigate? (Or, if it’s a tool/API, is it simple to integrate?)

📊 Business Viability (35%) – Practicality & business plan

• Does the project solve a real-world problem or fill a significant gap?
• How feasible is the project’s implementation in the real market?
• Is there a clear and sustainable business model or revenue strategy?
• How intuitive is the UX/UI for the intended audience?

💡 Innovation (15%) – Originality & unique value

• How unique or creative is the concept compared to existing solutions?
• Does the project leverage emerging or cutting-edge technologies?
• Does it enable new possibilities, markets, or applications?

🖼️ Creativity (10%) – Presentation & problem-solving approach

• How engaging and effective is the project presentation?
• How well does the project demonstrate creative problem-solving?
• Are there novel design elements or storytelling approaches that enhance impact?

<aside> 🚨 PLEASE NOTE:

Judges preserve a 14-day period to make the results of the two hackathon tracks official. If irregularities are found in the code repositories of any of the winning teams, the judges may exclude the team from the hackathon competition and not award the prize.

To allow the judges to make appropriate evaluations of the code repository, the code must be left open source for at least 4 weeks after the closing ceremony happening on Sunday, October 26th 2025.

</aside>