[Bug] Fix Notification Status Desynchronization After Refresh

[Abd-Standard]

Description

Some users report outdated notification statuses after refreshing the dashboard despite successful blockchain updates.

Tasks
Reproduce the issue.
Investigate caching layer.
Fix synchronization logic.
Add regression tests.

Acceptance Criteria
Statuses remain accurate after refresh.
Cached data updates correctly.
Regression tests prevent recurrence.

Contributor Guidelines
git checkout -b fix/status-desynchronization

[coder45oj]

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

I have a solid understanding of the underlying architecture and I would like to start testing for a solution for it

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

[Joseph-1-Duro]

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

Hi, I would love to work on your project

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Joseph-1-Duro to this issue.

[attyolu]

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

Hello Maintainer. I have experience with this kind of issue. I would love to be assigned to resolve it. Thanks

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

[AYo101o]

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

Hi! I'd like to take this, I'll reproduce the issue, inspect the caching layer for stale-read/invalidation gaps after on-chain updates, fix the sync logic so refreshes reflect current status, and add regression tests to prevent recurrence.

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

[N-thnI]

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

Dear maintainer
Please assign me this issue

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

[drips-wave]

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

🧑‍💻 @N-thnI: 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]

🎉 This issue has been marked as completed on GrantFox!

@N-thnI's PR #238 was approved and merged by @Abd-Standard.

🏆 @N-thnI: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,191 total points). Track your full progress on GrantFox.

👏 Great work, @N-thnI! Keep contributing to Core-Foundry.