Labels: Stellar Wave, stellar, docs, design, drips, help-wanted
Tier: M (2–4 days)
Type: design / docs
Context
The existing SVG diagrams in docs/assets/diagrams/ (stealth-flow.svg, stealth-visual-flow.svg, key-derivation.svg, etc.) are EVM-centric — they show hex addresses, secp256k1 math, and 0x... prefixes. A Stellar-first reader has to mentally translate to StrKey, ledger sequences, and ed25519.
We want a parallel set of Stellar-native diagrams.
Scope
Create the following SVGs and add them to docs/assets/diagrams/stellar/:
stealth-flow-stellar.svg — sender → ECDH → stealth address (StrKey) → announcement (Soroban event) → recipient scan
key-derivation-stellar.svg — signature → SHA-256 + domain separation → spending scalar / viewing scalar → public keys
view-tag-scan-stellar.svg — incoming announcements, view tag filter, ECDH only on matches
name-resolution-stellar.svg — alice.wraith → SHA-256(name) → wraith-names contract lookup → meta-address
fee-bump-withdrawal-stellar.svg — stealth account with no XLM → sponsor's outer tx → inner withdraw → resulting state
Style guide
- Match the existing diagram aesthetic (dark-monochrome, hand-drawn-ish, minimal).
- Use StrKey-shaped addresses (
G... or C... for contracts) in examples.
- Annotate with Stellar-native terms (ledger, contract ID, Soroban event topic).
- Keep file size reasonable (no embedded raster, no megabyte SVGs).
Where to add references
Update the following MDX files to link to the new diagrams:
docs/sdk/chains/stellar.mdx
docs/architecture/overview.mdx (Stellar paragraph)
docs/architecture/stellar-cryptography.mdx (if #03 lands)
docs/guides/stellar-quickstart.mdx (if #01 lands)
Acceptance criteria
Why this matters
Visual learners are a non-trivial slice of every dev audience. Stellar developers especially have grown up with very specific iconography (Horizon, Soroban, Stellar branding) — meeting them there matters.
Labels:
Stellar Wave,stellar,docs,design,drips,help-wantedTier: M (2–4 days)
Type: design / docs
Context
The existing SVG diagrams in
docs/assets/diagrams/(stealth-flow.svg,stealth-visual-flow.svg,key-derivation.svg, etc.) are EVM-centric — they show hex addresses, secp256k1 math, and0x...prefixes. A Stellar-first reader has to mentally translate to StrKey, ledger sequences, and ed25519.We want a parallel set of Stellar-native diagrams.
Scope
Create the following SVGs and add them to
docs/assets/diagrams/stellar/:stealth-flow-stellar.svg— sender → ECDH → stealth address (StrKey) → announcement (Soroban event) → recipient scankey-derivation-stellar.svg— signature → SHA-256 + domain separation → spending scalar / viewing scalar → public keysview-tag-scan-stellar.svg— incoming announcements, view tag filter, ECDH only on matchesname-resolution-stellar.svg—alice.wraith→ SHA-256(name) → wraith-names contract lookup → meta-addressfee-bump-withdrawal-stellar.svg— stealth account with no XLM → sponsor's outer tx → inner withdraw → resulting stateStyle guide
G...orC...for contracts) in examples.Where to add references
Update the following MDX files to link to the new diagrams:
docs/sdk/chains/stellar.mdxdocs/architecture/overview.mdx(Stellar paragraph)docs/architecture/stellar-cryptography.mdx(if #03 lands)docs/guides/stellar-quickstart.mdx(if #01 lands)Acceptance criteria
Why this matters
Visual learners are a non-trivial slice of every dev audience. Stellar developers especially have grown up with very specific iconography (Horizon, Soroban, Stellar branding) — meeting them there matters.