Stellar batch operation builder (atomic multi-op transactions)

[truthixify]

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

Context

Stellar supports up to 100 operations per transaction with atomic semantics. Useful for stealth scenarios: send to N stealth addresses + emit N announcements in one tx without needing the splitter contract.

Scope

• StellarBatchBuilder that accepts multiple stealth payment configs
• Builds a single transaction with the corresponding ops
• Validates total fee against account balance
• Splits into multiple transactions if op count > 100
• Returns transaction(s) ready to sign

Acceptance criteria

• Builder + tests
• Op-count splitting logic
• Documentation
• Demo follow-up for batch send UI

Files to start with

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

[fadesany]

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

Hello maintainer, i would like to work on this issue

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

[drips-wave]

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

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

@fadesany 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. If you get stuck or context changes, just say so on the PR — silence is the only thing that costs you the assignment.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building. Looking forward to the PR.