Anything not answered here, email dev@anam145.com. Once your application is confirmed you can also ask in the Discord channels. All times are KST.
No. It is free to enter.
Sep 20, 2026 at 11:59 PM KST — the same moment submissions close. Apply any time before that.
There is no fixed start. The official build period opens on Aug 25, but the deadline is the only fixed point, so how you use the remaining time is up to your team.
Yes. Mark on the application that you would like a team and we help match you through Discord.
Yes. The application asks for two to five sentences on the problem and how you would approach it; it does not have to be a settled plan.
1–5 people. One person cannot be on two teams at once.
Yes, but keep the work and the submission separate for each. The same artefact submitted to two tracks does not count.
Yes. State in the README what you built during this period.
No restrictions. Your team remains responsible for understanding, explaining and validating everything you submit. Disclose material AI-generated components in the README.
Freely — just respect the licence. Submitting code that is not yours as your own is disqualifying.
No. Testing must happen only in environments the organisers provide or explicitly approve. Demo on testnets, with test accounts and de-identified data — never real wallets or real personal data.
A pitch deck (PDF), a demo video and a code repository. Track 02 is the one exception: it accepts an ideathon submission, so only the pitch deck is required there. Details on Submit.
Yes, public at submission time. A private repository cannot be judged and counts as no submission. You may make it private again after judging closes on Sep 25.
You may resubmit as often as you like until the deadline. The final submission is the one judged.
The pitch deck is uploaded as a file, so the upload needs a Google account. Submit from the account of one team member.
Submissions after the deadline are not judged.
Out of 100 points, common to every track — problem definition 25%, security soundness 25%, implementation 20%, verifiability 15%, technical originality and impact 10%, extensibility 5%. Each track supplies its own criteria as the basis for scoring security soundness and verifiability. The table is on Judging & Rules.
Every team is invited to Demo Day and networking. The final presentations are given by the Top 6 Finalists, 15 minutes each.
The Top 6 Finalists are announced on Sep 26, and the winners are decided by the Demo Day judging on Sep 29.
Prizes are awarded on site, so at least one team member must attend to stay eligible.
After deduction of taxes and charges required by applicable law, to one team account. How the team divides it is up to the team.
Your team does. The organisers use it non-exclusively for judging and for event records and promotion; any research or commercial use requires your prior consent.