← 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
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.

📮

Two bounties want a second form. Arkiv reads submissions from its own page: fill in the Arkiv bounty submission as well, or their team never sees your project. Team1 does the same on their side. Everyone else is covered by the form above.

One submission per team, filled in by the team leader. You can edit your answers until the deadline, so submit early and refine later.

The form

What it asks

Read them now, so that on Sunday morning you are pasting answers, not writing them. It asks for your email first.

  1. Team name, then team members, the name of every one of you.
  2. Team leader, and the Telegram handle of that person. It has to stay responsive during the judging session: if judges have a question and nobody answers, that is your problem.
  3. Project name and what it does, in one line. That line is the sentence a judge reads before opening your repository.
  4. What you built, a few lines: what it does, how it works, what is actually running.
  5. Public repository. It must be open now, and it must stay open for 4 weeks.
  6. Demo video, 3 minutes maximum, and the link has to work without login.
  7. Contract addresses, if your project deploys anything on chain. Optional.
  8. Pre-existing project? If yes, spell out what already existed and what you built during the weekend.
  9. Sponsor bounties you are applying to. Tick every one that applies.
☑️

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.