feat: improve ens caching of treasury votes table

[ECWireless]

Co-authored-by: Rick Staa rick.staa@outlook.com

Description

Module-level cache to avoid repeated ENS lookups across renders/navigations.

Type of Change

• feat: New feature
• fix: Bug fix
• docs: Documentation update
• style: Code style/formatting changes (no logic changes)
• refactor: Code refactoring (no behavior change)
• perf: Performance improvement
• test: Adding or updating tests
• build: Build system or dependency changes
• ci: CI/CD changes
• chore: Other changes

Related Issue(s)

Related: #539

^ closes and replaces the above PR

Changes Made

• Adds memory caching for ens lookups in the TreasuryVoteTable
• Includes ENS_CACHE_MAX_ENTRIES for edge case memory bloating
• Includes in-flight dedupes in case the same 2 address get looked up at the same time

Testing

• Tested locally
• Added/updated tests
• All tests passing

How to test (optional unless test is not trivial)

• Check the voting history of a proposal on a treasury proposal page; ensure ens names load quickly

Impact / Risk

Risk level: Low

Impacted areas: UI

User impact: faster ens name loads

Rollback plan: hotfix or Vercel rollback

Screenshots / Recordings (if applicable)

NA

Additional Notes

NA

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
explorer-arbitrum-one	Ready	Preview, Comment	Feb 25, 2026 1:46am

[Copilot]

Pull request overview

Adds a module-level ENS lookup cache for the TreasuryVoteTable to reduce repeated ENS provider calls across re-renders/navigations.

Changes:

• Introduces a bounded module-level Map cache for resolved ENS names (with LRU-like eviction).
• Adds in-flight request de-duplication so concurrent lookups for the same address share a single promise.
• Updates Apollo query fetchPolicy for treasury votes/events to "cache-and-network".

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[rickstaa]

@ECWireless looks good to me thanks. I however had two suggestions https://github.com/livepeer/explorer/pull/569/changes.

[Jipperism]

Had a look at this and @rickstaa suggested changes. I agree his changed should be merged into this PR as it's a bit cleaner. My only suggestion would be to change name in const ensCache = new Map<string, { name: string; timestamp: number }>(); to nameOrAddress as it can resolve to both, as seen in resolveEnsName.

[rickstaa]

Had a look at this and @rickstaa suggested changes. I agree his changed should be merged into this PR as it's a bit cleaner. My only suggestion would be to change name in const ensCache = new Map<string, { name: string; timestamp: number }>(); to nameOrAddress as it can resolve to both, as seen in resolveEnsName.

Good catch. Applied in d1d2743.

[rickstaa]

@Jipperism, @ECWireless I realized that when going out of office, I overlooked the fact that we already have a useEnsData hook that could improve this behavior. Will open up a replacement pull request.

[rickstaa]

Replaced by #572.