[Quality] Persist notification read state across sessions safely

[1nonlypiece]

Problem

Notifications can become inconsistent across tabs or disappear on reload, making verifier and vault activity easy to miss.

This issue requires a meaningful production implementation. Typo-only, documentation-only, formatting-only, dependency-only, or cosmetic changes do not satisfy the scope.

Objective

Add a versioned notification persistence and synchronization strategy with bounded storage.

Scope

Define IDs, deduplication, unread semantics, cross-tab updates, expiry, and migration for older stored data.

Acceptance criteria

• The same notification is not duplicated across refresh or tabs.
• Read/unread changes converge across open tabs.
• Corrupt or oversized storage fails closed without breaking the app.
• Tests cover migration, expiry, deduplication, cross-tab events, and reset.
• Existing CI/CD checks remain green.
• The PR explains the design, tradeoffs, test evidence, and any remaining limitations.
• The PR references this issue with Closes #{issue-number} or Fixes #{issue-number}.

Implementation notes

Implement only the stated behavior; keep unrelated refactors out of the PR.

Non-goals

• Do not remove tests merely to make CI pass.
• Do not introduce secrets, private keys, credentials, or mainnet-only values.
• Do not change unrelated APIs, UI surfaces, contract behavior, or deployment configuration.

Contributor application

Before starting, comment with relevant experience, a 1–4 bullet implementation approach, and an estimate for opening the first draft PR. Wait for maintainer assignment before coding. Only the assigned contributor is eligible for reward consideration.

Submission requirements

• Use PR title format [#<issue-number>] <short summary>.
• Check off each completed acceptance criterion.
• Include focused automated tests for success, failure, authorization, and boundary behavior where applicable.
• Include the validation commands and results in the PR description.
• Address maintainer review feedback before merge.

GrantFox reward consideration is based on the original scope, implementation quality, tests, security review, CI/CD results, review feedback, and follow-up stability; completion or merge alone is not a guarantee.

[Rodrigoue9]

Hi team! I would like to apply for this issue.

Relevant Experience

• Hands-on experience developing and shipping production Next.js/React applications with Web Storage API, BroadcastChannel, and state synchronization for Stellar/Soroban web apps.

Implementation Approach

1. Versioned Storage Schema & Bounds: Implement a versioned schema in browser storage with bounded capacity (LRU eviction) that safely fails closed on corrupted or oversized storage.
2. Cross-Tab Synchronization: Synchronize read/unread state updates across open tabs in real-time via BroadcastChannel and storage events.
3. Deduplication & TTL Expiry: Enforce deterministic ID deduplication and timestamp-based TTL expiry across sessions and refreshes.
4. Automated Test Coverage: Write focused unit tests covering schema migration, corruption fallback, deduplication, expiry, and cross-tab event synchronization.

Estimate for First Draft PR

• Ready within 6–12 hours upon assignment.

Looking forward to your assignment before starting implementation!

[ranjeet150]

Hello @maintainers,

I would love to take this on. My planned approach:

• Deliver [Quality] Persist notification read state across sessions safely with proper loading/error states and clean component architecture.
• Test across viewport breakpoints and ensure 0 TypeScript or linting errors.

Looking forward to contributing—please assign whenever convenient!