[Wave 9] Add request timeouts to Horizon and Soroban RPC clients

[truthixify]

Problem

The Horizon and RPC clients retry failed requests, but a request that never resolves can hold a scan indefinitely.

Done when

• Add configurable connect and request timeouts.
• Abort timed-out fetches before retrying or failing over.
• Preserve the original endpoint and attempt in the typed error.
• Add fake-fetch tests for timeout and retry behavior.

[legend-esc]

@legend-esc has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.

I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.

My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.

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

[Immaculate0606]

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

I’d love to work on this.

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

[6tamichael-boop]

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

Hi Maintainer, I’d be glad to take on this issue. I have experience with similar tasks and can get started immediately. I’m confident I can deliver a clean and reliable solution that meets the requirements.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @6tamichael-boop to this issue.

[Nelsonkay]

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

Hello Team, I’d like to take on this issue. I have experience as a backend developer and have worked with different frameworks. I’m confident I can handle it and find a solution. Looking forward to working on it.
Thanks.

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

[Jerryvic911]

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

Hi, I’d like to work on this issue. I’ll add configurable connect/request timeouts to the Horizon and Soroban RPC clients, ensure timed-out requests are properly aborted before retries/failover, preserve endpoint and attempt information in typed errors, and add fake-fetch tests covering timeout and retry behavior.

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

[d1a-m3n]

@d1a-m3n has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello! I have 3+ years of experience. I’d love to contribute to this project by taking on this issue. I’ve read the requirements thoroughly—please assign it to me.

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

[aratass]

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

I'd like to take this one. I have a merged PR in this repo (#215) and two open ones (#216, #218), and I have already worked through createRpcClient's retry, circuit-breaker and failover loop and createHorizonClient's retry policy.

Plan:

• Add timeout options to both clients: a connect timeout (time until response headers arrive) and a request timeout (the whole request, body included), configurable per client and per call.
• Give every attempt its own AbortController, so a timed-out fetch is really aborted before the next retry or the failover, instead of being left running in the background.
• Report a timeout as a typed error in the existing WraithNetworkError family, carrying the endpoint URL, the attempt number and which timeout fired.
• Fake-fetch tests with fake timers: a hanging request times out and is retried; timeouts on every attempt fail over to the next endpoint; a slow body hits the request timeout; the timed-out fetch receives the abort; no timers are left behind.

I'll open the PR soon after assignment, leaving time for review before the wave closes.

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

[drips-wave]

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

🧑‍💻 @aratass: 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 @aratass as part of the Stellar Wave Program's 9th Wave 🥳

😎 @aratass: You earned 400 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.