Rules

 

Dates

  • Project Start Date: November 9, 12:01 AM THA

  • Submission Deadline: November 17, 10:00 AM THA

  • Winners Announced: November 23, 12:01 AM THA

Eligibility

  • Aleo Grant Recipients: Projects that previously received an Aleo grant are not eligible.

  • Novelty Requirement: Projects should be novel and new to the Aleo ecosystem.

  • Team Composition: Open to individuals or teams. All team members must meet the eligibility criteria if participating as a team. Participants must be approved members of the Aleo Hacker House Thailand 24' or approved guests.

  • No Pre-Built Solutions: Eligible projects must be built during the hackathon only to ensure fairness.

Project and Submission Requirements

  • Project Timeline: Work on projects can begin as early as November 9, 2024. All projects must be submitted via DevPost by the deadline.

  • Submission Components: Complete project, presentation, GitHub repository, and README file.

Code of Conduct (For In-Person Participation) A comprehensive code of conduct will ensure a safe, respectful, and inclusive environment for all participants. This will be shared with all attendees before the event.

Legal Considerations Participants should consult their legal advisors to understand their rights and obligations. Hackathon organizers are recommended to consult a lawyer to finalize the rules and ensure compliance with all applicable laws and regulations. Aleo Tokens (rewards) will be paid after the mainnet. All US residents will be required to have a holding period. Payments will be made within 30 business days of the hackathon end date. If there are not enough qualified projects for the initial prize, consolation prizes will be awarded at the discretion of the judges.

Judging Criteria and Winner Selection

Innovation and Creativity

  • Assessing how the project introduces fresh ideas and solutions using zk proofs on the Aleo Blockchain.

  • Innovation in leveraging zk technology for novel applications.

Technical Implementation

  • Evaluating project functionality, security, and code quality, including its integration with the Aleo Blockchain.

  • Focus on robustness, efficiency, and scalability of the solution.

User Experience

  • Examining user-friendliness, accessibility, and the navigational ease of the project's interface, considering the time constraints of the hackathon.

  • Importance of intuitive design and seamless interaction.

Practicality and Real-World Use Case

  • Gauging the project's real-world applicability and potential impact on a global audience.

  • Relevance and potential for implementation in practical scenarios.

Bounty Implementation

  • Ensuring bounties are used correctly, in accordance with their rules and adequately explained to participants.

  • Proper utilization of resources and alignment with hackathon objectives.

zk Proof Usage

  • Analyzing the effective use of zk proofs for scalability, privacy, and computational efficiency.

  • Emphasis on innovative applications of zk proofs for enhancing privacy and security.