The whole process from application to results, the rules, evaluation and frequently asked questions are on this page. If you can't find what you need, ask the HackTrail Assistant or write in our Telegram group.
HackTrail is a fully online hackathon series open to everyone, everywhere. Joining is free. Everything happens on this site: application, team, submission, evaluation and results. For announcements, questions and finding teammates there is also our dedicated Telegram group.
01
Apply
Fill in the 3-minute form and choose to join solo or as a team. You get a confirmation email; you sign in to your panel with email and password or with your Google account.
02
Form your team
If you are the team lead, send the invite link from your panel to your friends. Up to 5 people. You can also take part on your own.
03
Learn and set up
Learn Canton and Daml with the steps in the Developer Hub, set up your environment and pick your idea.
04
Build
Build your project for four weeks. When you get stuck, turn to the Developer Hub, the HackTrail Assistant or the Telegram group.
05
Submit
Send your GitHub repo, demo video and short description from your panel before the deadline. You can edit it until the deadline.
06
See the results
The jury scores projects online and winners are announced in one overall ranking. Scores and jury comments are published openly.
Dates are on the Program page and in the countdown in your panel. All times are shown in Istanbul time (UTC+3) and UTC.
Joining
Solo or as a team
The process is the same for everyone: each person submits their own application. Teams come together after applying, through an invite link.
Solo
Choose "Solo" in the form. You appear as a one-person team in your panel. You can team up with someone else any time before the team lock.
Team lead
Choose "As a team" in the form and enter the team name. Your panel gives you your own invite link. Send it to your teammates.
Team member
Open the link from your team lead, complete your own application and press "Join team". If you have already applied, just open the link.
A team has 1 to 5 members. Everyone can be in only one team, and each team submits one project.
Members can be added and removed until the team lock. After the lock no new members can join; leaving is still possible. The team lock is 3 days before the deadline.
If the team lead leaves, leadership passes automatically to another member.
All team changes are shown with date and time on the team page.
Everyone who applies is deemed to accept these rules. If the rules change, the change is announced on this page with its date and participants are notified by email.
Who can take part
Anyone aged 18 or over, from anywhere in the world, can take part. Joining is free; you don't need to buy any product or token.
Organizers, jury members, mentors and their immediate family cannot receive prizes.
People on international sanctions lists, and organizations they represent, cannot take part.
Project
The project must run on Canton Network: it must contain real Daml contracts (signatories, observers, choices). A wrapper around another chain does not count.
Projects running on LocalNet are valid. DevNet and MainNet are not required.
The project must be built during the building period. Pre-existing code may be used, but the submission form must state clearly which parts existed before. The jury only scores work done during the building period.
A large codebase with no commit history, or uploaded in one go, may be treated as undeclared pre-existing code.
AI tools may be used. If they were, say so in the submission form.
Open-source libraries and official templates (for example CN Quickstart) are allowed.
Intellectual property
All rights to the project and code belong to the team.
The repo must be public and carry an open-source license (MIT or Apache-2.0).
The organizer and sponsors may use the project name, description and demo video to promote HackTrail.
Time and submission
The submission deadline is final. The system closes submissions automatically at that time.
If you have a technical problem before the deadline, use the "Report a problem" button in your panel. Extra time can only be considered for problems recorded this way.
At the deadline, the current state of your repo (commit) is recorded. The jury evaluates that state; later changes are not scored.
Disqualification
Copying someone else's project or using undeclared pre-existing code
Breaking the code of conduct
Misleading the jury or other participants, or trying to influence the evaluation
Being in more than one team or creating fake accounts
General
Responsible organization and prize payer: Canton Foundation. Questions: ferhat@hacktrail.cc
The organizer may change dates and format when needed. Changes are announced in advance.
The jury's decision is final. Within 72 hours of the results, appeals are only possible for factual errors (such as a wrong commit or a link that wouldn't open being evaluated).
Submission
Submission checklist
You submit from your panel. When you press Submit, the system automatically checks that your links open. You can edit your submission as often as you like until the deadline.
GitHub repo: public, with an open-source license.
README: setup and run steps, the privacy model (which party sees what), architecture and known gaps. The jury should be able to run the project just by following the README.
Demo video: 2 to 5 minutes. Upload it wherever you like (YouTube, Vimeo, Loom, Google Drive, etc.); the only requirement is that the link opens publicly without signing in. The system checks the link when you submit. Show the screens of different parties in the video to make clear who sees what.
Short description: the problem, the solution, why you use Canton and the target user.
Category: your project's area. Shown next to the project in the results.
Declarations: whether there is pre-existing code, and whether AI was used.
Network: LocalNet or DevNet. If you used DevNet, your Party IDs and a sample contract ID.
Optional: a live demo link, a presentation file and your project's official links (such as its website or X account).
Evaluation
How are projects evaluated?
Evaluation has two steps: the organizer runs the pre-check, then the jury scores projects online. There is no live final; winners are announced based on the jury scores.
1. Pre-check
The project runs on Canton and contains real Daml contracts.
The repo is public and can be run with the README.
All parts of the submission are complete and open.
The organizer runs the pre-check. Projects that don't pass are not scored; the team is told what is missing and why.
2. Scoring
Criterion
Points
The jury's question
Problem and value
20
Is it a real problem, and why now?
Need for Canton and privacy model
20
Would the product work without Canton? Who sees what, and is it designed correctly?
MVP and technical quality
25
Does it work end to end, does it have tests, is the code clean?
Target users and validation
15
Who uses it, who pays, is there evidence?
Go-to-market
10
How will it find its first users?
Presentation
10
Is it clear and convincing?
Total
100
3. Fair evaluation
At least 3 judges score every project. Each criterion is scored from 1 to 5 on a scale defined with examples, and each project gets a short comment.
Differences between strict and generous judges are balanced automatically: each judge's scores are adjusted relative to their own average.
If the judges' scores differ a lot, a fourth judge is assigned to the project.
Judges never score their own team; the system blocks this automatically.
In a tie, the project with the higher "Need for Canton" and then "MVP" score goes ahead. There is no draw.
4. Results
Winners are announced in one overall ranking, regardless of category. The category is shown next to the project.
How many projects receive prizes is announced together with the prize pool.
All scores and jury comments are published openly with the results. Each team sees its detailed score in its panel.
Prizes
Prizes and beyond
Overall ranking prizes
Winners are announced in one overall ranking, regardless of category. The top-scoring projects receive prizes; their category is shown next to them.
Grant path
Strong projects are referred to the Canton Foundation Grants Program and get guidance through the application.
The prize pool and how many projects receive prizes are announced before the building period starts. There are no separate sponsor prizes; all prizes follow the overall ranking.
Prizes are paid by the Canton Foundation.
The prize is paid to the team lead; splitting it within the team is the team's responsibility. A member who leaves the team cannot claim a share.
Winners are asked for identity and eligibility information before payment. Only winners are asked for it.
Prizes are paid within 30 days of the results. The payment status is shown in the team's panel.
A team that doesn't complete the prize claim form within 30 days loses its prize.
Any taxes on the prize are the winner's responsibility, under the rules of the country where they live.
Jury guide
For jury members
Jury members do the whole evaluation on this site. No setup is needed; every project is reviewed on one screen.
Invitation: The organizer sends you an email invitation. You set your password from the link, sign in and choose your areas of expertise.
Waiting: Projects are hidden until the deadline.
Assignment: Once submissions close and the organizer finishes the pre-check, projects are assigned to you automatically and you get an email. 3 judges review each project and, where possible, the system assigns a relevant expert to each one; with 7 judges, each judge gets about 20 projects.
Review: For each project, the video, the repo (as of the deadline), README, description and demo link are on one screen. You don't need to set up the project on your computer; the organizer checks in the pre-check that it runs. You can report a link that won't open with one click.
Scoring: You score each criterion from 1 to 5 and write a short comment. Your scores are saved automatically and you see your progress (for example 7/20) on screen.
Timing: During the evaluation you get reminders at the start, in the middle and 24 hours before the end.
The jury list is published on this site with names and organizations. Jury members don't share projects or scores until the results are announced.
Code of conduct
A safe space for everyone
These rules apply to everyone, including participants, jury members, mentors, sponsors and organizers; they also cover the Telegram groups and every area of the site.
Treat everyone with respect. Harassment, discrimination, insults and threats are not accepted.
Don't share anyone's personal information without permission.
Don't share spam, unsolicited ads or investment advice.
Respect other people's work; don't copy code or ideas.
Violations can lead to a warning, removal from the group or disqualification.
To report a problem: ferhat@hacktrail.cc. Reports are kept confidential.
Privacy
How is your data used?
What we collect: full name, email, country, GitHub and optional Telegram username, experience level, interests, team and submission details.
What for: to receive your application, match you with your team, send you emails about the process and evaluate your project.
Who sees it: the organizer and the jury members assigned to you. Your teammates only see your team details. Only your submitted project, team name and results are public. If you agreed, your profile (name, country, GitHub, experience) is shared with the main sponsors after the hackathon; you can withdraw this consent any time in your panel.
What we don't ask for: the application does not ask for ID, phone, address or wallet details. These are only requested from prize-winning teams, for payment.
How long: data of participants who don't win is deleted 12 months after the event ends. Payment records are kept for the legally required period.
Your rights: to see, correct or delete your data, write to ferhat@hacktrail.cc. You get a reply within 30 days.
Cookies: the site only uses cookies it needs to work (language choice and session). There are no advertising or tracking cookies.
Visit statistics: we count which pages are visited anonymously, without cookies and without identifying you (Vercel Web Analytics).
Data is stored on servers in Europe and the US run by the service providers that operate the site (hosting, database, email).
Map data: mledoze/countries (ODbL)
FAQ
All questions
If your question isn't here, ask the HackTrail Assistant or write in our Telegram group.
Joining
Is there a fee to join?
No. Joining is completely free and you don't need to buy any product or token.
Who can take part?
Anyone aged 18 or over, from anywhere in the world, can take part. Organizers, jury members and mentors cannot receive prizes.
Can I take part on my own?
Yes. Choose "Solo" when you apply. You can still join a team before the team lock if you want.
How do I form my team?
Choose "As a team" when you apply and enter the team name. Your panel gives you your own invite link; send it to your friends. Each member submits their own application. A team has up to 5 people.
Introduce yourself briefly in our Telegram group, with the skills you are looking for. Taking part solo is completely fine too.
Can I leave the team or add new members?
Yes, until the team lock. After the lock no new members can join; leaving is still possible. The team lock is 3 days before the deadline.
Can I be in more than one team?
No. Everyone can be in only one team, and each team submits one project.
Can I change my details after applying?
Yes. You can update your profile in your panel at any time.
Technical
Do I need Canton or Daml experience?
No. The Developer Hub takes you step by step from zero to a working Daml contract. If you have Ethereum or other chain experience, there are learning paths for you too.
For a local environment with CN Quickstart, at least 16 GB RAM, 4 cores and 50 GB of free disk are recommended. Windows needs WSL 2. For simpler projects the Daml SDK (dpm) alone is enough and needs far fewer resources.
Does my project have to run on DevNet or MainNet?
No. Projects running on LocalNet on your own computer are valid. DevNet is optional.
Which wallet should I use?
Any Canton-compatible wallet can be used. The Developer Hub includes a connection example with Loop Wallet.
Can I use a ready-made template or pre-existing code?
Open-source libraries and official templates are allowed. You can use code you wrote earlier, but you must declare it in the submission form. The jury only scores work done during the building period.
Are AI tools allowed?
Yes. If you used them, say so in the submission form. There is also an official MCP server for the Canton docs; the link is in the Developer Hub.
Which programming languages can I use?
Contracts are written in Daml. You can use any language for the backend and frontend; the official SDKs are for JavaScript/TypeScript and Java.
Submission and evaluation
What do I need to submit?
A public GitHub repo, README, a 2 to 5 minute demo video, a short description, category and declarations.
No. For a transparent evaluation the repo must be public and carry an open-source license.
Can I edit after submitting?
You can edit as much as you like until the deadline. At the deadline the current state of your repo is recorded; later changes are not scored.
What happens if I miss the deadline?
The system closes automatically at the deadline. If you have a technical problem before the deadline, use the "Report a problem" button in your panel; extra time can only be considered for recorded problems.
Which time zone are the times in?
All times are shown in Istanbul time (UTC+3) and UTC. The countdown in your panel follows your own time.
How are projects scored?
At least 3 judges score every project out of 100 using the 6 published criteria. Differences between judges are balanced automatically.
No. Winners are announced in one overall ranking, based on the jury's online scores.
Will I see my score and the jury comments?
Yes. Each team sees its detailed score and all jury comments in its panel. Results are published openly.
Prizes
What are the prizes?
Overall ranking prizes and referral to the Canton Foundation grant program. There are no separate sponsor prizes. Winners are announced by overall ranking, not by category. The prize pool is announced before the building period starts.
How and when are prizes paid?
Within 30 days of the results, after identity and eligibility checks, to the team lead. The payment status is shown in your team's panel.
Do I have to provide ID?
Not when you apply. ID and payment details are only requested from prize-winning teams.
Can I win more than one prize?
No. Prizes follow the overall ranking; each project receives at most one prize.
Other
I want to become a sponsor.
For sponsorship, send a short email about your company to ferhat@hacktrail.cc and we'll send you our sponsorship file.
For technical questions about Canton and Daml, the official Canton forum is the fastest way to get an answer. All official support now happens on the forum.