Stellar Liquidity Pool swap-then-stealth helper

[truthixify]

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

Context

Sender holds USDC, recipient prefers XLM. Use Stellar AMM to swap then send to stealth address, all atomically. Helper builds this combined transaction.

Scope

• buildStellarSwapAndStealth({ fromAsset, toAsset, amount, recipientMeta }) returns single transaction
• Uses pathPaymentStrictReceive or liquidityPoolDeposit/Withdraw as appropriate
• Slippage protection (configurable)
• Stealth address still receives the announcement
• Tests against testnet AMM

Acceptance criteria

• Helper + tests
• Slippage protection documented
• Integration test with testnet pools
• Documentation page with worked example

Files to start with

• New: sdk/src/chains/stellar/swap.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 this issue to me, I am software developer and I have worked accross different chains, stellar etheruem , and other ecosystem.. Kindly assign me

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

[Mathew2k-hash]

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

I'd like to work on this issue because it combines several core Stellar capabilities—AMM swaps, path payments, and privacy-preserving transfers—into a single developer-friendly abstraction. Building an atomic swap-and-send flow with proper slippage protection would provide significant value to applications integrating the SDK.

I'll implement the helper, document the slippage model, add comprehensive unit and integration tests against Stellar testnet pools, and ensure the resulting transaction correctly delivers funds and stealth announcements in a single workflow.

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

[truthixify]

@Mathew2k-hash 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.

[drips-wave]

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

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