You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Branch: Open your PR against dev. PRs targeting main are closed automatically.
Description:
Write apps/web/docs/contracts-client-data-at-rest.md: every place the web client keeps data — memory, localStorage, sessionStorage, IndexedDB, the service-worker cache — with what is stored and whether it is sensitive. #282 covers IndexedDB schemas; this covers every storage location and what happens to each on logout.
Acceptance criteria:
One table: storage location, key or store name, contents, sensitivity (private key / plaintext / metadata / non-sensitive), and source module
Covers at minimum: device ID and identity public key in localStorage (deviceIdentity.ts), trusted identity snapshots (identityTrust.ts), the in-memory plaintext cache (crypto/plaintextCache.ts, cleared on unload), the local search index, session and prekey stores, and the auth token
Documents what logout and device revocation clear, and lists anything that survives them as a known gap
Flags NEXT_PUBLIC_AUTH_TOKEN as a fallback token source in lib/auth.tsx and states that it must never be set in a production build
Congratulations, @kosisochukwu1234! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @kosisochukwu1234: 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.
Activity
olubukolatanko209-doc commentedon Oct 20, 2026
@olubukolatanko209-doc has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @olubukolatanko209-doc to this issue.
Mawuli-tech commentedon Oct 20, 2026
@Mawuli-tech has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mawuli-tech to this issue.
kosisochukwu1234 commentedon Oct 20, 2026
@kosisochukwu1234 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @kosisochukwu1234 to this issue.
drips-wave commentedon Oct 20, 2026
Congratulations, @kosisochukwu1234! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @kosisochukwu1234: 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 🌊
github-actions commentedon Oct 28, 2026
Closed by #692, merged into
dev.