Auto-generate TypeScript bindings for Stellar contracts

[truthixify]

Labels: Stellar Wave, stellar, tooling, dx, drips, help-wanted
Tier: M (2–4 days)
Type: tooling

Context

The SDK currently hand-writes Stellar contract call payloads in sdk/src/chains/stellar/. When a Soroban contract function signature changes, the SDK can silently drift. EVM avoids this through typechain; Solana avoids it through Anchor IDL. Stellar has its own bindings generator (stellar contract bindings typescript) but we don't use it yet.

We want generated, type-safe bindings checked into the contracts repo that the SDK can consume.

Scope

1. Set up a contracts/stellar/bindings/typescript/ directory.
2. Add a script contracts/stellar/scripts/generate-bindings.ts that:
   • For each contract crate, runs stellar contract bindings typescript --contract-id ... --network ... --output-dir bindings/typescript/<contract-name> against the testnet deployment.
   • Post-processes the output to use named exports (some generator versions default to default exports).
   • Writes a top-level index.ts re-exporting all per-contract clients.
3. Wire it into the build: pnpm bindings:stellar runs the generation, pnpm build:stellar depends on it.
4. Add a CI step that re-runs the generator on every push and fails if the diff is non-empty (drift detection).
5. Document the SDK migration path in a follow-up issue: how sdk/src/chains/stellar/ should switch from hand-written calls to these bindings.

Acceptance criteria

• Bindings generated for all four contracts and checked in.
• CI drift-check job in .github/workflows/.
• README section "Generated bindings" explaining when to regenerate.
• A draft SDK PR (separate) demonstrating one function call (e.g., stealth-registry::stealth_meta_address_of) wired through the generated client.

Why not do this in the SDK repo?

The contract source is the source of truth. Keeping bindings here means every contract PR can update bindings atomically with the implementation change, and downstream consumers (SDK, demo, indexers) all sync from the same artifact.

Resources

• stellar contract bindings: https://developers.stellar.org/docs/tools/developer-tools/cli/install-cli
• SDK target file once bindings exist: sdk/src/chains/stellar/announcements.ts

[Jopsan-gm]

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

Hello maintainers 👋

I’ve reviewed this issue and explored the relevant parts of the codebase to understand the current architecture and constraints.

I’m a full-stack developer with hands-on experience contributing to real-world open source projects across both Web2 and Web3 environments. My work includes JavaScript/TypeScript stacks, React on the frontend, and Node.js on the backend. Additionally, I have experience working with smart contracts and blockchain-related systems, including writing and understanding contract logic, as well as interacting with on-chain data.

I’m also familiar with Rust, particularly in the context of modern blockchain ecosystems, and comfortable navigating lower-level concepts when needed.

I’m confident working within existing codebases, reasoning about system design (both on-chain and off-chain), and delivering clean, maintainable solutions that align with project standards. I’m used to collaborating through GitHub workflows, iterating based on feedback, and communicating clearly during the development process.

This issue aligns well with my experience, and I’m confident I can deliver a solid and reliable implementation. I’d be glad to take it on if it’s still available.

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

[drips-wave]

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

🧑‍💻 @Jopsan-gm: 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]

Resolved by #29 (merged into develop).

[drips-wave]

This issue has been completed by @Jopsan-gm as part of the Stellar Wave Program's 5th Wave 🥳

😎 @Jopsan-gm: 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.