Consolidate duplicate Stellar config across lib/config/stellar.ts, lib/soroban-client.ts and lib/soroban/client.ts

[Baskarayelu]

📋 Description

There are overlapping Stellar/Soroban modules: lib/config/stellar.ts, lib/soroban-client.ts, and lib/soroban/client.ts (the latter holding the withRetry wrapper). The duplication risks divergent network passphrases/RPC URLs and makes it ambiguous which client a new contributor should use.

This issue consolidates the Soroban client into a single canonical module and re-exports for back-compat, deferring network resolution to lib/contracts/network-resolution.ts.

Why this matters: two clients with different config is a classic source of "works on testnet, breaks on mainnet" bugs.

🎯 Requirements & Context

• Pick one canonical client module; migrate callers.
• Keep the withRetry timeout/retry wrapper in the canonical module.
• Provide thin re-exports from the old paths to avoid breaking imports, with @deprecated TSDoc.

Context & constraints

• No behavioural change to retry/timeout semantics.
• Use the existing network-resolution helper for passphrase/RPC.

🛠️ Suggested Execution

git checkout -b refactor/consolidate-soroban-client

• Consolidate + re-export; TSDoc deprecations.
• Run existing contract tests to confirm no regressions.

npx vitest run && npx tsc --noEmit && npm run lint && npm run build

refactor(soroban): consolidate duplicate Stellar client modules

✅ Acceptance Criteria & Guidelines

Requirement	Target
Single canonical client	Required
Back-compat re-exports	Required
Retry semantics preserved	Required
tsc --noEmit, lint, build clean	Required
Timeframe	96 hours from assignment

💬 Community & Support

Join the RemitWise contributor community on Discord: https://discord.gg/CtQuPZFMA

Comment to claim and ask questions in the channel. 🚀

[dominiccreates]

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

I would like to work on this issue because i am confident i can resolve the issue, having worked on and resolved similar issues. my eta is 4 hours

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

[grantfox-oss]

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

Next steps:

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

Good luck! Track your progress on GrantFox.

[drips-wave]

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

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