What Colosseum's form actually asks

The form doesn't save you from a blank page. Half its required fields have a hard character limit, and writing a business model to a 500-character ceiling for the first time, live, costs more time than drafting it in a doc beforehand and pasting it in once it fits.

Anyone with your project link sees these, including anyone you send it to before judging starts. Write them for a stranger, not for a judge.

• Project name.
• Brief description, up to 500 characters. The one-liner from your playbook belongs here, unchanged.
• Project website, optional.
• Product category. It's fine if the project spans several; pick the one closest to what it actually does.
• Where your team is primarily based.
• Project logo or graphic. JPEG, PNG, WEBP or GIF, up to 20MB before compression, stored at 0.5MB.
• GitHub link, a direct link to the repository, not an org or profile page. It can stay private if you share access with hackathon@colosseum.com.
• Pitch video, up to 2 minutes. Introduce the team, what you're building, and why you're the people to build it. Colosseum's own note: nothing fancy required, they're interested in how you think and communicate.
• X profile.

Not on the public page, but not private either. Every judge reads these before they watch anything.

• What are you building, and who is it for? Up to 1,000 characters.
• Why did you decide to build this, and why build it now? Up to 1,000 characters.
• What technologies are you using or integrating with? Colosseum asks for notable developer tools and AI tools too, not just the chain stack.
• Which chains does your product use? Select every chain actually integrated, not just the one you'd claim in a pitch.
• How does your product use these chains? Up to 500 characters, and the question a forced integration fails first.
• Is your project a mobile-focused dApp?
• A team Telegram contact. This is how Colosseum reaches you for prize distribution or an accelerator interview, so it needs to be someone who actually checks it.
• Did anyone not listed on the team do meaningful work on this project? Up to 600 characters. Answer honestly; it's a compliance question, not a trap.
• Anything else judges should know that isn't captured above? Up to 500 characters, optional but rarely wasted.
• Demo video, up to 3 minutes, a separate upload from the pitch video. Should show the live product, not a slide deck and not a code walkthrough. You choose whether it also shows on the public page.
• Live product link and access instructions, if judges need credentials to get in.

Colosseum's own label for this tab is accurate: these answers stay private to organizers and the Colosseum team. They're also required, whether or not you want the accelerator, because this tab is literally how Colosseum decides who gets a look for it.

• How do you know people actually need, or will need, this product? Up to 1,000 characters.
• How far along are you? Do you have users? Be as specific as possible, up to 1,000 characters.
• Who else is building in this space, and what do you think they're getting wrong? Up to 1,000 characters.
• How do you make money, or how do you plan to? Up to 500 characters.
• How long have you each been working on this? Have you been working on it full time? Up to 500 characters.
• Where is each team member currently based, and do you work in person together? Note whether that would change after funding.

Then four yes-or-no questions: whether you've formed a legal entity, taken any investment, are currently fundraising, and have a live token.

1. 01Draft every answer above in a doc first, to the character limits given. Writing to a hard ceiling is a different task from writing freely, and it's faster to do once, offline.
2. 02Have someone outside the team open the GitHub link, the demo video and the pitch video before you submit. The same rule as the repo: a link that only works for you doesn't work.
3. 03Decide your chain list before you fill in "how does your product use these chains". That answer is where a forced integration gets caught first.
4. 04If you're not chasing the accelerator this cycle, still answer Tier 3 properly. It's required to submit, and a thin answer costs nothing to avoid.