Stellar Soroban contract spec extraction helper

[truthixify]

Tier: M (2-4 days) Type: feature

Context

Tooling that wants to interact with arbitrary Wraith deployments needs to discover the contract's spec dynamically. Stellar CLI can extract spec from a deployed contract; expose this in the SDK.

Scope

• extractContractSpec(contractId, network) returns parsed spec (function signatures, types)
• Uses Soroban RPC's contract data endpoint
• Caches results per (contractId, version)
• Generates TypeScript types on demand (optional helper)

Acceptance criteria

• Helper + tests
• Integration test against deployed Wraith contracts
• Type generation helper (optional flag)
• Documentation

Files to start with

• New: sdk/src/chains/stellar/spec.ts

[beebozy]

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

Hi sir, could you please assign me this issue?

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

[Timrossid]

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

Hi, I just reviewed the issue description and I will like to work on this issue. I’m a full-stack developer and Smart contract expert, I have previously contributed to multiple open-source projects. Please assign this issue to me! I can have a PR ready for review in a few hours.

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

[drips-wave]

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

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

[truthixify]

@beebozy Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. Silence is the only thing that costs you the assignment; if you get stuck or context changes, just say so on the PR.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building.