<aside> 💡

Welcome, Babylon Builders! This guide addresses key questions about project judging for Hackathons and Hacker Houses. For further clarification, contact us on the public Babylon developer Discord channel or event-specific support channels.

</aside>

Judging Criteria

All projects will be assessed on:

🤩 Innovation

Does it have unique and novel features or combine features of other projects in a unique and novel way? Does it solve a new problem?

🚀 Usefulness

Does it fill a gap in the web3 space, and have the potential to be used by a large, growing and diverse audience or market?

🤖 Technology

Is the solution or code elegant, clean, and technically interesting? Does the project cover complete workflows?

🪄 Integration

How well and important is Babylon’s tech in your project? Does it allow a seamless integration with Babylon?

✨Presentation & Pitch

How is the UX/UI/DX? Is it easy to use? If targeting developer users, is the experience smooth and intuitive? Does the visual design delight you?

*Event-specific deviations may occur. Contact the event organizer if any questions.

Submission Guidelines

All prize submissions must include:

Project Description

• Project name and summary
• Team members' names and contact information (e.g., GitHub handle, email, Telegram)
• Detailed explanation of Babylon Chain usage, including:
  • Links to relevant source code files & functions
  • Addresses of smart contracts deployed on devnet

Public Source Code Repo

• Provide a link to a public GitHub or GitLab repository
• Include a comprehensive README with:
  • Clear project description
  • "Technologies Used" section highlighting our tech
  • Link to working demo / testing guide

Showcase (Optional)

• 2-3 minute video presenting the idea and demonstrating Babylon usage
• Specify targeted tracks in your submission

Eligibility Requirements

1. Open-Source Mandate: All submitted projects must be open-sourced. Exceptions require prior approval from the judging team.

2. Project Originality: Resubmission of previously entered projects without significant improvements will result in disqualification.

3. Conflict of Interest: Projects with existing Babylon grants or investments are ineligible if the hackathon scope overlaps with prior agreements.

4. Event Specific Development: Only projects or features developed specifically for this event will be considered. New features should be in separate branches with a clean commit history.

5. Readable Submissions: Broken repository links or demo materials may lead to disqualification as judging timeline does not allow back & forth communication with hackers.

6. Compliance with Sanctions: Prize disbursements are subject to U.S. Treasury sanctions regulations without limits. The full list is available here. Participant eligibility may vary based on country of residence. Teams must provide necessary information for legal clearance prior to payment processing.

   Payment Restricted Countries

<aside> 💡

This page is a living document which means it is subject to changes from time to time, please always refresh for the latest information before you code.

</aside>

Looking for the next Babylon Developer event? Visit #buildonbabylon