Stellar privacy best-practices addendum (Stellar-specific)

[truthixify]

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

Context

Generic privacy guide exists. Stellar has its own quirks: account-existence-leaks, memo metadata, federation DNS leakage, watcher anomalies. Add a Stellar-specific addendum.

Scope

Write docs/guides/stellar-privacy-best-practices.mdx:

• Account-existence leak: trustline operations reveal recipient is an existing account
• Memo metadata: text memos visible on-chain, don't put identifying info
• Federation DNS leakage: resolving name*domain.com queries DNS, traffic-correlation risk
• Stellar.expert + similar explorers index every account; treat stealth addresses as one-shot
• Sponsored withdrawal trail (sponsor address links sender to stealth withdraw)
• Recommendations for each scenario

Acceptance criteria

• Page committed
• Each leak vector explained with example
• Recommendations actionable (not generic)
• Linked from Privacy + SDK Stellar

Files to start with

• New: docs/guides/stellar-privacy-best-practices.mdx
• docs/guides/privacy-best-practices.mdx (existing generic)

[agnesnaomiolim-cloud]

@agnesnaomiolim-cloud 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.

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

[Mubking-dev]

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

please assign me two more issue in this repo

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

[truthixify]

@agnesnaomiolim-cloud Assigned. Welcome to wave 6 (or welcome back).

Quick expectations:

1. Branch from develop (auto-default).
2. Open a draft PR within ~3 days.
3. Update at least every 5 days; silence costs the assignment.
4. Acceptance criteria in the issue body are the merge bar.

Ask on the issue if anything is ambiguous before building.

[drips-wave]

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

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