[SEP-38] Update Quotes Cache Expiration Rules

[Ceejaytech25]

📋 Issue #620: [SEP-38] Update Quotes Cache Expiration Rules

💡 Description & Objective

This issue tracking item focuses on addressing [SEP-38] Update Quotes Cache Expiration Rules 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:

• Enforce cache validation timeouts settings.
• Ensure formatting rules are respected before pushing.

---

🧪 Local Validation

Validate your changes locally by running:

npm run test:backend

---

🤝 Contribution Guidelines

🌿 1. Branch Naming Rules

Create a new branch from main using the following exact format:

feature/issue-620-sep-38-update-quotes-cache-expirati

💬 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] update quotes cache expiration rules (closes #620)

Example: feat(backend-sep38): [sep-38] update quotes cache expiration rules closes #620

🚀 3. Pull Request Details

• Ensure all tests pass locally.
• Do not commit local SQLite files or lock files.
• Submit your branch for peer review.

[AlphaMaleBaDI]

@AlphaMaleBaDI has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer,

I would like to take on this issue to set up the Dependabot configuration for automated Soroban SDK and dependency updates.

To implement this cleanly, I plan to:

• Create a valid .github/dependabot.yml configuration targeting both cargo (for the Soroban SDK and Rust contracts) and npm or github-actions ecosystems depending on your repository structure.
• Configure appropriate update schedules (e.g., weekly), target directories, and open-PR limits to ensure updates are structured and manageable without spamming the repository.
• Ensure all repository formatting rules and local validation requirements are strictly respected before submitting.

I am familiar with your contribution guidelines and will ensure that the branch naming conventions match your exact issue footprint and that my final commit adheres precisely to your conventional commit standard. Ready to spin up a clean PR for this right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AlphaMaleBaDI to this issue.

[GideonBature]

@GideonBature has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I want to work on this issue....

ℹ️ Repo Maintainers: To accept this application, review their application or assign @GideonBature to this issue.

[drips-wave]

Congratulations, @GideonBature! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @GideonBature: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