BlockDAG Hackathon Rules

BlockDAG Hackathon Rules

Welcome to the BlockDAG Hackathon, hosted on HackerEarth! This document outlines the rules, requirements, and best practices to ensure a fair and productive environment for all participants. All submissions must comply with these rules to be eligible for judging and prizes.

🧾 General Rules

• Eligibility: Open to individuals 18 years or older. Teams may consist of 1–5 participants.

• Original Work: All projects must be started and completed during the official hackathon period. Pre-existing code or solutions must be declared and approved by the organizers.

• Code of Conduct: All participants must adhere to the HackerEarth Code of Conduct and maintain a respectful and inclusive environment.

🧠 Submission Requirements

Each team must submit the following:

1. GitHub Repository

   • Must be public at the time of judging.

   • Include a README.md with:

     • Project overview and purpose

     • Installation steps

     • Usage instructions

     • License (preferably MIT or Apache 2.0)

   • All major logic must be written by the team during the hackathon.

2. Working Demo

   • A live or recorded video (2–5 minutes) demonstrating the working functionality.

   • Should clearly show interaction with deployed smart contracts (if applicable).

3. Pitch Deck or Slides (Optional but Recommended)

   • Overview of the problem, solution, and implementation.

   • Potential use case or go-to-market strategy (if relevant).

4. Deployed Smart Contracts

   • Deploy to BlockDAG testnet (e.g., Primordial )

   • Include contract addresses in the submission.

   • Source code must be verified on a block explorer where possible.

🔐 Smart Contract Best Practices

To ensure code quality and EVM compatibility:

• Follow security best practices (use OpenZeppelin libraries where appropriate).

• Use Solidity version ^0.8.0 or higher to avoid issues with under/overflow.

• Include a test suite using Hardhat, Foundry, or Truffle.

• All state-changing contract functions must be covered by unit tests.

• Use .env for sensitive keys and avoid hardcoding them in source code.

📊 Judging Criteria

Projects will be judged based on the following:

Criterion	Description
Technical Excellence	Code quality, smart contract design, and infrastructure decisions
Use of BlockDAG Tech	How well the project integrates BlockDAG’s tools, APIs, or ecosystem assets
Innovation	Creativity and originality of the idea
Utility	Real-world applicability and potential impact
UX/UI	Interface design, usability, and overall polish
Completeness	How well the final product is delivered, tested, and documented

🚫 Disqualifications

Submissions will be disqualified for:

• Plagiarism or reuse of another team’s code.

• Submitting after the deadline.

• Failure to meet the basic submission requirements.

🗓️ Timeline

Detailed timeline, submission deadlines, and judging schedule will be published on the HackerEarth Hackathon page.

📞 Support

Join the official Discord for support, team formation, and announcements: [Discord Invite Link]

---

Let's build something revolutionary together. Good luck!