Stellar Asset (USDC) send/receive UX

[truthixify]

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

Context

Demo currently sends XLM only. USDC is the realistic use case. Add asset selector + trustline-aware flows on Send and Receive.

Scope

• Asset selector in StellarSend (XLM + USDC at minimum)
• Trustline detection: warn if recipient lacks trustline (link to fix)
• Use sdk's buildSendStellarAsset (from PR feat(storybook): add Storybook 8 with stories for Stellar components #32)
• Receive: display per-asset balances on stealth addresses
• Withdraw flow supports per-asset

Acceptance criteria

• Asset selector functional on Send
• Trustline detection working
• Per-asset balance display on Receive
• Per-asset withdraw
• Playwright test with USDC testnet

Files to start with

• src/components/StellarSend.tsx, StellarReceive.tsx

[stpatrickghost]

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

Please maintainer... Assign me this issue... I'll resolve it without errors 🙏

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

[DevScoopee]

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

I have reviewed and understood the context and scope I can handle this issue and deliver. Kindly assign

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

[drips-wave]

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

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

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

[truthixify]

@DevScoopee — noticed you closed #79 without a follow-up. Since the PR was scoped differently from issue #65 (USDC send/receive UX) and there's no replacement PR, going to unassign #65 to free it up for re-pickup. No hard feelings — feel free to take a different issue from the available pool if you want to continue contributing.

[Neziahtech]

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

please assign me, i can work on this

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

[Silver36-ship-it]

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

I would love to work on this professionally, please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Silver36-ship-it to this issue.