## 1- Due Diligence and Checks Review

(attach link to due diligence document for review, see template [here](https://hackmd.io/btMxqcktREOIMjVwcgjRtg)

(attach link to checks document for review, see template [here](https://hackmd.io/btMxqcktREOIMjVwcgjRtg)

### Once a strategy's due diligence has been approved by the team, the strategist can begin codifying it for code review

## 2- Strategy Review

**Description**: {description}

**Commit (hash)**: {link}

**Repo**: {link}

**Scope**:

- Strategy.sol {link}

**Flat Strategy (with dependencies)**: {link}

**Review Ongoing By**:

- [ ] Dev 1
- [ ] Dev 2

**Review Completed By**:

- [ ] Dev 1
- [ ] Dev 2

## 3- Summary Table

Total Issues: N

| Issue # | Description | Severity | Likelihood | Status |
| ------ | ------ | ------ | ------ | ------ |
| 1 | Description issue 1 | [Critical, High, Medium, Low, Info] | [High, Medium, Low] | [Pending, Acked, Fixed]
| 2 | Description issue 2 | [Critical, High, Medium, Low, Info] | [High, Medium, Low] | [Pending, Acked, Fixed]
| N | Description issue N | [Critical, High, Medium, Low, Info] | [High, Medium, Low] | [Pending, Acked, Fixed]

## Risk Scores

(To be filled by the security team before closing the ticket)

{
  name: string;
  network: number;
  targets: string[];
  codeReviewScore: number;
  testingScore: number;
  auditScore: number;
  protocolSafetyScore: number;
  complexityScore: number;
  teamKnowledgeScore: number;
  tags: string[];
}

Example:

{
    "name": "Strategy X",
    "network": 1,
    "targets": ["0x1234...1234", "0x2345...2345"],
    "codeReviewScore": 2,
    "testingScore": 3,
    "auditScore": 4,
    "protocolSafetyScore": 3,
    "complexityScore": 4,
    "teamKnowledgeScore": 4,
    "tags": ["protocol", "standalone"]
}