Evidence Submission Template

Instructions: Complete this form when submitting evidence for milestone completion. All evidence must be submitted by the milestone deadline. Late submissions require a formal delay request via Community vote.

---

Submission Metadata

Project Name: _____________________

Milestone Number: M___

Milestone Title: _____________________________________________________

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

Submission Date & Time: YYYY-MM-DD HH:MM UTC

Submission Status:

• On Time (submitted before deadline)

• Late (submitted after deadline) - Requires explanation below

If Late, Explanation: ___________________________________________________

---

Submitted By:

• Name: _____________________

• Role in Project: _____________________

• Email: _____________________

• Telegram: _____________________

Submission Method:

• Seedify Portal Upload

• IPFS (provide hash)

• GitHub Repository

• Other: _____________________

Evidence Package Hash (SHA-256): _____________________________________ (Hash of all evidence files combined - for integrity verification)

Blockchain Timestamp (if applicable):

• Transaction Hash: _____________________

• Block Number: _____________________

• Timestamp: YYYY-MM-DD HH:MM UTC

---

Executive Summary

Milestone Completion Status:

• ✅ Fully Completed - All criteria met

• ⚠️ Partially Completed - Some criteria met (requires explanation)

• ❌ Not Completed - Requesting extension or modification

If Partially Completed, Percentage Estimate: _____%

Brief Summary of Achievements (3-5 sentences):

---

---

---

---

Key Highlights:

• Achievement 1: _____________________________________________________________

• Achievement 2: _____________________________________________________________

• Achievement 3: _____________________________________________________________

Known Issues / Incomplete Items:

• Issue 1: ___________________________________________________________________

• Issue 2: ___________________________________________________________________

• Issue 3: ___________________________________________________________________

---

Evidence Index

Quick Navigation Guide for Reviewers:

Criterion #	Status	Primary Evidence Link	Backup Evidence
1	✅/⚠️/❌
2	✅/⚠️/❌
3	✅/⚠️/❌
4	✅/⚠️/❌
5	✅/⚠️/❌
6	✅/⚠️/❌
7	✅/⚠️/❌
8	✅/⚠️/❌

---

CRITERION-BY-CRITERION EVIDENCE

Criterion 1

Original Criterion Statement

From approved milestone submission:

---

---

Completion Status

• ✅ Fully Met

• ⚠️ Partially Met (____% complete)

• ❌ Not Met

Evidence Submission

Primary Evidence

Evidence Type:

• Smart Contract Deployment

• On-Chain Transaction Data

• GitHub Commit/Repository

• Third-Party Platform Data

• Performance Metrics

• User Adoption Metrics

• Partnership Documentation

• Other: _____________________

Evidence Link 1 (Primary):

• URL: _______________________________________________________________________

• Type: [ ] Live Link [ ] Screenshot [ ] Video [ ] Document [ ] API Endpoint

• Storage: [ ] Public URL [ ] IPFS [ ] Arweave [ ] GitHub

• Hash (if applicable): _______________________________________________________

• Access Instructions: ________________________________________________________

Evidence Link 2 (Supporting):

• URL: _______________________________________________________________________

• Type: [ ] Live Link [ ] Screenshot [ ] Video [ ] Document [ ] API Endpoint

• Storage: [ ] Public URL [ ] IPFS [ ] Arweave [ ] GitHub

• Hash (if applicable): _______________________________________________________

Evidence Link 3 (Supporting):

• URL: _______________________________________________________________________

• Type: [ ] Live Link [ ] Screenshot [ ] Video [ ] Document [ ] API Endpoint

• Storage: [ ] Public URL [ ] IPFS [ ] Arweave [ ] GitHub

• Hash (if applicable): _______________________________________________________

Verification Instructions for Oracle/Reviewers

Step-by-step verification process:

Step 1: ___________________________________________________________________

---

Step 2: ___________________________________________________________________

---

Step 3: ___________________________________________________________________

---

Expected Result: __________________________________________________________

Verification Tools Needed:

• Block Explorer (specify: ___________________)

• DeFiLlama

• Dune Analytics

• GitHub

• API Tool (Postman, curl, etc.)

• Other: _____________________

Screenshots & Visual Evidence

Screenshot 1:

• Description: ________________________________________________________________

• IPFS Hash: __________________________________________________________________

• Timestamp Visible: [ ] Yes [ ] No

• URL Visible: [ ] Yes [ ] No

• Annotation: _________________________________________________________________

