Custom Stellar Asset Contract send tests (extend SAC matrix)

[truthixify]

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

Context

The SAC compatibility audit (#43) covered seven SAC variants. Production use will surface real-world tokens: USDC, EURC, AQUA, MOBI, BLND. Need integration tests against actual issued assets on futurenet to validate the matrix predictions.

Scope

• Pick 5 well-known issued assets on Stellar testnet/futurenet
• For each: send through stealth-sender, verify announcement, verify withdraw
• Document any divergence from the matrix predictions in stellar/audits/2026-06-sac-compatibility.md
• Add CI smoke job (allow-flaky)

Acceptance criteria

• 5 integration tests against real testnet assets
• Matrix doc updated with empirical observations
• CI smoke job
• Asset-discovery script: list all known testnet issued assets for the contributor

Files to start with

• stellar/stealth-sender/tests/sac_compat.rs
• stellar/audits/2026-06-sac-compatibility.md

[DevSolex]

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

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

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

[cashflaretech-glitch]

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

Hi Maintainer, please assign me to this issue. Thanks for your consideration

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

[AJtheManager]

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

My name is Ayomide . I am a frontend developer and smart contract developer, and I would love to contribute to your project.
I’m particularly interested in taking up this issue and I’m confident I can deliver it within 24 hours. I enjoy working on meaningful open-source projects and contributing clean, reliable solutions.
I’d be glad to be considered for this task, and I’m ready to get started immediately.
Thank you for the opportunity.

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

[drips-wave]

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

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

@cashflaretech-glitch Assigned. Welcome to wave 6.

Quick expectations:

1. Branch from develop. PRs target develop (it's the default branch now, so GitHub auto-picks).
2. Open a draft PR within ~3 days so we can see direction.
3. Update at least every 5 days. Silence is the only thing that costs the assignment.
4. Acceptance criteria in the issue body are the merge bar.

If anything is ambiguous, ask on the issue before building.