Criteria & How We Judge

The following details the sections of the criteria, and the respective weightings of each section.

The weightings used here, align with a sentiment of:

Projects that execute effectively as a team

Projects that sufficiently integrate with our network

Projects that sufficiently gain market validation

Projects that achieve results that align with network outcomes

Judging Criteria

INNOVATION

10%

INNOVATION

10%

FEASIBILITY

10%

FEASIBILITY

10%

EXECUTION

20%

EXECUTION

20%

INTEGRATION

15%

INTEGRATION

15%

SUCCESS

20%

SUCCESS

20%

VALIDATION

15%

VALIDATION

15%

PITCH

10%

PITCH

10%

CRITERIA

How We Judge

INNOVATION

10%

FEASIBILITY

10%

EXECUTION

20%

INTEGRATION

15%

SUCCESS

20%

VALIDATION

15%

PITCH

10%

The following details the sections of the criteria, and the respective weightings of each section.

The weightings used here, align with a sentiment of:

Projects that execute effectively as a team

Projects that sufficiently integrate with our network

Projects that sufficiently gain market validation

Projects that achieve results that align with network outcomes

CRITERIA

How We Judge

INNOVATION

10%

FEASIBILITY

10%

EXECUTION

20%

INTEGRATION

15%

SUCCESS

20%

VALIDATION

15%

PITCH

10%

The following details the sections of the criteria, and the respective weightings of each section.

The weightings used here, align with a sentiment of:

Projects that execute effectively as a team

Projects that sufficiently integrate with our network

Projects that sufficiently gain market validation

Projects that achieve results that align with network outcomes

Submission Artefacts

Each team should appoint 1 ‘Team Representative’ to submit your project on the submission portal by

8 AUGUST 2025

11:59 PM ET

11:59
PM ET

Project’s GitHub Repo Link

Team leader to create the project's GitHub Repo and share the access with the rest of the team to collaborate on.

The team will save all submission items onto this Github Repo where the judges may access the items during the judging period.

GitHub repo should host the application’s code, a README file, any other deployment files and testing instructions.

Project Details

Project Description (max 100 words)

Selected hackathon track

A list of tech stack (solutions, technology infrastructure, technology services, etc.) used by the team to build your project

Project Demo Link

This is the URL to the live working environment of the solution the team has developed.

Pitch Deck in PDF

Here’s a potential structure you can adapt for your pitch deck:

Team and Project Introduction

Here’s a potential structure you can adapt for your pitch deck:

Team and Project Introduction

Project Summary

Provide a comprehensive overview of your solution, keeping in mind that the 7 judging criteria will form the basis of judges’ assessment.

Future Road Map

Any key learnings and room from improvements? Outline the next steps for your project if you were to continue developing it.

Demo

Showcase the technical strengths, usability and performance of your solution here! You must pre-record your demo, upload it to Youtube, and insert the link in your deck.

Note: Submissions without a demo video link in the deck will not be scored

Optional

Certificate of completion for "Building on Hedera" Course

The "Building on Hedera" course offers valuable benefits for hackathon participants:

Comprehensive Learning

11 modules covering Hedera Hashgraph architecture and development fundamentals.

Official Training

Created by The Hashgraph Association and Swirlds Labs.


Recognised Certification

Earn an official Certificate of Completion minted on Hedera and a developer knowledge badge upon passing the final assessment.

Bonus Reward Opportunity

First 100 participants to submit the certificate of completion for building on Hedera course will receive USD$50.

Note: Submission of the certificate is optional and does not impact your eligibility to participate in or win the hackathon.

Submission Portal

Reminder that all teams should submit before the following date, to qualify for the hackathon prizes.

8 AUGUST 2025

11:59 PM ET

01

Make sure ALL members of your team have registered for the hackathon.

02

Only the Team Representative will need to submit the project on behalf of the team.

All teams are encouraged to submit as soon as possible before 08 August 2025 to avoid last-minute submissions and missing the deadline.

03

Begin your submission via Dorahacks. If all the submission items are not yet completed, you may put placeholders.

04

If you need to make edits or updates to your submission, you may do so before the submission deadline via Dorahacks.

05

If you face any issues or require help during submission, contact us on the 

#mentor-assistance channel on the Hedera Hello Future: Origins Hackathon Discord, or email us at support@hellofuturehackathon.dev