📋 Issue #610: [SEP-38] Implement Dynamic Fee Calculation based on Asset Amount
💡 Description & Objective
This issue tracking item focuses on addressing [SEP-38] Implement Dynamic Fee Calculation based on Asset Amount within the backend-sep38 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-610-sep-38-implement-dynamic-fee-calcul
💬 2. Commit Message Standard
Use Conventional Commits format when creating commits. Your final commit (or PR squash commit) must include:
feat(backend-sep38): [sep-38] implement dynamic fee calculation based on asset amount (closes #610)
Example: feat(backend-sep38): [sep-38] implement dynamic fee calculation based on asset amount closes #610
🚀 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 #610: [SEP-38] Implement Dynamic Fee Calculation based on Asset Amount
💡 Description & Objective
This issue tracking item focuses on addressing [SEP-38] Implement Dynamic Fee Calculation based on Asset Amount within the
backend-sep38component 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-sep38): [sep-38] implement dynamic fee calculation based on asset amount closes #610🚀 3. Pull Request Details