BELOW IS THE TEMPLATE FOR THE HACKATHON SUBMISSION

Project Name

[Insert your project name]

Team Members

• [Name 1] - [Role/Responsibility]
• [Name 2] - [Role/Responsibility]
• [Name 3] - [Role/Responsibility]
• Contact Information: [Email/Discord/LinkedIn]

Development Guidelines

• Fork the UI template: https://github.com/openguild-labs/dotui
• Follow the Polkadot brand hub: https://polkadot.com/community/brand-hub

Requirement Checklist

Hackathon submissions MUST follow these rules to reach the entry requirements of the hackathon. The project can be quality, but if these requirements are not satisfied or rules are violated, it will be disqualified from the competition.

🔴 Note: These requirements are applied for all track submission.

• Because projects will be developed on Polkadot Hub (https://contracts.polkadot.io/), all projects UI need to follow the design guidelines of Polkadot.
• All projects must be open-source and the organizer team has the authority to fork the project codebase and organized under the organizer’s Github organization - OpenGuild Labs.
  • These archived codebase is for the purpose of common good projects and will not be used for commercial purpose.
  • Only the submitted codebase for final judgement will be archived.
• The hackathon is open for innovation on top of existing open-source codebase. However, project that forks from the existing open-source projects on the market with more than 70% codebase similarities will be disqualified immediately.
• All project team members must verify their identity on OpenGuild Discord channel (which takes 2 minutes) following the guide OpenGuild - Discord Guidelines
• Projects does not need to be developed during the hackathon, it can be past hackathon projects as far as it is quality and had not been granted by the past hackathon or the ecosystem fund yet. (from Polkadot ecosystem under one year)
• Valid commit history of the projects are required for this hackathon as well. It is a proof of contribution of your team to the projects.
  • The commit history must indicates the contribution of the team during the hackathon. Only the contribution made during the hackathon is counted towards the final score.

Project Description

What does your project do?

[Provide a concise overview of your project. Explain the problem it solves and the solution your project provides.]

Inspiration

[What inspired you to create this project? Share your motivation and any relevant background.]

Technical Stack

• Languages and Frameworks:
  [List the primary programming languages, frameworks, and libraries used.]
• Blockchain/Protocol:
  [Describe which blockchain (e.g., Polkadot, Ethereum, etc.) or protocol your project integrates with and how.]
• Tools and APIs:
  [Include tools or APIs used in your project development.]

Features

• Feature 1: [Short description]
• Feature 2: [Short description]
• Feature 3: [Short description]

How It Works

Architecture

[Provide a high-level explanation of your project's architecture. Attach diagrams or flowcharts if applicable.]

Demo Instructions

[Provide step-by-step instructions on how to use or test your project. Include any setup steps, such as running a local server or connecting to a blockchain.]

Challenges

What challenges did you face?

[Explain the difficulties you encountered during development and how you overcame them.]

Future Development

What’s next for your project?

[Outline plans for future development, features you would like to add, or areas for improvement.]

Submission Details

• GitHub Repository:
  [Provide the link to your GitHub repo]
• Live Demo:
  [Provide the link to your deployed project or a recorded demo video]
• Documentation:
  [Link to any additional documentation, such as a detailed user guide, API docs, etc.]
• Presentation Slides:
  [Link to your project’s presentation slides, if applicable.]

Acknowledgments

[Recognize any resources, mentors, or open-source projects that helped in your development process.]