Memo-encoded structured metadata schema

[truthixify]

Extra labels: stellar, feature, interop
Tier: M (2-4 days) | Type: feature

Context. Wraith memos today are opaque bytes. Partners (Reflector, Soroswap) want a structured schema so they can attach reason strings / invoice IDs. Ship a versioned MessagePack (or similar) schema + a decode helper.

Scope.

• Schema v1: { version, kind, data } where kind is a small enum.
• Encoder + decoder in src/chains/stellar/memo/schema.ts.
• Backwards compat: if memo is not schema-shaped, decode returns raw bytes.
• Docs land via a separate docs issue.

Acceptance.

• Schema fits Stellar memo size (32 bytes for MEMO_HASH is tight; consider MEMO_RETURN or off-memo)
• Encode / decode round-trip test
• Doc'd extension mechanism for new kinds

Files. src/chains/stellar/memo/schema.ts (new), test/chains/stellar/memo/schema.test.ts (new).

[lockoabosede8-byte]

@lockoabosede8-byte has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would like to work on this issue because I will get it done well.

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

[drips-wave]

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

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