`useProfile`'s verification check swallows all errors into `false`, masking real failures as "not verified"

[K1NGD4VID]

Category: Functional Edge Case

Repository location: apps/web/hooks/useProfile.ts (isVerifiedQuery, lines ~87-101)

Problem
Any failure calling the registry contract — including a transient RPC/network failure or a misconfigured registryContractID — is caught and converted into isVerified: false, with isVerifiedError always null since the error never reaches react-query's error state. Downstream UI that gates issuer actions on isVerified will incorrectly tell an already-verified user they're unverified during a network blip, with no way to distinguish "actually unverified" from "couldn't check."

Evidence

queryFn: async (): Promise<boolean> => {
  if (!address) return false;
  const client = new RegistryClient(registryContractID);
  try {
    const verified = await client.isVerified(address, address);
    return verified;
  } catch (err) {
    captureError(err);
    return false; // any error becomes "not verified"
  }
},

Suggested implementation
Re-throw the error instead of swallowing it to false, so react-query's error state carries it, and let the UI branch explicitly on isVerifiedError vs. a genuine isVerified === false.

Acceptance criteria

• A simulated RPC failure during the verification check surfaces via isVerifiedError, not as isVerified: false.
• The UI shows a distinct "couldn't verify status, try again" state instead of "not verified" when the check itself fails.

Difficulty: Easy

Expected impact: Prevents legitimately verified issuers from being incorrectly blocked from issuer actions during transient failures.

---

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

[xtep103]

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

Hi there, I’ve carefully reviewed the issue details and I’m confident I can provide a clean, efficient, and maintainable solution.

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

[badmusdare4]

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

I would love to work on this issue.

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

[Duyicoda]

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

Hi maintainer 👋

I’d love to work on this issue and ensure verification errors are surfaced correctly instead of being treated as “not verified,” with a clear UI state for temporary failures.

Please assign it to me! 🙌

ETA: 24 hours

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

[luciusverus-cyber]

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

HELLO MAINTAINER CAN I WORK ON THIS?????

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

[drips-wave]

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

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