# Milestone Submission Template

**Instructions**: Complete all sections below. Submit this document along with your full project proposal before community voting begins. Incomplete submissions will be rejected.

***

### Project Information

**Project Name**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Project Category**:

* [ ] DeFi (DEX, Lending, Derivatives, etc.)
* [ ] GameFi
* [ ] Infrastructure (L1, L2, Oracle, etc.)
* [ ] NFT
* [ ] Prediction Markets
* [ ] Other: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Total Fundraise Target**: $\_\_\_\_\_\_\_\_\_\_\_\_\_ USDC

**Project Website**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Project Social Links**:

* Twitter/X: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Discord: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Telegram: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* GitHub: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Team Lead Contact**:

* Name: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Role: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Email: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Telegram: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

### Milestone Roadmap Overview

**Total Number of Milestones**: \_\_\_\_\_ (Recommended: 3-6 milestones)

**Total Timeline**: \_\_\_\_\_ months from fundraise close

**Milestone Distribution Table**:

| Milestone | Title | Timeline | Funds %  | Funds $     | Token Vest % |
| --------- | ----- | -------- | -------- | ----------- | ------------ |
| M1        |       |          |          |             |              |
| M2        |       |          |          |             |              |
| M3        |       |          |          |             |              |
| M4        |       |          |          |             |              |
| M5        |       |          |          |             |              |
| M6        |       |          |          |             |              |
| **TOTAL** |       |          | **100%** | **$\_\_\_** | **100%**     |

**Milestone Timeline Visualization**:

```
Month 0 ---|--- M1 (Month 3) ---|--- M2 (Month 6) ---|--- M3 (Month 9) ---...
```

***

## MILESTONE 1

### M1: \[Insert Milestone Title]

#### Basic Information

**Milestone Number**: 1

**Milestone Title**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ (Max 80 characters)

**Start Date**: YYYY-MM-DD

**Deadline**: YYYY-MM-DD HH:MM UTC

**Timeline Duration**: \_\_\_\_\_ days

**Recommended Buffer**: +\_\_\_\_\_ days (10-20% of timeline)

**Dependencies**:

* [ ] None (first milestone)
* [ ] Depends on: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

#### Funding Allocation

**Percentage of Total Raise**: \_\_\_\_\_%

**Dollar Amount**: $\_\_\_\_\_\_\_\_\_\_\_\_\_ USDC

**Justification** (Why this amount is needed for this milestone):

***

***

***

**Detailed Budget Breakdown**:

| Expense Category | Amount | % of Milestone | Justification |
| ---------------- | ------ | -------------- | ------------- |
| Development      | $      |                |               |
| Security/Audit   | $      |                |               |
| Infrastructure   | $      |                |               |
| Marketing        | $      |                |               |
| Operations       | $      |                |               |
| Contingency      | $      |                |               |
| **TOTAL**        | **$**  | **100%**       |               |

#### Description

**Comprehensive Milestone Description** (200-500 words):

What will be delivered:

***

***

***

Why it matters to the project:

***

***

***

How it advances the roadmap:

***

***

***

#### Completion Criteria

**Total Number of Criteria**: \_\_\_\_\_ (Minimum 3, Maximum 8)

***

**Criterion 1**

**Statement**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Type**:

* [ ] On-Chain Metric
* [ ] Off-Chain with Cryptographic Proof
* [ ] Manual Review Required

**Target Value/Status**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Measurement Method**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Data Source(s)**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Verification Instructions** (How Seedify/Oracle can independently verify):

***

***

**Evidence Required**:

* [ ] Smart contract address + transaction hash
* [ ] Block explorer link
* [ ] Third-party aggregator link (DeFiLlama, Dune, etc.)
* [ ] GitHub commit hash / repository link
* [ ] Screenshots (timestamped, IPFS hosted)
* [ ] API endpoint with query parameters
* [ ] Signed attestation from third party
* [ ] Other: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Gameability Assessment**:

* Can this metric be faked through wash trading? \[ ] Yes \[ ] No
* Can this metric be Sybil attacked? \[ ] Yes \[ ] No
* If yes to either, explain mitigation: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**Criterion 2**

**Statement**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Type**:

* [ ] On-Chain Metric
* [ ] Off-Chain with Cryptographic Proof
* [ ] Manual Review Required

**Target Value/Status**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Measurement Method**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Data Source(s)**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Verification Instructions**:

***

***

**Evidence Required**:

* [ ] Smart contract address + transaction hash
* [ ] Block explorer link
* [ ] Third-party aggregator link
* [ ] GitHub commit hash / repository link
* [ ] Screenshots (timestamped, IPFS hosted)
* [ ] API endpoint with query parameters
* [ ] Signed attestation from third party
* [ ] Other: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Gameability Assessment**:

