Milestone Structure Requirements

See "Milestone Submission Template" Page under RESOURCES Section for complete submission template.

Each milestone submission must include the following mandatory components.

A. Milestone Title

  • Format: M[Number]: [Concise Description]

  • Example: M1: Mainnet Launch with Core DEX Features

  • Max 80 characters

B. Detailed Description

Comprehensive explanation including:

  • What will be delivered

  • Why it matters to the project

  • How it advances the roadmap

  • Dependencies on previous milestones (if any)

Length: 200-500 words

C. Completion Criteria (Critical)

Minimum 3, maximum 8 objective criteria per milestone.

Format:

Examples:

✅ GOOD:

❌ BAD:

D. Evidence Package Requirements

Specify exactly what evidence must be submitted.

For Technical Milestones:

  • Contract addresses with block numbers

  • GitHub repository links with specific commit ranges

  • Deployment transaction hashes

  • API endpoints for verification

  • Screenshots/screen recordings (timestamped, with visible URLs)

For Traction/Metrics Milestones:

  • Data source links (DeFiLlama, Dune Analytics, blockchain explorers)

  • Query/API parameters for reproducibility

  • Time period specification (UTC timezone)

  • Methodology for calculation

For Partnership/Integration Milestones:

  • Official announcement links from both parties

  • Integration test transaction hashes

  • Joint marketing materials (dated)

  • Technical documentation of integration

E. Timeline

  • Deadline: Exact date and time (UTC)

  • Estimated Start Date: When work begins

  • Buffer Period: Recommended 10-20% time buffer

  • Dependencies: List any prerequisite milestones

F. Funding Allocation

  • Percentage of Total Raise: X%

  • Dollar Amount: $XXX,XXX USDC

  • Justification: Brief explanation of why this amount is needed for this milestone

G. Risk Disclosures

Projects must disclose:

  • External dependencies (third-party protocols, services)

  • Technical risks (unaudited code, experimental features)

  • Market risks (requires specific token price/TVL)

  • Regulatory risks (jurisdiction-dependent features)

Format:

Last updated

Was this helpful?