Implement RetryPolicy for 5xx RPC errors

[Emrys02]

Contribution Guide

• PRs go to the dev branch, not main
• Application must explain your specific approach to this task; generic applications will not be assigned
• PR description must clearly describe what you built and changed
• Link your PR to the correct issue number

RPC nodes may occasionally return 5xx Server Error responses due to temporary overloads or internal failures. Implementing a robust retry policy with exponential backoff will improve the resilience of the client.

Implementation Guidelines Key Files: crates/core/src/rpc/client.rs.
Expectations What done looks like: The client automatically retries requests that receive a 5xx status code, following an exponential backoff strategy before giving up.

For any question, reach me on Discord: emry_ss

[Guddy1-tech]

@Guddy1-tech has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I believe i can solve this issue

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

[Simongodw]

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

Good day,
You should consider assigning me this issue because I can implement a robust and production-safe RetryPolicy specifically tuned for transient 5xx RPC failures, ensuring improved system resilience without introducing request storms or duplicate side effects.

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

[Sulex45]

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

Hi I’d love to work on this

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

[0xElyte]

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

I would love to resolve this 💯

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

[boalambo]

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

i would like to work on this issue

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

[Clement-coder]

@Clement-coder has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

Hi, I’m a full-stack software and Rust engineer with experience in resilient RPC clients and distributed systems.

I’ll implement a RetryPolicy for 5xx RPC failures in crates/core/src/rpc/client.rs, adding exponential backoff with a safe retry cap to improve reliability under node instability.

Specific approach: intercept HTTP 5xx responses in the RPC client layer, apply exponential backoff with jitter to avoid thundering herd issues, and ensure retries are bounded to prevent infinite loops or request hangs. I’ll also keep behavior configurable and ensure existing success paths remain unchanged.

Robust, fault-tolerant, and production-safe.

I can start immediately and deliver quickly.

Would love to be assigned.

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

[N-thnI]

@N-thnI has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Dear maintainer
Please assign me this issue

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

[drips-wave]

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

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