Virtualize /transactions and /streams lists

[Jaydbrown]

Large accounts render hundreds of rows. Add windowing (react-virtual) to both list pages.

[ZacLou]

I'd like to work on this issue. I have relevant experience with this tech stack and can deliver a clean, well-tested PR. I can submit within 1-2 days.

[Ranjeet2063]

Hi maintainers, I would love to take up this issue.

I am a senior Web3 frontend engineer (#1 contributor on Mova Store with 28 successfully merged PRs), specializing in Next.js, React, TypeScript, Tailwind CSS, and Freighter/Stellar wallet integrations.

🎯 Technical Execution Plan for Virtualize /transactions and /streams lists:

1. Component Design & UI State: Implement Virtualize /transactions and /streams lists with clean component decoupling, responsive layouts, accessible forms/modals, and robust loading/skeleton/error boundaries.
2. Web3 & Client Logic: Wire real-time state streams, optimistic UI updates, and seamless Freighter wallet transaction signatures with user-friendly error alerts for rejections/timeouts.
3. Comprehensive Test Suite: Add component and unit tests (Vitest / Jest + React Testing Library) verifying state changes, input sanitization, and edge-case rendering.
4. Production Verification: Confirm zero TypeScript errors (noImplicitAny), zero ESLint/Prettier warnings, and clean production build (pnpm build).

💡 Why Assigning Me Directly Benefits You:

• Zero Maintenance Burden: Pixel-perfect UI with strict typing and responsive states that work out of the box.
• Rapid Turnaround: Ready to deliver a production-ready PR within 12–24 hours, clearing this task quickly.
• Track Record: 28 merged Web3 PRs — zero review ping-pong and immediate alignment with your conventions.

[Iker2522]

I'd like to take this issue on!

I can integrate react-virtual into both list pages to handle large account datasets efficiently without performance degradation.

I will wrap the account table/list components with useVirtualizer, dynamically calculating row offsets based on the container scroll position. This ensures only visible items are rendered in the DOM, keeping memory usage low and scrolling smooth even with hundreds or thousands of rows, while preserving existing table layouts, interactive states, and accessibility attributes.

I will also add unit tests to verify row virtualization