1.All submissions need to deploy on the Injective Testnet or Mainnet and include the following

• Project Description

a)Name and summary of the project;

b)Name of team member(s) and roles;

c)An overview of what problem is being addressed and how the team resolves the identified problem through this creation;

d)The design process behind the project;

e)The value this project brings to the Injective Ecosystem

• A demo video illustrating the project
• Github repo link
  2. Single entry submission: Participants may submit a maximum of ONE project by the hackathon deadline.
  3. Submission Materials

All submission materials must be in English, including the demonstration video, text description, and testing instructions, as well as any other materials submitted.

4.Disclosure

• Projects submitted to other hackathons or challenges need to be disclosed in the submission or README of the project.
• Our judges will evaluate project submissions based on how the team implements their features and the uniqueness of the application.

5.Developer Resources

• Dev Tools: https://docs.injective.network/develop/tools/
• Dev Guides: https://docs.injective.network/develop/guides/
• Injective Modules: https://docs.injective.network/develop/modules/
• Cosmos SDK Modules: https://docs.injective.network/develop/modules/Core/auth/
• CosmWasm Smart Contracts: https://docs.injective.network/develop/guides/cosmwasm-dapps/
• Injective Workshops: https://www.youtube.com/playlist?list=PLTS_stt4XpDC3isu2cnBGpfviy3y7_Egu
• Hackathon Idea: https://injective.notion.site/Injective-Hackathon-Ideas-410b9575e0bf497f801014e3f07ce537

Once all submissions are collected, Injective will distribute a list to the judges for evaluation. Teams and individuals who submitted projects will be evaluated on the following criteria:

• Project Sustainability

Can this project continue to grow and evolve?

• Design

Is the user experience and design of the project well thought out?

• Security

Is the contract properly tested?

Have relevant test cases been covered with unit tests?

• Originality and Innovation

How creative and unique is the project?

• Mass Usability

Is the idea feasible?

How adaptable is it across other ecosystems and integrations?

• Ecosystem Impact

How impactful and useful is the submission for the larger Injective ecosystem?

• Technical Complexity

Does the interaction with Injective demonstrate quality software development?

How well was the idea executed by the developer?

Does the project work as designed?

What is the level of skill or knowledge required to build the project?