[Frontend] Add Catch and Error State to useBlockchainSync.syncRecord

[llinsss]

Description

src/hooks/useBlockchainSync.ts (line ~16) has a try block in syncRecord with no corresponding catch — an exception during sync propagates uncaught instead of setting an error state the UI can display.

Current State

• syncRecord's try block has no catch clause

What Needs to Be Fixed / Built

• Add a catch clause that sets an error state on the hook
• Ensure consumers of this hook (e.g. BlockchainSyncStatus.tsx) render that error state

Acceptance Criteria

• A failed sync sets a visible error state instead of throwing uncaught
• Covered by the related useBlockchainSync unit test issue

Files to Modify

• src/hooks/useBlockchainSync.ts

Priority

Medium-High — silent sync failures mean records may never get anchored without anyone noticing

Estimated Effort

0.5 day

[Mykelsown]

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

I would like to take this one. It is a focused, well scoped fix and matches the kind of hook level error handling I work with regularly in React. I will add a catch clause to syncRecord that sets a clear error state on the hook, then update BlockchainSyncStatus.tsx to render that state so a failed sync is visible instead of throwing uncaught. I will keep the change minimal and consistent with the existing hook structure.

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

[drips-wave]

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

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