Launched Product & Usage Quality

Evaluates whether the main product is live, stable, and supports core use-cases with real users.

Methodology

Product Status Levels

Level	Description
TestNet	Product in testing phase, not production ready
MainNet	Live on mainnet, accessible to users
MainNet-audited	Live and security audited
Full Dev Docs	Comprehensive developer documentation

What We Look For

Evaluation Criteria:

• TestNet vs MainNet status
• Whether the product is audited by a reputable firm
• Developer documentation quality and completeness
• Real user activity on core flows
• Product stability and uptime

Data Sources:

Source Type	Examples
Primary	Live app/dapp, mobile app listing, on-chain contract usage
Secondary	Docs onboarding flow, UX reviews, third-party walkthroughs

Guide

Finding Information

Step 1: Determine Product Status

Identify where your product is deployed:

• TestNet only
• MainNet (which chain?)
• Multiple chains

Step 2: Check for Security Audit

If on MainNet, verify if audited:

• Audit report from reputable firm (Trail of Bits, OpenZeppelin, Certora, etc.)
• Public audit results
• Date of audit

Step 3: Evaluate Documentation

Review your developer documentation:

• Getting started guide
• API reference
• Code examples
• Integration tutorials
• Architecture overview

Submitting Evidence

When submitting product information:

1. Product URL:

   • Live application URL
   • dApp URL
   • Mobile app store links

2. Contract Information (if applicable):

   • Deployed contract addresses
   • Block explorer links
   • Chain(s) deployed on

3. Audit Evidence:

   • Link to audit report(s)
   • Auditing firm name
   • Date completed

4. Documentation:

   • Developer docs URL
   • Getting started guide
   • API reference

5. Usage Evidence:

   • Active user count (if available)
   • Transaction volume
   • Key metrics showing real usage