Expose LRU cache hit/miss metrics

[Jaydbrown]

StreamsModule._addrCache / FactoryModule address cache — expose counters so consumers can tune maxConcurrency / cache size.

[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 Expose LRU cache hit/miss metrics:

1. Component Design & UI State: Implement Expose LRU cache hit/miss metrics 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.

[Ranjeet2063]

Hi maintainers,

I have resolved this issue by introducing getAddressCacheMetrics() and resetAddressCacheMetrics() on FactoryModule and StreamsModule in PR #685:
#685

Summary of Changes:

• Exported CacheMetrics interface (hits, misses, size)
• Instrumented streamAddress to track both positive and unexpired negative cache hits vs misses
• Added getAddressCacheMetrics() and resetAddressCacheMetrics()
• Added unit tests covering initial counters, positive & negative hits, misses, reset, and clear in src/tests/factory.test.ts (all 24 tests green)
• Verified full build and entire test suite (1026 tests passing)

[abojeEdwin]

Hi maintainer, I've gone through the issue and I have a clear understanding of the fix for this issue. I'd love to be assigned to this issue. Thank you