<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 Urbe Campus Florence edition will start on January 26th at 12:00pm and will last for 2 hour (till 2: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.

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

Minimum requirements to be judged

• A link to the open-source code must be provided (e.g. an open and public Github repository)
• If applicable, the contract address(es) of your deployed demo must be provided, either on a testnet of your choice or mainnet of a platform of choice
• A link to a walkthrough video (or demo) of max 3 minutes that shows what you built
  • NO ONLY SLIDES POLICY 🚫
  • How to record your video demo
• More detailed requirements are described on the form (Submissions ) submission page.

Judging Process

The judging process consists of two steps:

• Code and live demo showcase (submission deadline is 12:00pm)
• Each team will have a maximum 7-minute slot with the judges (4 mins demo + 3 mins Q&A). Hackers will have to present their projects and answer questions from the judges. Hackers are only allowed to show a live demo of their project.
• Winning teams will have the chance to run a live demo during the closing cerimony

Judging Criteria

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

• 🎨 Creativity (10%)
  • Is the project idea new and interesting? 0/5
  • Does the project fit the Hackathon theme in an unexpected way? 0/5