[Frontend] Several hooks bypass the queryKeys factory with ad-hoc inline keys, defeating centralized/typed invalidation

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

The file ships a Centralised query key factory (useApi.ts:38) whose stated purpose is targeted invalidation, yet useCreditScore (useApi.ts:1044), useCreditScoreHistory (989), useYieldHistory (1153), useRemittanceNft (1013), useNotificationPreferences (1343), useLoanAmortizationSchedule (711) and useLoanAmortizationPreview (738) hardcode string-array keys outside the factory. These keys can drift from invalidators and there is no compile-time guarantee read/write keys agree.

Acceptance criteria

• Add factory entries for creditScore, creditScoreHistory, yieldHistory, remittanceNft, notificationPreferences, amortization, amortizationPreview
• Replace the inline keys in those hooks with the factory functions
• Type queryKeys with as const return types already present so invalidators reuse them

Files to touch

• frontend/src/app/hooks/useApi.ts

Out of scope

• Renaming existing cache keys that would invalidate persisted caches

[wheval]

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

Hello i would love to work on this.

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

[Buchi-Einstein]

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

Can i work on this please

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

[Thoni76]

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

Please assign . you will get a pr today

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

[Georgechisom]

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

Hi, I have reviewed this issue and am familiar and skilled to solve this issue, kindly assign it to me

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

[drips-wave]

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

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

[grantfox-oss]

🦊 GrantFox — @wheval has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #1222)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.