Screenshot 2:

• Description: ________________________________________________________________

• IPFS Hash: __________________________________________________________________

• Timestamp Visible: [ ] Yes [ ] No

• URL Visible: [ ] Yes [ ] No

Screenshot 3:

• Description: ________________________________________________________________

• IPFS Hash: __________________________________________________________________

Video Evidence (if applicable):

• Description: ________________________________________________________________

• Video Link: _________________________________________________________________

• Duration: _______ minutes

• IPFS/Arweave Hash: __________________________________________________________

• Key Timestamps: _____________________________________________________________

On-Chain Evidence (if applicable)

Blockchain: [ ] Ethereum [ ] BNB Chain [ ] Polygon [ ] Arbitrum [ ] Base [ ] Other: _______

Smart Contract Address: ___________________________________________________

Deployment Transaction:

• Transaction Hash: ___________________________________________________________

• Block Number: _______________________________________________________________

• Timestamp: YYYY-MM-DD HH:MM UTC

• Gas Used: ___________________________________________________________________

Verification Link (Etherscan/BscScan/etc.):

---

Key Transactions (demonstrating functionality):

Transaction 1:

• Purpose: ____________________________________________________________________

• Hash: _______________________________________________________________________

• Block: ______________________________________________________________________

• From/To: ____________________________________________________________________

Transaction 2:

• Purpose: ____________________________________________________________________

• Hash: _______________________________________________________________________

• Block: ______________________________________________________________________

Transaction 3:

• Purpose: ____________________________________________________________________

• Hash: _______________________________________________________________________

• Block: ______________________________________________________________________

Contract Verification Status:

• Verified on block explorer

• Source code published

• Proxy implementation verified (if proxy)

Third-Party Data Sources

Data Source 1:

• Platform: [ ] DeFiLlama [ ] Dune Analytics [ ] CoinGecko [ ] DefiPulse [ ] Other: _______

• Metric Tracked: _____________________________________________________________

• Link to Dashboard/Query: ____________________________________________________

• Screenshot of Data: _________________________________________________________

• Date Range: From _____________ To _____________

• Current Value: ______________________________________________________________

• Target Value (from criterion): ______________________________________________

• Status: [ ] Target Met [ ] Target Not Met

Data Source 2:

• Platform: ___________________________________________________________________

• Metric Tracked: _____________________________________________________________

• Link: _______________________________________________________________________

• Screenshot: _________________________________________________________________

• Date Range: From _____________ To _____________

• Current Value: ______________________________________________________________

• Target Value: _______________________________________________________________

• Status: [ ] Target Met [ ] Target Not Met

Data Integrity & Anti-Gaming Evidence

Sybil Resistance Check:

• We have analyzed wallet addresses for clustering/Sybil behavior

• Analysis shows: __________________________________________________________

• Supporting evidence: _____________________________________________________

Wash Trading Check:

• We have analyzed transaction patterns for circular flows

• Analysis shows: __________________________________________________________

• Supporting evidence: _____________________________________________________

Organic Growth Evidence:

• Growth rate analysis attached

• Geographic distribution data attached

• User behavior analytics attached

• Third-party validation attached

Third-Party Verification (if available):

• Verifier Name: ______________________________________________________________

• Verification Method: ________________________________________________________

• Signed Attestation: [ ] Yes (attach) [ ] No [ ] Not Applicable

Technical Documentation (if applicable)

Code Repository:

• Repository URL: _____________________________________________________________

• Branch: _____________________________________________________________________

• Commit Hash (milestone completion): _________________________________________

• Commits Since Last Milestone: _______________________________________________

• Contributors Count: _________________________________________________________

• Lines of Code Added: ________________________________________________________

• Test Coverage: _______%

Changelog/Release Notes:

• Link: _______________________________________________________________________

• Summary of Changes: _________________________________________________________

---

API Documentation (if applicable):

• Documentation URL: __________________________________________________________

• Endpoints Delivered: ________________________________________________________

• API Version: ________________________________________________________________

Technical Specifications:

• Link to Specs: ______________________________________________________________

• Implementation Status: [ ] Full [ ] Partial (____%)

Additional Context

Why This Evidence Proves Criterion Completion:

---

---

---

Challenges Overcome:

---

---

Deviations from Original Plan (if any):

---

---

Quality Assurance:

• Internal testing completed

• External testing completed

• Security review completed

• Performance benchmarking completed

Testing Evidence:

• Test Results Document: ______________________________________________________

