[Wave 9] Implement the Stellar batch-sender contract path

[truthixify]

Problem

src/chains/stellar/tx-builder.ts detects batchSenderContract but throws instead of building the Soroban invocation. The public option is therefore misleading.

Done when

• Build the contract invocation with the correct transfer schema.
• Support native XLM and the documented asset path.
• Return the contract transaction and generated stealth metadata.
• Add tests for success, invalid contract configuration, and operation limits.

[SixtusEzeogu]

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

After going through the task and its requirements, I’m confident I can implement a solution that aligns with the expected design and acceptance criteria.

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

[abdulraheemabdullahi30-tech]

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

Dear Maintainers,

I’ve reviewed the issue and understand that "tx-builder.ts" currently detects "batchSenderContract" but does not complete the Soroban contract invocation, making the public option non-functional.

I’d like to take ownership of implementing this path, including constructing the correct transfer invocation, supporting both native XLM and the documented asset flow, and returning the expected contract transaction and generated stealth metadata. I’ll also cover the required validation and edge cases, including invalid contract configuration and operation limits, with focused tests for successful and failing scenarios.

I’ll first review the existing Stellar transaction-building and stealth metadata patterns in the SDK so the implementation remains consistent with the project’s architecture and existing APIs. I’m ready to deliver a clean, tested implementation against the stated acceptance criteria.

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

[joshuasaleh200-spec]

@joshuasaleh200-spec has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I would like to work on this issue because I have the necessary experience and skills to solve it.

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

[d1a-m3n]

@d1a-m3n has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello! I’d love to contribute to this project by taking on this issue. I’ve read the requirements thoroughly—please assign it to me.

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

[boalambo]

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

Hello maintainer, I would like to work on this issue

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

[Faizehy]

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

Hello Maintainer,

I’d like to take on this issue. I’ll first trace the existing Stellar transaction-building flow in src/chains/stellar/tx-builder.ts, the batchSenderContract configuration, and the current Soroban/XLM transfer handling so the implementation follows the SDK’s existing transaction and stealth-metadata conventions.

I’ll replace the current unsupported-path failure with a proper Soroban contract invocation using the expected batch-transfer schema. I’ll handle both native XLM and the documented asset path, preserve the existing stealth metadata generation, and ensure the resulting contract transaction is returned through the same builder interface without changing unrelated Stellar paths.

I’ll add focused tests covering a valid native XLM batch, the documented asset flow, invalid contract configuration, and operation-limit boundaries. I’ll also verify the generated invocation arguments and returned stealth metadata rather than testing only that transaction construction succeeds.

I’ll keep the change scoped to the batch-sender contract path and its required tests, following the project’s existing Stellar/Soroban abstractions rather than introducing a parallel transaction-building flow.

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

[helenahelenavanbeek-png]

@helenahelenavanbeek-png has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I’m a full-stack software developer experienced in both enterprise applications and Web3 projects, with four hackathon wins and hands-on work across frontend, backend, APIs, databases, and blockchain integrations. I will first review the issue and existing codebase, then implement a clean, well-tested solution and submit a clear PR within the agreed timeline. Kindly assign.

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

[fwseyi]

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

Hi, can i work on this issue

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

[drips-wave]

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

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