← Hacker Manual

ETHRome 2026

Submissions

One Google Form, one deadline. This page tells you exactly what the form asks and when it closes.

Sunday 10:00Deadline, 13 September, Europe/Rome
PlatformA Google Form
3 min maxDemo video length
Public repoOpen, and staying open for 4 weeks

Submission runs on a Google Form. You open it, fill it in once, and you are done. Everything the judges need is in that one page.

The form closes on Sunday 13 September at 10:00 (Europe/Rome), the same moment hacking ends. Submit early, then keep editing until the deadline if you need to.

๐Ÿ”—

The Google Form link lands here before the event, and goes out at the same time in the Telegram group. Bookmark this page: it is where you will come back to submit.

TBD Google Form link, published before the event.

The form

What it asks

Nine fields. Read them now, so that on Sunday morning you are pasting answers, not writing them.

  1. Team name and the name of every member.
  2. Team leader, plus a Telegram contact that stays responsive during the judging session. If judges have a question and nobody answers, that is your problem.
  3. Project name and a few lines on what you built.
  4. What it does, in one line. The sentence a judge reads before opening your repository.
  5. Sponsor bounties you are applying to. Tick every one that applies.
  6. Link to the public repository. It must be open, and it must stay open for 4 weeks.
  7. Link to the demo video, 3 minutes maximum.
  8. Contract addresses, if your project deploys anything on chain.
  9. Pre-existing project? If yes, spell out what already existed and what you built during the weekend.
โ˜‘๏ธ

Tick your bounty boxes. Sponsors only look at the projects that selected their bounty. If you do not tick it, you are not in the running, no matter what you built. This is the single most common way teams lose money at a hackathon.

Before you hit submit

Final checklist

Run through this with your team before Sunday morning gets loud.

๐Ÿ’ฌ

Stuck on something the form asks? Write in the Telegram group or to hello@urbe.build before the deadline, not after.