Dates

  • Hackathon: June 15–20, on site at Futura
  • Mandatory sessions: workshop (June 16, 10 AM), kick-off (June 16, 12 PM), and award ceremony (June 20, 8 PM)
  • Submission deadline: June 20, 9 AM
  • Award ceremony: June 20, 3 PM

Eligibility

  • Participation is limited to accepted applicants and Futura ticket holders.
  • Teams of 1–3 members. Each person may join only one team and contribute to only one submission.
  • Accepted hackers confirm their spot with a refundable deposit. The deposit is refunded in full after attending the mandatory sessions and submitting a project by the deadline; it is forfeited otherwise.

Project and Submission Requirements

  • Projects must be created during the hackathon (June 16 - 20). Use of existing open-source libraries and public APIs is allowed; submitting pre-built projects is grounds for disqualification.
  • Projects must use MPP and/or run on Tempo.
  • One submission per team, in one category (Applications or Infrastructure).
  • A complete submission includes: project name and category, short description, repository link (public or with judge access, README with setup instructions), demo video (max 3 minutes), and all team members added on Devpost.
  • Submissions close June 20, 9 AM. Late or incomplete submissions are not judged.

Prizes

Category 1st place 2nd place
Applications $5,000 $2,500
Infrastructure $5,000 $2,500
  • Prizes are paid to the team, split among members at the team's discretion.
  • Teams are only eligible to win if they are present at the award ceremony (June 20, 3 PM).

Judging Criteria and Winner Selection

  • Projects are judged by the Tempo team, per category.
  • Criteria: TBD
  • Judges' decisions are final.

 

Other

  • Teams retain full ownership of what they build. By submitting, teams grant the organizers and Tempo the right to feature the project (name, description, video) in event communications.
  • The Futura code of conduct applies. Organizers may disqualify participants for violations of these rules or the code of conduct.
  • Organizers may amend these rules for fairness or logistics; material changes will be announced in the hackathon's Updates.