📋 Issue #611: [SEP-31] Validate Sender Receiver Relationship in KYC Requirements
💡 Description & Objective
This issue tracking item focuses on addressing [SEP-31] Validate Sender Receiver Relationship in KYC Requirements within the backend-sep31 component scope. Contributors should follow the detailed guidelines below to implement, document, and test the solution correctly.
🛠️ Step-by-Step Implementation Guide
To solve this issue, please proceed as follows:
🧪 Local Validation
Validate your changes locally by running:
🤝 Contribution Guidelines
🌿 1. Branch Naming Rules
Create a new branch from main using the following exact format:
feature/issue-611-sep-31-validate-sender-receiver-rel
💬 2. Commit Message Standard
Use Conventional Commits format when creating commits. Your final commit (or PR squash commit) must include:
feat(backend-sep31): [sep-31] validate sender receiver relationship in kyc requirements (closes #611)
Example: feat(backend-sep31): [sep-31] validate sender receiver relationship in kyc requirements closes #611
🚀 3. Pull Request Details
- Ensure all tests pass locally.
- Do not commit local SQLite files or lock files.
- Submit your branch for peer review.
📋 Issue #611: [SEP-31] Validate Sender Receiver Relationship in KYC Requirements
💡 Description & Objective
This issue tracking item focuses on addressing [SEP-31] Validate Sender Receiver Relationship in KYC Requirements within the
backend-sep31component scope. Contributors should follow the detailed guidelines below to implement, document, and test the solution correctly.🛠️ Step-by-Step Implementation Guide
To solve this issue, please proceed as follows:
🧪 Local Validation
Validate your changes locally by running:
🤝 Contribution Guidelines
🌿 1. Branch Naming Rules
Create a new branch from
mainusing the following exact format:💬 2. Commit Message Standard
Use Conventional Commits format when creating commits. Your final commit (or PR squash commit) must include:
Example:
feat(backend-sep31): [sep-31] validate sender receiver relationship in kyc requirements closes #611🚀 3. Pull Request Details