bug: empty / silent catch blocks hide errors across the codebase

[nanaf6203-bit]

Summary

Several catch blocks silently swallow errors, returning defaults or doing nothing.

Affected area

(every try { … } catch { } or near-empty catch observed in repo)

• src/utils/security/blockchainSecurity.ts — falls back to default score, hides errors
• src/utils/security/phishingProtection.ts — silently returns unsafe=false
• src/utils/walletHelpers.ts — returns null
• src/hooks/useSearchHistory.ts — JSON.parse failures disappear
• src/hooks/useCurrencyConverter.ts — silently fails rate fetch
• src/components/ViewToggle.tsx — swallows localStorage errors

Steps to reproduce / impact

Silent catch blocks hide regressions, data corruption, and intermittent outages from observability tools. Users experience mysterious failures.

Expected behaviour

At minimum, log via logger.warn/logger.error and add structured context. Trigger user-visible toasts when the failure affects UX.

Acceptance criteria

• Sweep empty catch blocks; require at least a structured log.
• Add ESLint rule or codemod nudging engineers.
• Verify Sentry / error reporting picks the error up.

[laraba9987-cmyk]

@laraba9987-cmyk has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i would like to work on this issue

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

[Akinyemi04]

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

I would like to work on this issue

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

[Johnpii1]

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

Hello Sir,

I came across your project and I’m really interested in contributing.

I have experience with React for building responsive, user-friendly interfaces, and I’m also familiar with smart contracts and blockchain basics. I focus on writing clean, scalable code and improving user experience.

I’m a fast learner and ready to get started immediately. Please let me know the next steps.

Thank you.

Best regards,
Johnpaul

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

[OmniZlatoon]

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

Good morning maintainer I would like to work on this issue and assure you that I'll complete the task in a short period of time with efficient and expected output

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

[drips-wave]

Congratulations, @laraba9987-cmyk! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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

[drips-wave]

This issue has been completed by @laraba9987-cmyk as part of the Stellar Wave Program's 6th Wave 🥳

😎 @laraba9987-cmyk: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.