* Can this metric be faked through wash trading? \[ ] Yes \[ ] No
* Can this metric be Sybil attacked? \[ ] Yes \[ ] No
* If yes to either, explain mitigation: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**Criterion 3**

**Statement**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Type**:

* [ ] On-Chain Metric
* [ ] Off-Chain with Cryptographic Proof
* [ ] Manual Review Required

**Target Value/Status**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Measurement Method**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Data Source(s)**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Verification Instructions**:

***

***

**Evidence Required**:

* [ ] Smart contract address + transaction hash
* [ ] Block explorer link
* [ ] Third-party aggregator link
* [ ] GitHub commit hash / repository link
* [ ] Screenshots (timestamped, IPFS hosted)
* [ ] API endpoint with query parameters
* [ ] Signed attestation from third party
* [ ] Other: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Gameability Assessment**:

* Can this metric be faked through wash trading? \[ ] Yes \[ ] No
* Can this metric be Sybil attacked? \[ ] Yes \[ ] No
* If yes to either, explain mitigation: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**Criterion 4 (Optional)**

**Statement**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\[Repeat same format as Criterion 1-3]

***

**Criterion 5 (Optional)**

**Statement**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\[Repeat same format]

***

**Criterion 6 (Optional)**

**Statement**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\[Repeat same format]

***

**Criterion 7 (Optional)**

**Statement**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\[Repeat same format]

***

**Criterion 8 (Optional)**

**Statement**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\[Repeat same format]

***

#### Evidence Package Requirements

**Evidence Submission Deadline**: Same as Milestone Deadline (YYYY-MM-DD HH:MM UTC)

**Submission Method**: Via Seedify Portal at \[URL]

**Required Documents** (Check all that apply):

* [ ] Evidence Index Document (structured list of all evidence with links)
* [ ] Smart contract addresses with deployment transactions
* [ ] Transaction hashes demonstrating functionality
* [ ] Block explorer links with filters applied
* [ ] GitHub repository link with specific commit hash
* [ ] Code diff/changelog since previous milestone
* [ ] Third-party data aggregator links (DeFiLlama, Dune Analytics, etc.)
* [ ] Screenshots (timestamped, uploaded to IPFS/Arweave)
* [ ] Screen recording videos (timestamped, with visible URLs)
* [ ] API endpoint documentation with sample queries
* [ ] Analytics dashboard access (read-only credentials)
* [ ] Audit reports (if applicable)
* [ ] Partnership announcements (official links from both parties)
* [ ] Technical documentation / user guides
* [ ] Test coverage reports
* [ ] Performance benchmarks / load test results
* [ ] Third-party attestations (signed statements)
* [ ] Other: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Evidence Integrity Commitments**:

* [ ] We will not edit evidence after submission deadline
* [ ] We will not delete or modify on-chain data retroactively
* [ ] We will not engage in wash trading or Sybil attacks to inflate metrics
* [ ] We will disclose any known issues or partial completions
* [ ] We understand evidence manipulation results in milestone failure

**Evidence Storage**:

* Primary storage: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ (Seedify portal, GitHub, IPFS, etc.)
* Backup storage: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ (recommended: IPFS/Arweave for immutability)
* Hash of evidence package will be recorded on-chain: \[ ] Yes \[ ] No

#### Risk Disclosures

**Overall Risk Level**:

* [ ] Low (established technology, minimal external dependencies)
* [ ] Medium (some technical challenges or market dependencies)
* [ ] High (novel technology, significant external dependencies, or ambitious targets)

***

**Risk 1: \[Risk Category]**

**Description**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**Likelihood**: \[ ] Low \[ ] Medium \[ ] High

**Impact if occurs**: \[ ] Low \[ ] Medium \[ ] High

**Mitigation Strategy**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**Contingency Plan**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

***

**Risk 2: \[Risk Category]**

**Description**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**Likelihood**: \[ ] Low \[ ] Medium \[ ] High

**Impact if occurs**: \[ ] Low \[ ] Medium \[ ] High

**Mitigation Strategy**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**Contingency Plan**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

***

**Risk 3: \[Risk Category]**

**Description**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**Likelihood**: \[ ] Low \[ ] Medium \[ ] High

**Impact if occurs**: \[ ] Low \[ ] Medium \[ ] High

**Mitigation Strategy**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**Contingency Plan**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

***

**Additional Risks (if applicable)**

\[Add more risks following the same format]

***

#### External Dependencies

**Does this milestone depend on external parties/protocols?**

* [ ] No external dependencies
* [ ] Yes (list below)

**External Dependency 1**:

* Name: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Type: \[ ] Third-party protocol \[ ] Service provider \[ ] Regulatory approval \[ ] Other
* Criticality: \[ ] Required \[ ] Preferred \[ ] Optional
* Fallback if unavailable: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Risk mitigation: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**External Dependency 2**:

