Batch send UI for splitter contract

[truthixify]

Tier: L (1-2 weeks) Type: feature

Context

stealth-splitter (PR #42) shipped but has no demo UX. Build a "split a payment among N recipients" flow.

Scope

• New page /split (or modal on Send page)
• Form: list of (recipient meta-address, weight), single funded amount
• Compute weighted shares; surface dust handling
• Build split definition, fund split atomically
• Show success state with per-recipient stealth addresses

Acceptance criteria

• Page or modal implemented
• Per-recipient validation
• Successful flow demo'd end-to-end on testnet
• Playwright test

Files to start with

• src/components/StellarSend.tsx (extend)
• New: src/components/StellarSplit.tsx

[stpatrickghost]

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

Can I work on this issue?

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

[paulinaapeh8]

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

Please I will like to work on this issue. Thank you

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

[drips-wave]

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

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

@paulinaapeh8 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.