[Issue #293] Perf: Virtualise Long Transaction History Lists

[Ogstevyn]

The history page renders all transactions as DOM nodes. With 100+ transactions this causes visible lag on scroll.\n\nInstall @tanstack/virtual (TanStack Virtualizer). Virtualise the transaction list so only visible rows are in the DOM.\n\nAcceptance Criteria: With 500 mock transactions, scrolling the history page shows no frame drops.\n\nFiles: components/history/TransactionList.tsx (Modify), package.json (Modify)

[khanavi272-spec]

@khanavi272-spec has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue

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

[Danielobito009]

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

i would love to work on this issue, please assign me to this .

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

[Agbeleshe]

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

Hello, can I handle this? I have experience optimizing React and Next.js applications for performance, including bundle size reduction, code splitting, lazy loading, and Lighthouse score improvements. After reviewing the issue, I understand that the goal is to prevent Three.js from being included in the initial landing page bundle by converting DottedSurface to use dynamic imports with React.lazy and Suspense, allowing the component to load only after the page becomes interactive. I can update components/ui/dotted-surface.tsx and app/page.tsx to implement an efficient lazy-loading strategy, provide an appropriate loading fallback, and verify that the Three.js bundle is deferred from the critical rendering path. I will also validate the impact through bundle analysis and Lighthouse testing to ensure the optimization delivers the expected performance improvement while preserving the existing user experience. I focus on writing clean, maintainable frontend code with measurable performance gains and am available to start immediately. I would appreciate the opportunity to contribute and look forward to hearing from you.

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

[devchant]

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

Hi, I would love to fix this. I have experience optimizing React and Next.js applications, including code splitting, lazy loading, and bundle size reduction. I can update DottedSurface to use React.lazy and Suspense, ensuring Three.js is loaded only after the landing page becomes interactive. I'll also verify the improvement through Lighthouse testing and ensure the existing user experience remains unchanged. I can get started right away and would be happy to contribute.

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

[drips-wave]

Congratulations, @devchant! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

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