Hydrate persisted TanStack Query cache on client app boot

[king-aj-the-first]

GitHub labels: Stellar Wave

Drips complexity: High (200 points)

Area: Performance

Description

lib/queryPersistence.ts defines persistence helpers, but app/providers.tsx does not restore the dehydrated cache on first paint.

Requirements and Context

Returning users should see cached marketplace data instantly while revalidating. Wire persistQueryClient restore in Providers.

Suggested Execution

git checkout -b feat/query-persistence-hydration

1. Create branch feat/query-persistence-hydration
2. Integrate queryPersistence in app/providers.tsx
3. Restore cache before rendering data routes
4. Skip persistence for wallet/tx sensitive keys
5. Add test for dehydrate/hydrate round-trip

Example commit message

feat(performance): hydrate persisted TanStack Query cache on boot

File Paths

• lib/queryPersistence.ts
• app/providers.tsx
• lib/queryKeys.ts

Guidelines

• Assignment required before starting
• PR description must include: Closes #<issue_number>
• Run npm run lint, npm run type-check, npm run test, and npm run build before opening PR
• Add screenshots or recordings for UI changes
• Complexity: High (200 points) — complex engineering work touching multiple modules

Acceptance Criteria

• Cache restores on reload for marketplace queries
• Wallet routes are excluded from persistence
• Stale data revalidates in background
• No hydration mismatch errors
• Test covers round-trip

[ToryMic]

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

Hey, I've checked your issue and I can work on it.

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

[martinzhames]

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

Hi maintainer can i please work on this issue

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

[drips-wave]

Congratulations, @martinzhames! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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