* Name: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Type: \[ ] Third-party protocol \[ ] Service provider \[ ] Regulatory approval \[ ] Other
* Criticality: \[ ] Required \[ ] Preferred \[ ] Optional
* Fallback if unavailable: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Risk mitigation: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**External Dependency 3**: \[Add more as needed]

***

#### Technical Architecture (For Technical Milestones)

**Tech Stack**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Smart Contract Language**: \[ ] Solidity \[ ] Rust \[ ] Move \[ ] Other: \_\_\_\_\_\_\_

**Blockchain(s)**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Key Technologies/Frameworks**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Security Measures**:

* [ ] Code audit planned (auditor: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_)
* [ ] Bug bounty program (amount: $\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_)
* [ ] Formal verification
* [ ] Multi-sig implementation
* [ ] Time locks
* [ ] Other: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Open Source Commitment**:

* [ ] Fully open source
* [ ] Partially open source (specify: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_)
* [ ] Closed source with audit

***

#### Success Indicators Beyond Criteria

**What would make this milestone exceptionally successful (beyond baseline criteria)?**

***

***

***

**How will this milestone's success be measured long-term?**

***

***

***

#### Prohibited Milestone Types Check

**Verify your milestone does NOT include** (check to confirm):

* [ ] ✅ No subjective quality assessments ("high-quality", "good UX", etc.)
* [ ] ✅ No effort-based metrics ("work for 3 months", "attend 5 conferences")
* [ ] ✅ No circular/self-referential metrics (token price, market cap)
* [ ] ✅ No easily manipulable metrics (social media followers without engagement)
* [ ] ✅ No vague technical terms ("complete development", "finish backend")
* [ ] ✅ No single-point-of-failure external dependencies without alternatives
* [ ] ✅ No binary pass/fail for overly complex deliverables (broken into sub-milestones)

***

#### Team Accountability

**Key Personnel Responsible for This Milestone**:

| Name | Role | Primary Responsibility | Time Commitment     |
| ---- | ---- | ---------------------- | ------------------- |
|      |      |                        | \_\_\_\_ hours/week |
|      |      |                        | \_\_\_\_ hours/week |
|      |      |                        | \_\_\_\_ hours/week |

**Team Stability Commitment**:

* [ ] We commit to maintaining core team members throughout this milestone
* [ ] If team changes occur, we will notify Seedify within 7 days
* [ ] We understand significant team changes may trigger milestone review

**Communication Protocol**:

* Primary contact: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Update frequency: \[ ] Weekly \[ ] Bi-weekly \[ ] Monthly
* Progress reporting method: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

## MILESTONE 2

### M2: \[Insert Milestone Title]

\[Repeat entire structure from Milestone 1]

***

## MILESTONE 3

### M3: \[Insert Milestone Title]

\[Repeat entire structure from Milestone 1]

***

## MILESTONE 4 (if applicable)

### M4: \[Insert Milestone Title]

\[Repeat entire structure from Milestone 1]

***

## MILESTONE 5 (if applicable)

### M5: \[Insert Milestone Title]

\[Repeat entire structure from Milestone 1]

***

## MILESTONE 6 (if applicable)

### M6: \[Insert Milestone Title]

\[Repeat entire structure from Milestone 1]

***

## CROSS-MILESTONE CONSIDERATIONS

### Milestone Dependencies & Sequencing

**Dependency Map**:

```
M1 (Foundation)
  ↓
M2 (Core Build) ← depends on M1 architecture
  ↓
M3 (Feature Expansion) ← depends on M2 completion
  ↓
M4 (Scaling) ← depends on M3 user base
```

**Detailed Dependency Explanation**:

***

***

***

**Risk of Cascading Failures**:

* If Milestone X fails, which subsequent milestones become impossible? \_\_\_\_\_\_\_\_
* Mitigation strategy: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

### Emergency Protocols

#### Force Majeure Events

**Events that would qualify as force majeure**:

* [ ] Natural disasters affecting team location
* [ ] War or civil unrest in team's country
* [ ] Regulatory shutdown of blockchain/protocol
* [ ] Critical vulnerability in underlying infrastructure
* [ ] Pandemic/health crisis preventing work
* [ ] Other: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Force Majeure Response Plan**:

1. Notify Seedify within: \_\_\_\_\_ hours
2. Provide documentation: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
3. Request milestone delay via Community vote
4. Alternative work plan: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

#### Team Departure Protocol

**If key team members leave**:

* Notification to Seedify: Within \_\_\_\_\_ days
* Replacement plan: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Impact assessment required: \[ ] Yes \[ ] No
* Milestone timeline adjustment: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

#### Smart Contract Vulnerability

**If critical bug discovered in deployed contracts**:

