UX:

• Does your project’s stack actively contribute to improving UX in a meaningful way?
• Is it easy to use for new users?
• When using your project, do the three S’s ‘seamless’, ‘smooth’ and ‘simple’ come to mind?

Code:

• Is the code clean, easy-to-read with documentation, basic tests (if applicable) and forkable with a proper and concise README?
• Can the code run with a testnet deployment successfully and without hiccups?

Product Market Fit:

• Does your project satisfy a current gap in the market when it comes to improving web3’s mass adoption?
• Is your project solving this product market fit in a unique and creative way?
• Does your project solve a pet peeve of yours? If so, explain what it is and why? Note: Sometimes the best solutions are built from a user’s own frustration at the gap in the market.