Add configurable request timeouts to RPC providers

[Lakes41]

Difficulty: Intermediate
Type: Feature
Recommended labels (if available in this repo): enhancement, reliability, sdk

Background

src/contracts/providers/jsonRpcProvider.ts and webSocketProvider.ts wrap the underlying RPC transports, but neither currently exposes a configurable per-request timeout — a hung RPC connection can block an access check indefinitely.

Problem

Without a timeout, a slow or unresponsive RPC endpoint causes access checks to hang rather than failing fast (which would allow the adaptive provider or caller to fail over or surface a clear error).

Expected Outcome

Both providers accept a requestTimeoutMs config option; requests exceeding the timeout are aborted and rejected with a typed TimeoutError.

Suggested Implementation

Use AbortController (or the transport library's native timeout support) to enforce the timeout in both providers. Ensure the WebSocket provider's timeout doesn't tear down the underlying persistent connection, only the individual pending request. Surface timeouts through healthTracker.ts so the adaptive provider can factor timeout frequency into its health scoring.

Acceptance Criteria

• requestTimeoutMs is configurable via networkConfig.ts / sdkConfig.ts, with a sensible default
• Timed-out requests reject with a typed TimeoutError, not a generic error
• WebSocket provider timeout does not close the underlying socket connection
• Unit tests simulate a hung request and verify timeout behavior for both providers
• pnpm test:run passes

Likely Affected Files/Directories

• src/contracts/providers/jsonRpcProvider.ts
• src/contracts/providers/webSocketProvider.ts
• src/contracts/providers/healthTracker.ts
• src/config/networkConfig.ts

[subheeksh5599]

hi, interested. shipped anchorfx backend with 10+ api routes handling soroban rpc timeouts with exponential backoff. same pattern.

approach:

1. add requestTimeoutMs to jsonRpcProvider.ts and webSocketProvider.ts via AbortController
2. ws provider: abort only individual request, not underlying socket
3. surface timeouts through healthTracker for adaptive provider scoring
4. configurable via networkConfig.ts with sensible default
5. typed TimeoutError, not generic
6. unit tests: simulate hung request, verify timeout + rejection

[grantfox-oss]

🦊 GrantFox — @subheeksh5599 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #424)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@subheeksh5599's PR #437 was approved and merged by @Lakes41.

🏆 @subheeksh5599: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (223 total points). Track your full progress on GrantFox.

👏 Great work, @subheeksh5599! Keep contributing to Adamantine-guild.