`useProfile` constructs a new `RegistryClient` on every call instead of memoizing it

[K1NGD4VID]

Category: Performance

Repository location: apps/web/hooks/useProfile.ts (lines ~71, 91, 112)

Problem
useProfile does const client = new RegistryClient(registryContractID); independently in three separate places (once per query/mutation), re-constructing the SDK client object on every refetch or mutation call — including on each interval-based refetch. usePool.ts already establishes the correct pattern: const poolClient = useMemo(() => new PoolClient(poolContractID), []);.

Evidence
useProfile.ts has three separate new RegistryClient(registryContractID) call sites; usePool.ts line ~32 memoizes its client with useMemo.

Suggested implementation
Memoize a single RegistryClient instance the same way usePool does, and reuse it across all three call sites in useProfile.

Acceptance criteria

• useProfile constructs exactly one RegistryClient instance per mount, verified by a test that spies on the RegistryClient constructor.

Difficulty: Easy

Expected impact: Removes avoidable object churn on a hook that polls/refetches regularly.

---

Filed as part of the second repository-wide audit (deeper refinements following the first cleanup pass).

[Niffy03]

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

Hi there, I think i handle this.

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

[Emmycivity]

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

Having carefully examined the details, I’m confident I can resolve the issue effectively while keeping the solution clean and efficient.

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

[DeePrincipal-dev-lang]

@DeePrincipal-dev-lang has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi there! I'd like to work on this issue if it's still open.

I'm a prompt engineer who takes a detail oriented, methodical approach to debugging and testing. I've gone through the issue description and have a clear plan for tackling it, happy to walk through my approach first if that helps with review.

I can start right away and will share progress along the way, including test coverage and the PR link, so it's easy to follow.

Would love to take this one on. Thanks for maintaining the repo!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DeePrincipal-dev-lang to this issue.

[Oyinkans0la12]

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

Can i work on this please?

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

[drips-wave]

Congratulations, @Oyinkans0la12! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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