Skip to content

Stellar privacy best-practices addendum (Stellar-specific) #45

@truthixify

Description

@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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave programdocsDocumentationdripsFunded via Drips Networkhelp wantedExtra attention is neededprivacyPrivacy-specific work

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions