Judging & Rules

Scoring is out of 100 points, common to every track. Each track's own criteria supply the basis for scoring Security Soundness and Verifiability.

Judging Criteria

Criterion	Weight	What we look for
Problem Definition	25%	Is it specific about who has the problem? Is the problem real?
Security Soundness	25%	Is the threat model clear? Have you considered how it could be bypassed?
Implementation	20%	Does it demo live? Is it more than a mockup?
Verifiability	15%	Have you shown the effect with numbers or scenarios?
Extensibility	5%	Can this continue after the hackathon?
Technical Originality & Impact	10%	Did you solve it differently from everyone else? Does the approach travel outside the track?

Technical judging selects the Top 6 Finalists, who give final presentations at Demo Day; winners are decided by the Demo Day judging. Every team is invited to Demo Day and networking.

Participation Rules

Team size

1–5 people. Solo entries are welcome. One person cannot be on two teams.
Multiple tracks

A team may enter more than one track. Keep the work and the submission separate for each; the same artefact submitted to two tracks does not count.
Prior code

You may build on an existing project. State in the README what you built during this period.
AI tools

AI-assisted development is allowed. Teams remain responsible for understanding, explaining and validating all submitted work. Material AI-generated components should be disclosed in the README.
Open source

Use it freely, and respect the licence. Submitting someone else's code as your own is disqualifying.
Public repository

The repository must be public at submission time. You may make it private again after judging closes on Sep 25.
Intellectual property

IP in your submission remains with your team. The organisers may use it non-exclusively for judging and for event records and promotion; any research or commercial use requires your prior consent.
Demo Day attendance

Prizes are awarded on site. At least one team member must attend to be eligible.
Prize payment

Prizes are paid after deduction of taxes and charges required by applicable law. Payment goes to one team account; how the team divides it is up to the team.

White-hat Policy

Testing must be carried out only in environments provided or explicitly approved by the organisers. Unauthorised attacks against live services, mainnet or third-party systems are prohibited and may result in disqualification. Use testnets, test accounts and de-identified data for demos.

Code of Conduct

Treat participants, mentors, judges and partners with respect. Harassment, discrimination and threatening behaviour are not tolerated
Do not access or interfere with another team's work, repositories or submissions
Do not attempt to improperly influence the judging process
This applies equally on site and in every online channel
If you experience or witness a problem, contact dev@anam145.com. Reporters' identities are protected

A confirmed breach may lead to a warning, disqualification, or withdrawal of an award. The decision rests with the organisers.

Apply now -> Tracks -> Back to overview