Add a shared Soroban RPC server accessor to TrustFlowClient

[meshackyaro]

Description

This issue aims to address the implementation of Shared Soroban RPC Server Accessor on TrustFlowClient.

The core objective is to: Add a client.getSorobanServer() method to TrustFlowClient (mirroring its existing getServer() for Horizon) so that src/contract/invoke.ts, src/contract/read.ts, and src/contract/simulate.ts share one RPC server instance per client instead of each independently calling new SorobanRpc.Server(SOROBAN_RPC_URLS[client.network]). Today all three files construct their own throwaway RPC server client on every single call, with no caching or connection reuse, and any future cross-cutting change (timeouts, auth headers, retry wiring) would need to be applied in three separate places.

By completing this feature, we will ensure that the TrustFlow protocol maintains its high standards for security, usability, and decentralized logic. This issue requires careful attention to the SDK Wrapper architecture and adherence to the existing project conventions.

Component

SDK

Difficulty

🔴 Hard

Tasks

• Review existing Typescript abstract classes (TrustFlowClient in src/client.ts, which already exposes getServer() for Horizon.Server)
• Implement SDK method for: a getSorobanServer() accessor on TrustFlowClient that lazily constructs and caches a SorobanRpc.Server (once the SorobanRpc import is fixed per a companion issue)
• Update src/contract/invoke.ts, read.ts and simulate.ts to use the new client.getSorobanServer() instead of constructing their own instances
• Update typedoc comments for the new method
• Write Jest tests validating the accessor returns a consistent, cached instance
• Run npm run build to verify standard bundling

Acceptance Criteria

• Feature accurately implements the objective: a client.getSorobanServer() method exists and is reused by contract/invoke.ts, read.ts and simulate.ts
• contract/invoke.ts, read.ts and simulate.ts no longer each construct their own SorobanRpc.Server instances
• Any PR that introduces TypeScript errors is automatically blocked
• Code is properly reviewed and approved by codeowners

Estimated Time

2-3 days

[OkeA-dev]

@OkeA-dev has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintain,I will love to work on this issue,I have an experience and I have already reviewed the issue please assigned me to it and I will give a good result.

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

[OkpunTakem]

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

I would like to work on this issue.

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

[sadiqolalere41-pro]

@sadiqolalere41-pro has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer.
I'll resolve this issues an fix it correct.
Please assign me to this issue.

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

[barnabasolutayo-lgtm]

@barnabasolutayo-lgtm has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Good evening Maintainer. Please assign this issue to me. I'm begging

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

[Johnsource-hub]

@Johnsource-hub has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on this issue. I understand the problem described and I’m confident I can investigate it, implement the necessary changes, and test the solution properly.

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

[Majormaxx]

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

Hi team, can I tackle this? ETA is 4 hours

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

[drips-wave]

Congratulations, @Majormaxx! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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