`.wraith` name lifecycle docs (per chain, Stellar-led)

[truthixify]

Labels: Stellar Wave, stellar, docs, drips, help-wanted
Tier: M (2–4 days)
Type: writing

Context

.wraith names exist on all four chains but the docs only mention them in passing. There's no single page that explains: what a name is, how to register, update, release, resolve, what's reserved, what's allowed, what cross-chain semantics look like.

This becomes important as soon as users start collecting names — they need to know what their guarantees are.

Scope

Write docs/guides/wraith-names.mdx covering:

1. What .wraith is — human-readable identifier mapped to a stealth meta-address, per chain.
2. Naming rules — 3–32 characters, lowercase alphanumeric, no hyphens (or document if hyphens are allowed; check source per chain). Reserved patterns if any.
3. Cross-chain namespace — names are per chain. alice.wraith on Stellar ≠ alice.wraith on EVM. Why we chose this. Implications for users (you can register the same handle on every chain; you can lose it on one and keep it on the others).
4. Operations:
   • Register — direct and (where supported) signed-on-behalf
   • Resolve — forward lookup (name → meta-address)
   • Reverse — meta-address → name (where supported)
   • Update — change the meta-address bound to a name you own
   • Release — give up a name
5. Front-running considerations — what's our story on mempool-visible registrations? (Reference: contracts/04 wraith-names audit.)
6. Stellar-specific section — Soroban contract address, code examples for each operation using the SDK, friendbot for funding the registration tx.
7. Comparison table — per-chain quirks, costs, deployment addresses.

Acceptance criteria

• docs/guides/wraith-names.mdx committed.
• Added to docs.json nav.
• Stellar code examples for all five operations verified to run against testnet.
• Per-chain comparison table accurate as of the time of writing.

Why this matters

Identity is sticky. Users will form expectations about their names long before we have a chance to clarify. We need to set those expectations explicitly now.

Files

• New: docs/guides/wraith-names.mdx
• Source-of-truth: contract wraith-names impl per chain, sdk/src/chains/*/names.ts