---
tags: protocol, sop
---

# Protocol SOPs

### Issue Triage:

1. **New Issues:**
- [ ] Regularly check for new issues in the repository.
- [ ] Label issues with appropriate tags (bug, enhancement, feature, etc.).
- [ ] Assign issues to the relevant team member or contributors.

2. **Issue Prioritization:**
- [ ] Prioritize issues based on severity and impact.
- [ ] Determine which issues need immediate attention and which can be scheduled for future releases.
- [ ] Low priority issues can be marked as "Good first issue"

3. **Communication:**
- [ ] Communicate with contributors to gather additional information on reported issues.
- [ ] Provide updates and feedback to contributors about the status of their reported issues.

---

### Release Management:

1. **Release Planning:**
- [ ] Define the scope and features for the upcoming release.
- [ ] Set a tentative release date.

2. **Branching:**
- [ ] Create a release branch from the main development branch.
- [ ] Ensure the release branch is stable for testing.

3. **Testing:**
- [ ] Conduct thorough testing of new features and fixes.
- [ ] Address any issues identified during testing.

4. **Documentation:**
- [ ] Update release notes with details of changes.
- [ ] Ensure documentation is up-to-date.

5. **Tagging and Versioning:**
- [ ] Create a release tag for the version.
- [ ] Update version numbers in relevant files.

6. **Deployment:**
- [ ] Deploy the release to the appropriate environment.
- [ ] Confirm the release is successfully deployed.

7. **Communication:**
- [ ] Announce the release to the community.
- [ ] Update relevant channels and documentation.

---

### Bounty Management:

1. **Bounty Definition:**
- [ ] Clearly define the scope and requirements of bounties.
- [ ] Assign appropriate rewards for successful completion.

2. **Listing and Promotion:**
- [ ] List active bounties on relevant platforms.
- [ ] Promote bounties within the community and on social media.

3. **Evaluation and Reward Distribution:**
- [ ] Review submitted work against bounty criteria.
- [ ] Distribute rewards to contributors promptly.

---

### Documentation:

1. **Documentation Review:**
- [ ] Regularly review documentation for accuracy and completeness.
- [ ] Update documentation to reflect any changes in the protocol.

2. **New Features/Changes:**
- [ ] Document new features and changes introduced in each release.
- [ ] Provide clear examples and use cases.

3. **Community Contributions:**
- [ ] Encourage and document community contributions to documentation.
- [ ] Credit contributors for their documentation contributions.

---

### Contract Deploy / Upgrades:

1. **Contract Testing:**
- [ ] Perform thorough testing of smart contracts.
- [ ] Address any vulnerabilities or issues identified.

2. **Deployment Process:**
- [ ] Plan and execute the deployment process.
- [ ] Confirm the successful deployment of contracts.

3. **Community Notification:**
- [ ] Notify the community about contract deployments and upgrades.
- [ ] Provide relevant information about changes.

---

### Subgraphs Deploy / Upgrades:

1. **Subgraph Definition:**
- [ ] Clearly define the structure and purpose of subgraphs.
- [ ] Ensure subgraphs align with the overall project goals.

2. **Testing:**
- [ ] Test subgraphs in a controlled environment.
- [ ] Verify subgraphs against real data sources.

3. **Deployment:**
- [ ] Deploy subgraphs to the appropriate indexing service.
- [ ] Confirm successful indexing.

---

### Repo User/Config Management:

1. **Access Control:**
- [ ] Regularly review and update repository access permissions.
- [ ] Remove access for inactive or irrelevant contributors.

2. **Configuration Files:**
- [ ] Maintain and update configuration files as needed.
- [ ] Ensure consistency across development environments.

3. **User Support:**
- [ ] Address user queries and issues related to repository usage.
- [ ] Provide clear instructions for common configurations.