post-v1: Seedelf vault UX pass

[logicalmechanism]

Summary

The Vault's SeedelfPanel shipped functional in #155 — buttons that wire mintSeedelfTx / sendToSeedelfTx / spendFromSeedelfTx, plus a 32-byte-hex register-id render. This issue captures the UX pass that takes it from "works" to "comfortable to use day-to-day".

Scope

Receive flow

• Per-register share-friendly id: the bare 32-byte hex is a poor UX; render it as a copy-able blob with a QR code modal and an optional "human-name" annotation the user types locally (kept in IndexedDB, not on chain).
• A dedicated "Receive" sub-panel showing each register's id, a paste-into-this-wallet helper for the sender's UX (mirrors how exchanges show deposit addresses), and an optional "expected amount" the panel watches for.

Send flow

• Address book: locally-stored contacts mapping a friendly name → seedelf id. Tag-based (so a contact can carry both a Lovejoin address and a Seedelf id under one entry).
• Recent recipients: implicit "last N sent-to" suggestions sorted by recency.
• Amount QoL: max-out button (account for fee headroom), reject below min-UTxO with a clear hint.

Spend flow

• Internal rotate by default: today the spend form starts on "external" because that's the simpler path, but the more privacy-preserving default is "internal" (rotate the dust into a fresh register). Switch the default and explain the tradeoff inline.
• Spend to Lovejoin mix-box: a one-click affordance that bundles a Seedelf spend with a fresh Lovejoin deposit — washes stealth ADA back through the mixer without the user having to chain two txs by hand.
• Per-register history: a collapsed timeline of tx ids that produced / consumed this register's funds. Read-only, sourced from the indexer (today the user has to dig through cardanoscan).

Onboarding

• An "intensity dial"-style staircase for first-time users: explain stealth wallets, walk through minting, and gate the spend forms behind a one-time consent so users don't burn ADA on a misclick.
• Empty-state copy that links to the docs page (separate Help/Protocol page item).

Withdraw bridge

• The Withdraw page should optionally deliver to a Seedelf register (covered by a separate feat-ticket; see #linked). The presentation half — destination-mode radios, Seedelf-id picker, dynamic min-UTxO hints — belongs here so the two flows feel like one product.

Polish

• The mint button hard-fails when the wallet has fewer than 2-ish ADA spare; should surface a clear "needs ~2 ADA for the new register's min-UTxO" hint up-front.
• Toast copy is generic; tx-specific toasts ("Minted register M2: validators + Preprod bootstrap (calibration deferred to M4) #3", "Sent 5 ADA to alice's stealth wallet") read better.
• RTL audit for ar / fa / ur — the new forms should mirror correctly.
• Accessibility: the per-register row's button cluster needs better keyboard nav + screen-reader labels.

Non-goals

• Standalone Seedelf wallet UI outside the Lovejoin Vault (Seedelf-CLI exists for that).
• Multi-wallet / multi-identity Seedelf within one Lovejoin vault (one wallet-signed seed = one Seedelf identity, see feat(ui+sdk): integrate Seedelf as a stealth wallet inside Lovejoin #135 derivation).
• A custodial / hosted Seedelf service.

Order of attack

1. Receive flow (QR + human-name annotations) — biggest perceived UX win.
2. Address book — once Receive lands, contacts compose naturally.
3. Withdraw→Seedelf integration UI (after the linked SDK feat-ticket is merged).
4. Spend defaults + Spend-to-mix-box.
5. Onboarding staircase.
6. Polish (a11y, RTL, toast copy).

Related

• Built on top of feat(ui+sdk): ship Seedelf mint / send / spend transactional flows #155 (mint / send / spend SDK + minimal UI).
• The Withdraw bridge needs the SDK feat-ticket filed alongside this one.

[logicalmechanism]

Update — registers vs funds distinction (carried over from a pre-merge fix on #157):

PR #157's first cut put a Spend button on each register row, which conflated registers (the user's addresses — a locator NFT + ~2 ADA min-UTxO that exists so senders can pay you) with funds (the user's balance — re-randomized payment UTxOs without a locator NFT). Registers shouldn't be spendable as currency from the UI; their only spend operation is "burn the locator" (planned in #156).

That conflation got fixed on the same branch: Spend is now off the register row, and a new "Funds" section lists owned fund UTxOs each with its own Spend form. The UX-pass scope above should:

• Pin the registers-as-addresses / funds-as-balance vocabulary in onboarding copy.
• Add a small read-only summary card per register (received total, last activity) so users see why a register is useful even though they can't spend it directly.
• Wire the "Burn register" button from post-v1: Seedelf burn-register flow #156 alongside Copy id once post-v1: Seedelf burn-register flow #156 lands.

[logicalmechanism]

Adding one more item to scope, surfaced in conversation: clarify registers-as-addresses vs funds-as-balance in onboarding copy + visual treatment.

Background: the original SeedelfPanel attached a Spend button to register rows, which mixed metaphors — a register is the address (locator NFT + min-UTxO) you share with senders, while a fund is the balance (payments received, no locator NFT) you actually spend from. The PR #157 follow-up split the panel into two sections to drop the footgun, but the conceptual gap is still a learning curve for first-time users.

The UX pass should:

• Visually distinguish the two sections beyond a heading (icon / color / layout).
• Onboarding tooltip on first mount explaining the model with one example: "Register = a private 'addr_test1...' you share. Fund = ADA someone sent there, now spendable."
• Hint copy on the Mint button explaining what a register costs (~2 ADA min-UTxO that comes back if you burn it).
• When the user has registers but no funds, surface a "No payments received yet — share a register's seedelf id to receive ADA" hint rather than the bare empty state.
• Burn-register affordance on register rows (waits on post-v1: Seedelf burn-register flow #156).