[amilz]

confirmTransaction makes a detached getSignatureStatus call after subscription setup as an early-settlement optimization. It had no rejection handler, so a transient transport or JSON-RPC failure surfaced as an unhandled promise rejection, which terminates modern Node processes by default.

The call is only an optimization; the signature subscription and the expiry strategy's final status check already settle the confirmation. Its failure is now caught and ignored.

Test: first getSignatureStatuses rejects, subscription never responds, block height passes lastValidBlockHeight. Asserts no unhandledRejection fires and the transaction still confirms via the expiry path.

Fixes DEV-1132

[linear]

DEV-1132

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge because the ignored request is optional and all confirmation strategies retain independent settlement paths.

Summary

This PR prevents failures from an optional post-subscription signature-status check from escaping through its detached async task.

• Catches and ignores fallback status-check failures while leaving subscription and expiry settlement intact.
• Adds regression coverage for a transient status transport failure followed by successful confirmation through the block-height expiry path.

_{Reviews (1) · Last reviewed commit: "fix(web3.js): keep signature-status fall..."}

[dev-jodee]

Error handling: catch transient sig-status fallback errors to prevent unhandled rejections. CI green.