# Evidence Requirements

## Evidence Requirements

### Submission Format

All evidence must be submitted via Seedify portal by milestone deadline.

Required Package Contents:

#### 1. Evidence Index Document

A structured document listing all evidence with direct links. Example template:

```markdown
# Milestone [X] Evidence Submission
**Project**: [Name]
**Milestone**: [Title]
**Submission Date**: [YYYY-MM-DD HH:MM UTC]
**Submitted By**: [Team Member Name + Role]

## Completion Criteria Evidence

### Criterion 1: [Statement]
- **Evidence Link**: [URL]
- **Verification Method**: [How to verify]
- **Screenshot**: [Link to timestamped screenshot]
- **Additional Notes**: [Context if needed]

### Criterion 2: [Statement]
- **Evidence Link**: [URL]
- **Verification Method**: [How to verify]
...
```

#### 2. Timestamped Screenshots

* Must include visible URL bar
* Must include timestamp (system clock or on-page date)
* Must be uploaded to immutable storage (IPFS, Arweave)
* Hash of image file must be recorded on-chain

#### 3. Transaction Hashes (if applicable)

* Deployment transactions
* Key interaction transactions demonstrating functionality
* Must include block number and timestamp

#### 4. Code Repository State

* Specific commit hash for milestone completion
* Diff/changelog since previous milestone
* Documentation of new features
* Test coverage report (if applicable)

#### 5. Third-Party Verification Links

* DeFiLlama dashboard link with date range
* Dune Analytics query link
* Block explorer filtered transaction list
* Analytics platform screenshots

### Evidence Integrity Rules

Projects must NOT:

* Edit evidence after submission deadline
* Delete or modify on-chain data retroactively
* Manipulate metrics through wash trading, circular transactions, or Sybil attacks
* Use misleading screenshots or selective data presentation
* Coordinate with voters to manipulate outcomes

Oracle Review will include:

* Sybil detection analysis (wallet clustering, timing patterns)
* Wash trading detection (circular flows, self-dealing)
* Data consistency checks (multiple sources)
* Historical pattern analysis (growth rate plausibility)

Violations result in:

* Immediate milestone failure
* Flagging in Community vote with detailed report
* Potential disqualification from future Seedify raises


---

# 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/evidence-requirements.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.