Germany joins the Crypto World’s Fair.

Your one-liner should explain what the product does in plain English. Your project blurb should add who it is for and why it matters.

Ask someone unfamiliar with the project to explain it back to you. Avoid leading with buzzwords or a list of technologies.

Explain whose problem you are solving, what evidence supports demand, how you plan to reach users, and how the product could become sustainable.

Include genuine feedback or traction where available and clearly label assumptions. A large market-size number alone does not demonstrate demand for your product.

Use the presentation video to explain what you are building, why it matters, and why your team is suited to build it.

Have someone review the story before recording. If you use slides, make sure they are readable. Watch the uploaded version to check the audio, playback, and final length.

Test the main product flow and provide a working product link. For developer tools or infrastructure, provide a reproducible example instead.

Include test credentials where necessary and keep the relevant services running during judging. Avoid broken deployments, inaccessible environments, or a waitlist in place of a working product.

The product demo should be separate from the presentation video. Demonstrate the core product flow and provide enough technical context for judges to understand how it works.

Show the actual product rather than recording a second pitch. Clearly identify anything that is mocked, planned, or unfinished. The demo must be no longer than three minutes.

Link the correct repository, push the latest relevant code, and explain the setup and any important branches in the README.

Private repositories are allowed, but access must be granted to [email protected]. Do not assume judges will contact you after discovering that the repository is locked.

Every teammate must register for the current competition, and the team leader must include the complete team in the project submission.

Check that everyone’s details, background, and role are accurate. Do not assume that having an existing Colosseum account means someone is registered for the current hackathon.

Check the team location in Colosseum before submitting. Registering through the Germany referral link does not automatically set the country.

Germany must be selected for the team to be recognized as Germany-based and to qualify for the regional Earn track.

Review the current eligibility rules, including age, restricted jurisdictions, employer or contractual obligations, previous work, and the one-team/one-product restriction.

Disclose relevant work completed before the hackathon and clearly distinguish it from work completed during the competition. Complete every required field accurately; all submitted content must be in English.

Test the exact links pasted into the submission form—not only the versions saved in your bookmarks.

Open product, video, repository, and document links while logged out. Verify access to private repositories separately. Ideally, ask someone outside the team to check all materials as well.

The team leader must complete the final submission before the deadline.

Review the project information and uploaded materials, confirm that the entry shows as submitted, and save the confirmation. Do not stop after registering, creating a project, or saving a draft. Afterwards, monitor the contact inbox included in the submission.

Submit the same project to the Superteam Germany listing on Earn in addition to your Colosseum submission.

The project must be built on Solana, comply with the global hackathon rules, and meet the regional eligibility requirements, including having Germany selected as the country. Check the Earn deadline and confirm the separate submission.

Teams building for the Machine Economy can also submit their project separately to the optional peaq Germany side track.