• Bug Reports Resolved: _______________________________________________________

• Performance Metrics: ________________________________________________________

---

Criterion 2

[Repeat entire structure from Criterion 1]

Original Criterion Statement

---

Completion Status

• ✅ Fully Met

• ⚠️ Partially Met (____%)

• ❌ Not Met

Evidence Submission

[Full structure repeated...]

---

Criterion 3

[Repeat entire structure from Criterion 1]

---

Criterion 4 (if applicable)

[Repeat entire structure from Criterion 1]

---

Criterion 5 (if applicable)

[Repeat entire structure from Criterion 1]

---

Criterion 6 (if applicable)

[Repeat entire structure from Criterion 1]

---

Criterion 7 (if applicable)

[Repeat entire structure from Criterion 1]

---

Criterion 8 (if applicable)

[Repeat entire structure from Criterion 1]

---

SUPPLEMENTARY EVIDENCE

Overall Milestone Evidence

Project Activity Dashboard

GitHub Activity (if applicable):

• Repository Stars: ___________________________________________________________

• Forks: _______________________________________________________________________

• Open Issues: _________________________________________________________________

• Closed Issues This Period: __________________________________________________

• Pull Requests Merged: _______________________________________________________

• Contributor Activity: _______________________________________________________

Community Growth:

• Discord Members: Start: _______ | End: _______ | Growth: _______%

• Telegram Members: Start: _______ | End: _______ | Growth: _______%

• Twitter Followers: Start: _______ | End: _______ | Growth: _______%

• Active Community Engagement Rate: _______%

Media Coverage:

• Articles Published: __________________________________________________________

• Major Mentions: ______________________________________________________________

• Partnership Announcements: ___________________________________________________

User Testimonials & Feedback

User Testimonial 1:

• User: _______________________________________________________________________

• Quote: ______________________________________________________________________

• Source: _____________________________________________________________________

• Date: _______________________________________________________________________

User Testimonial 2: [Repeat format]

Community Feedback Summary:

---

---

Performance Metrics

System Performance:

• Uptime: _______%

• Average Response Time: _____ ms

• Throughput: _____ TPS (transactions per second)

• Peak Load Handled: __________________________________________________________

User Metrics:

• Daily Active Users (DAU): ___________________________________________________

• Monthly Active Users (MAU): _________________________________________________

• User Retention (7-day): ______%

• User Retention (30-day): ______%

Financial Metrics (if applicable):

• Total Value Locked (TVL): $__________________________________________________

• Transaction Volume: $________________________________________________________

• Revenue Generated: $________________________________________________________

• Fees Collected: $_____________________________________________________________

Competitive Analysis

How This Milestone Compares to Competitors:

---

---

Unique Achievements:

---

---

Media & Marketing Evidence

Content Created:

• Blog Posts: _________________________________________________________________

• Video Content: ______________________________________________________________

• Infographics: _______________________________________________________________

• Documentation: ______________________________________________________________

Distribution:

• Views/Impressions: __________________________________________________________

• Engagement Rate: ____________________________________________________________

• Media Mentions: _____________________________________________________________

---

DEVIATIONS & EXPLANATIONS

Deviations from Original Milestone Plan

Were there any deviations from the approved milestone criteria?

• No deviations - everything as planned

• Minor deviations - explained below

• Significant deviations - requires detailed explanation

Deviation 1

Original Plan: ____________________________________________________________

---

What Actually Happened: ___________________________________________________

---

Reason for Deviation: _____________________________________________________

---

Impact on Overall Milestone:

• No impact - equivalent value delivered

• Minor impact - slightly less value

• Significant impact - requires discussion

Mitigation / Compensation: ________________________________________________

---

Deviation 2

[Repeat format if applicable]

Deviation 3

[Repeat format if applicable]

---

Partial Completions & Blockers

If Any Criteria Not Fully Met, Explain:

Incomplete Item 1

Criterion Affected: _______________________________________________________

What Was Completed: _______________________________________________________

---

What Remains Incomplete: __________________________________________________

---

Reason for Incompletion:

• Technical blocker

• External dependency failure

• Timeline constraint

• Resource constraint

• Market conditions

• Regulatory issue

• Other: _____________________

Detailed Explanation: _____________________________________________________

---

---

Proposed Solution:

• Request milestone extension (_____ days)

• Request partial release (____% of milestone funds)

• Redistribute incomplete portion to future milestones

• Other: _____________________

Impact on Future Milestones: ______________________________________________

