SEP compatibility matrix reference

[truthixify]

Tier: S (1-2 days) | Type: reference

Context. Stellar ecosystem integrations (custodians, anchors, on-ramps) ask "which SEPs does Wraith support" and there is no page to point at. guides/stellar-federation.mdx covers SEP-2 in isolation. A compact matrix across SEP-1/2/6/10/12/24/31 with the current answer and the location of the relevant guide would close the sales-engineering loop.

Scope.

• New reference/sep-compatibility.mdx.
• Row per SEP with columns: number, name, status (supported / partial / n/a), where the code lives, further reading.
• Include a "what does supported mean" preamble.
• Cross-link the existing stellar-federation.mdx from the SEP-2 row.

Acceptance.

• Every listed SEP status verified against current SDK exports
• Renders in mint dev
• Passes Compile docs snippets CI
• Nav entry under Reference
• guides/stellar-federation.mdx links back

Files. reference/sep-compatibility.mdx (new), guides/stellar-federation.mdx, docs.json.

[franklin251861-killer]

@franklin251861-killer has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hey maintainer I would like to work on this issue, assign it to me .

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

[sanusishafii989]

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

Hi maintainer,

I would like to take on issue #124 to create the SEP compatibility matrix reference documentation.

Technical Implementation Plan:

Verification and Content Creation: Verify SEP support statuses (SEP-1/2/6/10/12/24/31) against current SDK exports and create reference/sep-compatibility.mdx with a clear preamble defining support criteria, status columns, code locations, and reading links.

Cross-Linking: Link the SEP-2 entry directly to guides/stellar-federation.mdx and add a back-link from stellar-federation.mdx to the new reference page.

Navigation and Documentation Config: Register the new reference page entry under the Reference section in docs.json.

Validation: Verify local rendering using mint dev and ensure documentation code snippets pass compilation and CI checks cleanly.

Ready to start immediately upon assignment!

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

[Mathew2k-hash]

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

I'd like to work on this issue because it's a focused documentation task with clear acceptance criteria. I can verify SEP support against the current SDK exports, create a concise compatibility matrix with relevant references, and ensure proper cross-linking, navigation updates, and CI compliance. This page would provide a valuable single source of truth for ecosystem integrations evaluating Wraith.

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

[drips-wave]

Congratulations, @franklin251861-killer! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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