Skip to content

feat: add realtime account state and resilience - #421

Open
iam-mercy wants to merge 1 commit into
Refract-Protocol:mainfrom
iam-mercy:feat/realtime-resilience-profiling
Open

iam-mercy wants to merge 1 commit into
Refract-Protocol:mainfrom
iam-mercy:feat/realtime-resilience-profiling

Conversation

@iam-mercy

@iam-mercy iam-mercy commented Oct 21, 2026 •

Copy link
Copy Markdown

Summary

  • Add account-scoped Stellar balance snapshots and live account topics, cold-start/fallback hydration, and post-transaction optimistic balance updates in the Navbar.
  • Persist stale-while-revalidate snapshots by topic, network, wallet, and schema version; handle unavailable storage and quota pressure.
  • Isolate realtime-backed page regions with REST fallbacks and degraded-topic reporting.
  • Add dev-only realtime render profiling, disconnected/streaming benchmark scenarios, committed performance budgets, and Lighthouse INP/TBT signals.

Verification

  • Focused realtime tests: 5 files, 8 tests passed.
  • node --check scripts/realtime-benchmark.mjs and git diff --check passed.
  • Full Vitest, typecheck, build, and lint remain blocked by existing repository issues: unrelated full-suite failures, broad baseline TS errors (including Playwright config and incomplete exports), and pre-existing lint violations. The benchmark could not be run because the production build cannot pass type validation.
  • Commit hook encountered the existing hard-coded color violations after parsing its invalid selector was fixed; commit created with the authenticated identity and no co-authors.

Closes #284
Closes #285
Closes #286
Closes #287

@drips-wave

drips-wave Bot commented Oct 21, 2026

Copy link
Copy Markdown

@iam-mercy Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment