Dates

March 29-30th, 2025

Eligibility

This hackathon is specifically designed for students in the Midwest, but is open to anyone as long as all members are on-site at the venue. Please apply at https://hack.kublockchain.com!

Team Composition

  • Teams can have 1 to 4 participants.
  • All team members must be present at the hackathon venue. Temporary departures are permitted.

Project Rules

  • Teams are allowed to seek advice from organizers, volunteers, sponsors, and other participants.
  • All project development must occur during the hackathon.
  • Teams may start with an idea conceived before the event and may revisit ideas previously worked on, provided no prior code is reused.
  • Use of libraries, frameworks, and open-source code is permitted, but pre-hacking (starting a project early and open-sourcing it to use the code during the hackathon) is prohibited.
  • Projects must adhere to the MLH Code of Conduct. Violations may result in disqualification.

Demos

To qualify for a challenge prize, teams must demo their project to the judges. Incomplete projects or those that encountered issues should still be presented (completion is not part of the judging criteria for general track awards).

Demos

There are two main tracks: (1) The General Track and (2) The No-Code Business Track. Both tracks will adhere to the same project rules as listed above.

  • For The No-Code Business Track, specific deliverable requirements and judging criteria will be given at registration starting at 2pm Saturday, 3/29 at the Burge Union.
  • Judging criteria for The General Track is described below.

Judging Criteria (Coding/General Tack)

1. Blockchain Innovation

  • How effectively does the project leverage blockchain technology? Is the implementation unique or innovative within the web3 space?
  • Does the project utilize advanced blockchain concepts such as smart contracts, tokenomics, or decentralized storage?
  • Does the solution enhance scalability, security, or interoperability in the blockchain ecosystem?

2. Technical Execution

  • Was the problem the team tackled complex or challenging?
  • Did the implementation use creative solutions, multiple components, or novel techniques?
  • Does the technology demonstrate a "wow" factor for technical depth or elegance?

3. User-Centric Design

  • How well-designed is the user experience and interface?
  • Is the project intuitive and accessible for its intended audience, including non-technical users?
  • For blockchain-specific tools, does the design help demystify complex concepts like wallets, dApps, or smart contract interactions?

4. Learning and Growth

  • Did the team explore new areas of blockchain or web3 development?
  • Did they learn and apply new skills, tools, or frameworks during the hackathon?
  • How does the project reflect the team’s effort to grow and experiment outside their comfort zones?

 

Additional Notes

  • Messy or inefficient code will not impact your score; focus on experimentation and learning.
  • Innovativeness of the idea is not a judging criterion; focus on the building and learning process.
  • Projects do not need to solve a specific problem; the goal is learning and enjoyment.

 

Remember, the hackathon is about learning, having fun, and making connections. Focus on these aspects, and let your creativity and passion guide your project development.