Stellar Asset memo extraction helpers

[truthixify]

Tier: S (½-1 day) Type: feature

Context

good-first-issue

Scope

Stellar transactions often carry memos that integrators want to surface ("invoice 1234", "refund", etc). Today consumers parse this themselves.

Acceptance criteria

• extractMemo(transaction) returning { type, value } or null
• Handles all memo types (text, id, hash, return)
• Used by fetchAnnouncements to attach memo to each Announcement (optional)
• Documented in Stellar chain module README

Files to start with

• Helper + tests
• Optional memo attached to Announcement type
• Documentation

Why this matters

• sdk/src/chains/stellar/utils.ts

[praizeD10]

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

I would like to work on this issue because reliable memo extraction utilities are essential for simplifying asset-related workflows and improving the developer experience when working with Stellar transactions. Providing well-structured helpers for extracting and handling memos would reduce duplication and make the codebase easier to maintain.

I have experience working with TypeScript and backend systems, building utility modules, and implementing type-safe abstractions. I am comfortable navigating existing codebases, writing clean and maintainable code, and adding tests to ensure correctness. I also have experience working with blockchain-related applications and understand the importance of robust transaction parsing and data handling. I would be happy to contribute a solution that integrates cleanly with the existing Stellar asset utilities and includes appropriate test coverage.

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

[truthixify]

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

[drips-wave]

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

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