* Emergency contact: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
* Pause mechanism: \[ ] Yes \[ ] No
* Migration plan prepared: \[ ] Yes \[ ] No
* Council for emergency actions: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

## PROJECT COMMITMENTS & DECLARATIONS

### Anti-Gaming Commitments

**We commit to:**

* [ ] Not engaging in wash trading to inflate metrics
* [ ] Not creating Sybil accounts to fake user adoption
* [ ] Not manipulating on-chain data through circular transactions
* [ ] Not submitting misleading or fabricated evidence
* [ ] Not coordinating with voters to manipulate outcomes
* [ ] Disclosing all conflicts of interest transparently
* [ ] Reporting any evidence manipulation attempts by third parties

**Penalty Acknowledgment**:

* [ ] We understand that evidence manipulation results in immediate milestone failure
* [ ] We understand that repeated violations may result in permanent ban from Seedify
* [ ] We understand that penalties may include forfeiture of remaining funds

### Transparency Commitments

**We commit to:**

* [ ] Providing monthly progress updates to community
* [ ] Responding to community questions within 48 hours
* [ ] Disclosing any material changes to team, strategy, or timelines
* [ ] Publishing post-mortems if milestones fail
* [ ] Maintaining open communication channels (Discord/Telegram)
* [ ] Being transparent about challenges and obstacles

### KYC/KYB Compliance

**We confirm:**

* [ ] All team members have completed KYC with Seedify
* [ ] Company has completed KYB (if incorporated)
* [ ] No team members are on sanctions lists
* [ ] Company is registered in: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ (jurisdiction)
* [ ] We will notify Seedify of any team composition changes within 7 days

### Legal & Regulatory Compliance

**We confirm:**

* [ ] Our project complies with all applicable laws in our jurisdiction
* [ ] We have consulted with legal counsel regarding our token structure
* [ ] We understand Seedify does not provide legal advice
* [ ] We are responsible for all regulatory compliance in our operating jurisdictions
* [ ] We will notify Seedify immediately of any regulatory actions or inquiries

### Intellectual Property

**We confirm:**

* [ ] We own or have licensed all IP used in this project
* [ ] No third-party IP is being used without permission
* [ ] Open-source licenses are properly attributed
* [ ] No patent violations to our knowledge

***

## SEEDIFY REVIEW SECTION

*(To be completed by Seedify team - do not fill out)*

**Reviewer Name**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Review Date**: YYYY-MM-DD

**Initial Assessment**:

* [ ] Milestones meet structural requirements
* [ ] Criteria are objective and measurable
* [ ] Evidence requirements are adequate
* [ ] Risk disclosures are comprehensive
* [ ] No prohibited milestone types used
* [ ] Funding allocation is reasonable
* [ ] Timeline is realistic

**Required Revisions**:

***

***

**Red Flags / Concerns**:

***

***

**Approval Status**:

* [ ] Approved for community voting
* [ ] Approved with minor revisions
* [ ] Requires major revisions
* [ ] Rejected

**Seedify Signature**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Date**: YYYY-MM-DD

***

## SUBMISSION CHECKLIST

Before submitting, verify:

**Structure & Completeness**:

* [ ] All milestones follow M\[#] format
* [ ] Each milestone has 3-8 completion criteria
* [ ] All criteria are objective and measurable
* [ ] Evidence requirements specified for each criterion
* [ ] Timeline includes exact deadlines (UTC)
* [ ] Funding percentages add to 100%
* [ ] Dependencies clearly noted

**Quality Standards**:

* [ ] No prohibited milestone types
* [ ] Verification methods specified
* [ ] Multiple evidence sources (not single point of failure)
* [ ] Risk disclosures for each milestone
* [ ] Budget breakdown detailed
* [ ] External dependencies identified with fallbacks

**Anti-Gaming Verification**:

* [ ] No circular metrics (price, market cap)
* [ ] No manipulable social metrics
* [ ] No subjective assessments
* [ ] Sybil-resistant metrics chosen
* [ ] Wash trading cannot fake success

**Documentation**:

* [ ] All required documents attached
* [ ] Team information complete
* [ ] Contact details provided
* [ ] KYC/KYB completed

**Commitments**:

* [ ] All commitment checkboxes marked
* [ ] Team accountability section filled
* [ ] Emergency protocols documented

***

**Submission Date**: YYYY-MM-DD

**Project Representative Signature**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Name**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Title**: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

***

**By submitting this milestone roadmap, you agree to:**

1. Follow all Seedify Milestone Guidance Criteria
2. Submit evidence by deadlines
3. Accept Community voting outcomes
4. Maintain transparency throughout project lifecycle
5. Comply with all anti-gaming and integrity commitments


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.seedify.fund/milestone-guidance-criteria/resources/milestone-submission-template.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.