---

Incomplete Item 2

[Repeat format if applicable]

---

TIMELINE & RESOURCE DOCUMENTATION

Milestone Timeline

Original Planned Timeline: ________________________________________________

Actual Timeline:

• Start Date: YYYY-MM-DD

• End Date: YYYY-MM-DD

• Total Duration: _____ days

Timeline Analysis:

• ✅ Completed ahead of schedule (by _____ days)

• ✅ Completed on schedule

• ⚠️ Completed with minor delay (_____ days)

• ❌ Significantly delayed (_____ days)

If Delayed, Explanation: __________________________________________________

---

Timeline Gantt Chart / Visual (optional but recommended):

• Link to Timeline Visual: ____________________________________________________

Resource Utilization

Budget Used:

• Allocated Budget: $__________________________________________________________

• Actual Spent: $______________________________________________________________

• Variance: $__________________ (____%)

• Status: [ ] Under Budget [ ] On Budget [ ] Over Budget

Budget Breakdown:

Category	Allocated	Spent	Variance	Notes
Development	$	$	$
Security/Audit	$	$	$
Infrastructure	$	$	$
Marketing	$	$	$
Operations	$	$	$
Other	$	$	$
TOTAL	$	$	$

If Over Budget, Explanation: ______________________________________________

---

How Excess Spent (if over budget):

• From project reserves

• From future milestone allocation (specify: M___)

• From external funding

• Other: _____________________

Team Activity

Team Members Who Worked on This Milestone:

Name	Role	Hours	Key Contributions

Total Team Hours: _________ hours

Team Stability:

• No changes to team

• Minor changes (explained below)

• Significant changes (explained below)

If Team Changes Occurred:

---

---

---

QUALITY ASSURANCE & TESTING

Testing Documentation

Testing Approach:

• Unit testing

• Integration testing

• End-to-end testing

• Load testing

• Security testing

• User acceptance testing

• Other: _____________________

Test Coverage:

• Code Coverage: _______%

• Test Cases Written: _________

• Test Cases Passed: _________

• Test Cases Failed: _________

• Critical Bugs Found: _________

• Critical Bugs Fixed: _________

Testing Evidence:

• Test Report Link: ___________________________________________________________

• Test Results Screenshots: ___________________________________________________

• Bug Tracker Export: _________________________________________________________

Security Measures

Security Audit:

• Audit completed

• Audit in progress

• Audit scheduled

• No audit required for this milestone

If Audit Completed:

• Auditor: ____________________________________________________________________

• Audit Report Link: __________________________________________________________

• Audit Report IPFS Hash: _____________________________________________________

• Critical Issues Found: _______________________________________________________

• High Severity Issues Found: __________________________________________________

• All Critical/High Issues Resolved: [ ] Yes [ ] No [ ] N/A

Security Best Practices:

• Multi-sig implemented

• Time locks implemented

• Access controls implemented

• Rate limiting implemented

• Input validation implemented

• Secure key management

• Bug bounty program active

Bug Bounty Program (if applicable):

• Program Link: _______________________________________________________________

• Bounty Pool: $_______________________________________________________________

• Bugs Reported: ______________________________________________________________

• Bugs Fixed: _________________________________________________________________

---

THIRD-PARTY VALIDATIONS

Independent Verifications

Verification 1:

• Verifier Name: ______________________________________________________________

• Verifier Type: [ ] Auditor [ ] Partner [ ] User [ ] Industry Expert [ ] Other

• Verification Method: ________________________________________________________

• Verification Result: ________________________________________________________

• Signed Attestation: [ ] Attached [ ] Available upon request [ ] N/A

• Contact Info (for Seedify to verify): _______________________________________

Verification 2: [Repeat format]

Verification 3: [Repeat format]

Partnership Confirmations

If Milestone Involves Partnerships:

Partner 1:

• Partner Name: _______________________________________________________________

• Partnership Type: ___________________________________________________________

• Official Announcement Link: __________________________________________________

• Partner's Confirmation: [ ] Public announcement [ ] Signed agreement [ ] Letter of intent

• Integration Status: [ ] Complete [ ] In Progress [ ] Planned

• Evidence of Active Integration: _____________________________________________

Partner 2: [Repeat format]

---

DECLARATIONS & COMMITMENTS

Evidence Integrity Declaration

We declare that:

• All evidence submitted is authentic and unmanipulated

• No wash trading was conducted to inflate metrics

• No Sybil attacks were used to fake user adoption

