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