V2-BE-060 — Create a Canonical API Cache-Key Registry

[dDevAhmed]

Objective

Create a Canonical API Cache-Key Registry as a focused, independently reviewable V2 backend work item.

Technical Scope

Centralize keys, versions, tenant/wallet scope, projection watermark, TTL, and invalidation for every cached read model.

Security and Architecture Requirements

• The API may index, validate, cache, and relay user-signed intent; it must never become authoritative for protocol settlement, rewards, treasury, or governance.
• Preserve Optimism/EVM semantics and reject Stellar, Soroban, or Freighter runtime dependencies.
• Use Prisma as the canonical persistence layer; do not deepen TypeORM/dual persistence.
• Do not commit secrets, personal data, generated drift, or placeholder production configuration.

Required Tests

• Unit tests for success, boundary, authorization, and failure paths.
• Integration tests against real PostgreSQL/Redis or deterministic service containers where applicable.
• Regression tests for retry, concurrency, replay, restart, and degraded dependencies.
• Run all required lint, typecheck, security, build, migration, and artifact checks.

Acceptance Criteria

• Scope is delivered without unrelated protocol or UI changes.
• Failure modes are bounded, observable, redacted, and fail closed.
• Concurrency and idempotency behaviour is explicitly tested.
• API/OpenAPI/runbook documentation is updated where applicable.
• The PR maps evidence to every acceptance criterion.
• Human maintainer approval is recorded for auth, database, indexer, or other sensitive changes.

Dependencies

• V2-BE-057
• V2-BE-058

Non-Goals

• Signing transactions for users.
• Calculating authoritative verdicts, settlement, rewards, or reputation.
• Restoring legacy dual-persistence architecture.

---

🏷 Labels

• backend
• security
• complexity-medium
• wave-candidate
• architecture

---

[chinweobtagaz]

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

can i work on this issue ????

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

[zainabbaba31-source]

@zainabbaba31-source has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

can I please work on this issue?

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

[drips-wave]

Congratulations, @zainabbaba31-source! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @zainabbaba31-source: 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 🌊