General Eligibility: Participants must register by the official deadline which is 16.10.2023 and comply with all hackathon guidelines and terms of service.

Track Selection: Each team must clearly state to which track they are submitting their project to. Same project cannot apply to multiple tracks, although a team can apply with different project to several tracks. Also team members can be part of several projects submitted to other tracks.

Number of submissions: Projects that were developed prior for another event or have been used in other hackathons are not eligible.

Maximum Team Size: All teams must consist of no more than six members.

Web3 Integration: All projects, irrespective of their track, must showcase a web3 integration component with MultiversX Blockchain or MultiversX core products (xPortal, xMoney). For Mobile Apps and Gaming & Metaverse tracks, the portion of the codebase demonstrating web3 integration must be publicly available, even if the entire codebase isn't.

Submission rules:

• Project Description: Every project should provide a detailed description outlining its purpose, functionality, and unique features.
• Presentation Video: Teams must submit a video showcasing their project. This video will be played on the secondary stage and, if the project wins first prize, on the main stage as well.Business Case: Submissions should include a clear business case, highlighting the problem they aim to solve, their target market, and how their solution fits into the existing market landscape.
• Roadmap: A roadmap detailing the future plans and milestones for the project is mandatory. This should include both short-term and long-term goals.
• Functional Product: It is vital for every project to have a functional product, be it a Minimum Viable Product (MVP) or a prototype, to be eligible for jury judgment. Consistent updates on the project's status can significantly assist the jury in the evaluation process.
• Continual Updates: Teams are encouraged to regularly update the hackathon organizers and community on their progress. This transparency will simplify the evaluation process for the jury, ensuring a more accurate assessment of each project's capabilities and potential.

Jury Evaluation and Quality Threshold:

• A project must be evaluated by a minimum of three jury members to ensure a comprehensive review.
• If a track has only one project submission, it doesn't automatically secure a first-place prize. The project will be judged based on a predetermined quality threshold. For instance, projects should score at least 70 out of 100 based on the judging criteria to be considered for prizes.
• Criteria will include innovation, usability, relevance to the track, scalability, and technical execution. Projects respecting one of the ideas will get extra points.

Code Submission, Documentation, and Early-stage Projects:

• Full Code Submission: All projects, except for Mobile Apps and Gaming & Metaverse tracks, must make their entire codebase publicly available for the jury's review. Other projects from the other track may be eligible for private code but this has to be communicated to the organizing team as soon as possible.
• Mobile Apps and Gaming & Metaverse Exceptions: Recognizing that distinctive app or game engines are what make these projects unique and that a top-tier app or game cannot be developed in just 30 days, we allow these projects to only disclose the portion of the codebase that demonstrates web3 integration. We believe that the essence of an app or game is often in its unique code, and that's what makes it stand out in the market.
• Early-stage Projects: We welcome submissions from early-stage projects across all tracks. Such projects need to adhere to the following:
  • The project must not have been submitted to any other hackathon previously.
  • The project should not have secured any external investment.
  • The project must not have any published tokenomics or token launched.
  • Before registration, the project must clearly state its current status and publicly declare what they aim to develop or implement during the hackathon. This transparency ensures that the jury knows precisely what to evaluate.
• Documentation Requirement: All projects must submit accompanying documentation that describes the problem, solution, setup instructions, and roles and contributions of each team member.

Ethical Compliance: Projects should not promote hate, discrimination, or any form of harm. They should also ensure compliance with data protection standards and prioritize user privacy.