• All on-chain data is accurate and verifiable

• All screenshots are timestamped and from legitimate sources

• All third-party validations are genuine

• We have not coordinated with voters to manipulate outcomes

We understand that:

• False evidence results in immediate milestone failure

• Evidence manipulation may result in permanent ban from Seedify

• Seedify and AI Oracles will perform anti-gaming analysis

• Community can challenge evidence during Community vote period

Transparency Commitment

We commit to:

• Responding to community questions within 48 hours during voting period

• Providing additional evidence if requested by Seedify

• Accepting the Community vote outcome

• Continuing transparent communication regardless of outcome

Dispute Rights Acknowledgment

We acknowledge that:

• We have ONE dispute right per milestone

• Disputes must be filed within 48 hours of Community vote

• Disputes cannot introduce new evidence

• Frivolous disputes harm our reputation for future votes

---

SUPPORTING DOCUMENTS

Document Checklist

Required Documents (attach all applicable):

• Evidence Index (this document)

• Screenshots folder (IPFS hash: _________)

• Video demonstrations (links: _________)

• Technical documentation

• Audit reports

• Test results

• Performance benchmarks

• Third-party attestations

• Partnership agreements/announcements

• Budget reconciliation

• Timeline analysis

• Other: _____________________

Document Storage

Primary Storage Location:

• Seedify Portal

• IPFS (CID: _________)

• Arweave (TX ID: _________)

• GitHub (Repo: _________, Branch: _________, Commit: _________)

• Other: _____________________

Backup Storage Location:

• IPFS (CID: _________)

• Arweave (TX ID: _________)

• Google Drive (shared link: _________)

• Dropbox (shared link: _________)

• Other: _____________________

Access Credentials (if needed for reviewers):

• Service: ____________________________________________________________________

• Username/Access Link: _______________________________________________________

• Password/Access Key: ________________________________________________________

• Access Expiration: YYYY-MM-DD

• Notes: ______________________________________________________________________

---

NEXT STEPS & FUTURE OUTLOOK

Impact on Future Milestones

How This Milestone Enables Future Work:

---

---

---

Dependencies Created for Next Milestone:

---

---

Risks Mitigated for Future Milestones:

---

---

Lessons Learned

What Went Well:

---

---

What Could Be Improved:

---

---

Process Improvements for Next Milestone:

---

---

Upcoming Milestone Preview

Next Milestone (M___): ____________________________________________________

Estimated Start Date: YYYY-MM-DD

Current Progress on Next Milestone (if any): ______%

Preparatory Work Completed:

---

---

---

SUBMISSION FINALIZATION

Final Checklist

Before submitting, verify:

Evidence Completeness:

• All criteria have evidence submitted

• All links are functional and accessible

• All screenshots are timestamped and clear

• All on-chain data is verifiable

• All third-party sources are cited

Documentation Quality:

• Verification instructions are clear

• Step-by-step guidance provided for reviewers

• Alternative evidence provided where possible

• Context and explanations are comprehensive

Integrity:

• Anti-gaming declarations signed

• All deviations explained

• All incomplete items disclosed

• No misleading information

Format:

• All required sections completed

• Document is well-organized

• Evidence index matches actual evidence

• Contact information is current

Submission Authorization

I certify that:

• I am authorized to submit evidence on behalf of the project

• All information provided is accurate to the best of my knowledge

• I have reviewed all evidence for completeness and accuracy

• I understand the consequences of submitting false evidence

Submitted By:

• Name: _______________________________________________________________________

• Title/Role: _________________________________________________________________

• Signature: __________________________________________________________________

• Date: YYYY-MM-DD HH:MM UTC

Project Lead Approval:

• Name: _______________________________________________________________________

• Title: ______________________________________________________________________

• Signature: __________________________________________________________________

• Date: YYYY-MM-DD HH:MM UTC

---

Submission Confirmation

Submission ID: ____________________________________________________________ (To be assigned by Seedify system)

Submission Timestamp: YYYY-MM-DD HH:MM UTC (Automatically recorded by system)

Blockchain Proof of Submission:

• Transaction Hash: ___________________________________________________________

• Block Number: _______________________________________________________________

Next Steps:

1. Seedify will acknowledge receipt within 24 hours

2. Oracle evaluation will begin within 48 hours

3. Seedify manual review will occur within 7 days

4. Community vote will be scheduled within 10 days of submission

5. You will be notified of each stage via Telegram

Support Contact: