From 42ea9d028b000f0b015c5ef91942487112462d4f Mon Sep 17 00:00:00 2001 From: Lukasz Klimek <842586+lklimek@users.noreply.github.com> Date: Fri, 23 Oct 2026 16:24:29 +0000 Subject: [PATCH 1/3] docs(wallet): redesign the Send screen as one From/To form Adds a UX analysis, simplified requirements, a UX spec and ASCII wireframes for Wallet > Send: one form with a From section (wallet and a "Pay from" choice with Auto) and a To section (someone else's address, username or identity, or one of my wallets with Auto), a live Auto status line, one Summary card and Advanced sources inside the form. User stories SND-019..022 are added as gaps. Co-Authored-By: Claude Opus 5.5 --- .../01-requirements.md | 148 +++++++++ .../02-ux-spec.md | 264 ++++++++++++++++ .../03-wireframes.md | 294 ++++++++++++++++++ .../2026-10-23-send-screen-redesign/README.md | 23 ++ docs/user-stories.md | 44 +++ 5 files changed, 773 insertions(+) create mode 100644 docs/ai-design/2026-10-23-send-screen-redesign/01-requirements.md create mode 100644 docs/ai-design/2026-10-23-send-screen-redesign/02-ux-spec.md create mode 100644 docs/ai-design/2026-10-23-send-screen-redesign/03-wireframes.md create mode 100644 docs/ai-design/2026-10-23-send-screen-redesign/README.md diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/01-requirements.md b/docs/ai-design/2026-10-23-send-screen-redesign/01-requirements.md new file mode 100644 index 000000000..84441ee38 --- /dev/null +++ b/docs/ai-design/2026-10-23-send-screen-redesign/01-requirements.md @@ -0,0 +1,148 @@ +# Send Screen Redesign — Requirements + +Status: proposal (not implemented). Screen: Wallet › Send (`src/ui/wallets/send_screen.rs`). + +## 1. Executive summary + +**Problem.** The Send screen asks users to understand Core vs Platform vs +Identity vs Shielded *before* it knows who they are paying. It also runs two +parallel UIs, Simple and "Advanced Options", with different layouts, validation +and fee read-outs. Everyday users (Alex) just want "pay this address this +amount". + +**Direction.** There is one form with two sections, **From** and **To**, and +**Auto** as the default way to pick the source. The app chooses the cheapest +compatible balance and says what it chose, live. Moving money between your own +wallets and accounts is a first-class mode, so you never copy your own address. +"Advanced Options" no longer switches to another screen. It becomes one option +inside each section. + +## 2. Today's screen: inventory and problems + +| Area | Today | +|---|---| +| Wallet | Read-only wallet info grid (no picker; only identity Top up has a `WalletSelector`) | +| Modes | Simple form; "Advanced Options" checkbox (top-right) swaps in a different form; shielded presets (Shield, Send (Private), Unshield); identity-bound modes (Send, Top up, Move to wallet) | +| Sources (Simple) | Radio cards: Core Wallet, Platform Addresses (combined), Identity (if identities exist **or** Expert view; dropdown when >1), Shielded Balance (feature gate + balance > 0) | +| Destination | One `AddressInput`. The accepted kinds depend on the source. It autocompletes wallets and identities and resolves DPNS names | +| Amount | `AmountInput` + Max; caption with fee reserve; minimum amount; "Transaction type: …" hint; a warning when no amount covers the funding fee | +| Extras | "Source breakdown" box listing Platform addresses used; fee summary card | +| Send | Button label changes per route: Send DASH, Fund Platform Address, Top Up Identity, Shield DASH, Transfer Credits, Withdraw to Wallet, … | +| Advanced form | Source type Core or Platform; per-address inputs **with per-address amounts**; output rows (+ Add Output) with type detection; fee strategy (4 options); its own fee summary | +| Gates | The unlock gate hides the whole form until the wallet is unlocked | +| Routes | 14 supported; Identity→Shielded and Shielded→Identity are refused at Send time | + +Problems found (`UX-NNN`, severity per the `severity` skill): + +| ID | Sev | Finding | +|---|---|---| +| UX-001 | High | Changing the source clears the typed destination (`address_input = None`, `validated_destination = None` on every source click). A pasted address is silently lost. | +| UX-002 | High | Users must pick an account kind before the recipient. That kind limits which addresses are accepted, so an address can be "invalid" only because of an unrelated earlier choice. | +| UX-003 | Medium | Two separate forms (Simple and Advanced) with different layouts, validation, fee summaries and button labels. Switching loses state and doubles what users must learn. | +| UX-004 | Medium | Fee information is spread over four places: the amount caption, the "Transaction type" hint, the source-breakdown box and the fee summary. | +| UX-005 | Medium | Paying into your own other wallet or account means finding and copying your own address (or knowing the `wallet:` search tag). | +| UX-006 | Low | The Send button label changes between about 10 verbs as inputs change. It repeats the "Transaction type" hint. | +| UX-007 | Low | The unlock gate hides the whole form. Users cannot see what they are about to do before unlocking. | +| UX-008 | Low | The Identity source card shows in Expert view even when the wallet has no identities, which leaves an empty option. | + +## 3. Actors + +| Actor | Goal on this screen | +|---|---| +| Alex (Everyday) | Pay an address or username fast (< 10 s) without knowing account kinds | +| Priya (Power) | Move funds between own wallets and accounts; occasionally choose which balance or addresses pay | +| Jordan (Developer) | Exercise every route (shielded, identity, multi-output) on testnet | +| Identity hub (entry point) | Opens the form bound to an identity (Send / Top up / Move to wallet) | +| Shielded tab (entry point) | Opens the Shield / Send (Private) / Unshield presets | + +## 4. Requirements + +`[U#]` = traces to the user's numbered requirement. `D-xx` = deviation (§5). + +### Structure +- **SR-01** `[U1]` The form has exactly two sections, **From** and **To**, then Amount, Summary and actions. There is no separate Advanced form (D-01). +- **SR-02** `[U2]` From = wallet picker + **Pay from** options: Auto · Core · Platform · Identity · Shielded · Advanced. +- **SR-03** `[U3]` To = a two-way switch **Someone else | My wallets** (D-02). + - *Someone else*: one address field (address, username or identity ID; type detected automatically). + - *My wallets*: wallet picker (default: the From wallet) + **Receive into** options: Auto · Core · Platform · Identity · Shielded. +- **SR-04** Multiple recipients are not a To option. They appear as "+ Add another recipient" under the Someone-else field (D-03). + +### Auto +- **SR-05** `[U4]` Auto is active on at most one side. Choosing Auto on one side while the other side is Auto pins the other side to the concrete option its Auto had resolved to. **The side the user last touched wins** (D-04). +- **SR-06** `[U5]` Source Auto tries, in order, the first candidate whose spendable maximum (same calculation as Max, SND-017) covers amount + fee: + + | Destination kind | Candidate order | + |---|---| + | Core | Core → Platform | + | Platform | Platform → Core | + | Identity | Platform → Core | + | Shielded | Shielded → Platform → Core | + | not yet known | the largest of Core and Platform (preview only) | + + Auto never spends Identity balances, never spends Shielded funds for a non-private destination, never splits one payment across two sources, and skips a candidate that is the destination account itself (D-05, D-06). +- **SR-07** `[U6]` Next to source Auto, a status line names the chosen balance and how much it holds. It updates live when the destination, amount or balances change, and says why when Auto fell back. +- **SR-08** `[U7]` Destination Auto (My wallets only) receives into an **unused** address of the resolved kind in the chosen wallet. Kind = same as the source kind. If the To wallet equals the From wallet, Auto uses the other kind: Core↔Platform, Shielded→Platform. The address is shown in the status line. +- **SR-09** `[U8]` If the source is Identity, destination Auto = a new Platform address. +- **SR-10** `[U9]` Next to destination Auto, a status line names the wallet, the kind and the short address. +- **SR-11** With *Someone else*, the destination kind comes from the typed value (Core / Platform / Shielded address, identity ID, or username → identity). Source Auto uses it. + +### Defaults +- **SR-12** `[U10]` From = the current wallet + Auto. To = **Someone else** with an empty, focused field (D-07). When the user switches to *My wallets*: the To wallet is the From wallet. The To option is the kind holding the most funds in the From wallet when the wallets differ (literal U10). When they are the same wallet, it is the other kind, so Auto pays from the larger balance and never sends to itself (D-07). + +### Amount, Max, fees +- **SR-13** Max works on the resolved source. With source Auto, Max takes the largest single-source maximum among the candidates for the destination and fixes Auto on that source. Max is an *intent* ("everything in Core"). It stays Max until the amount is edited (compatible with #1106). +- **SR-14** There is one **Summary** card with all fee information: amount, estimated fee, total debited from the named source, and "Recipient gets" when the fee comes out of the amount. Address-level detail is behind "Details" (Expert view). This replaces the amount caption, the "Transaction type" hint and the breakdown box (D-08). +- **SR-15** When no source can cover amount + fee, an inline error under Amount names the largest amount that one payment can send and offers it in one click. + +### Safety and state +- **SR-16** Changing any From option never clears the To value, and the reverse. Incompatible combinations show an inline reason (fixes UX-001). +- **SR-17** The Send button label is always **Send**. The confirmation dialog states route, source, destination, amount, fee and total (D-09). +- **SR-18** A locked wallet does not hide the form. Balances stay visible, and **Send** asks to unlock, then continues to the confirmation (D-10). +- **SR-19** The presets (Shield, Send (Private), Unshield, identity Send / Top up / Move to wallet) open this same form pre-filled. The fields the preset fixes are shown read-only. +- **SR-20** Unsupported routes (Identity→Shielded, Shielded→Identity) cannot be chosen. Their options are disabled with a reason; they are not refused after clicking Send. +- **SR-21** Advanced (source) = "spend only from these addresses": one checklist of Core *or* Platform addresses with balances, plus "Who pays the fee: Sender | Recipient" when Platform is involved (D-11, D-12). Visible in Expert/Developer view only (D-13). + +### Acceptance criteria (key) + +| ID | Given | When | Then | +|---|---|---|---| +| AC-01 | Main: Core 0.8, Platform 0.3; From Auto | Alex pastes a Core address and types 0.5 | The status line reads "Auto: paying from Core · 0.8000 DASH available". Send is enabled. | +| AC-02 | Same wallet as AC-01 | Alex changes the amount to 1.0 | The status line reads "Auto: no single balance in Main covers 1.0000 DASH plus the fee." Amount shows the max-offer link. Send is disabled. | +| AC-03 | Same wallet, amount 0.5 | Alex pastes a Platform address | Platform (0.3) cannot cover the amount, so Auto falls back to Core and the line reads "Auto: paying from Core · Platform can't cover 0.5000 DASH plus the fee." | +| AC-04 | From Auto, To My wallets · Core | The user picks Auto under To | From is pinned to its resolved option (e.g. Platform). An info line reads "Pay from is set to Platform so Receive into can choose automatically." | +| AC-05 | From Identity "alice" | The user picks My wallets · Auto | The To status line reads "Auto: to a new Platform address in Main · tdash1q…9f". | +| AC-06 | The user typed an address, then changes Pay from | — | The address stays. If the new source cannot pay it, an inline reason appears under the address. | +| AC-07 | Locked wallet, valid form | The user presses Send | The unlock dialog opens. After a successful unlock, the confirmation dialog opens. Cancelling the unlock leaves the form unchanged. | +| AC-08 | From Auto, Shielded destination typed, Shielded balance 0 | — | Auto resolves to Platform, then Core. Max follows the shield-quote rules (#1107/#1106). | + +## 5. Deviations from the user's requirements + +| ID | Requirement | Deviation | Rationale | +|---|---|---|---| +| D-01 | U2 "Advanced renders the hidden sources" | Advanced is a source option *inside* the one form, not a separate form | Removes the second UI (UX-003); the state is kept | +| D-02 | U3 "pick a wallet, then options + a manual field" | **Someone else / My wallets** switch; the manual field is its own mode | One active destination at a time. Without the switch, a wallet+option choice and a typed address compete, and nothing shows which one wins | +| D-03 | U3 "same options as source" (incl. Advanced) | No Advanced chip under To; multi-recipient = "+ Add another recipient" under the address field | Several recipients are external payees, so they belong to *Someone else*. A To-side Advanced chip would hide the address field | +| D-04 | U4 states "only one side" | Rule: last-touched wins and the other side is pinned to its resolved value; it is not disabled | A disabled Auto creates "why can't I click this?" moments. Pinning keeps what the user saw and can be undone | +| D-05 | U5 "fall back to Platform" | Full order per destination (SR-06); Core is the final fallback; Identity is never spent automatically; Shielded only for shielded destinations | Identity credits pay for usernames and Platform fees, so spending them silently would surprise users. Unshielding silently breaks privacy | +| D-06 | (gap) | Auto never splits one payment across two sources | A split is two transactions that can partly fail. "No single balance covers this" is honest and fixable with one click (SR-15) | +| D-07 | U10 default destination = current wallet + Core/Platform | Default To = **Someone else**. U10 applies when the user picks *My wallets*; for the same wallet it is adapted to "the other kind" | With U10 as written plus U5, the default is a send to yourself (Core→Core in the same wallet) that pays only a fee, and Send is enabled as soon as an amount is typed. Alex's main task is paying someone (SND-001) | +| D-08 | (gap) | One Summary card replaces four fee/route read-outs | UX-004 | +| D-09 | (gap) | The button always says "Send"; the route verb moves to the summary and confirmation | UX-006. With Auto, a label that changes as you type is unsettling | +| D-10 | (gap) | Unlock when Send is pressed, not up front | UX-007. Matches the sign-time unlock pattern already used elsewhere | +| D-11 | U2 Advanced = today's hidden contents | Per-address amounts are dropped. The user ticks the addresses to spend from; the amount comes from the one Amount field | Per-address amounts are the most error-prone part of the screen. Coin control means "which addresses", not "how much from each" | +| D-12 | (today) 4 fee strategies | 2 choices: Sender pays (= deduct from first input) / Recipient pays (= reduce first output) | "First/last input/output" means nothing to users. The everyday difference is who pays | +| D-13 | U2 lists Advanced for everyone | Advanced and "+ Add another recipient" show only in Expert/Developer view | Progressive disclosure: used by fewer than 20% of users | +| D-14 | U2 labels "Core Wallet", "Platform Addresses", "Shielded Balance" | Short labels **Core**, **Platform**, **Shielded**, **Identity**, plus info tooltips | Match the wallet screen's pills; they fit narrow widths | + +## 6. Dependencies + +- **#1107** — Max for Core / asset-lock / Platform→Shielded comes from upstream quotes, and Core pools all transparent accounts. Source Auto must use those same quotes as its "covers" test (SR-06), so "Core" means the pooled Core balance. +- **#1106** — Core→Shielded Max drains everything, can be resumed, and has "Finish now". SR-13 treats Max as an intent that stays until the amount is edited. The Summary and confirmation say "Moves your whole Core balance" for that route. +- **Unused-address allocation** for destination Auto: Core uses `WalletBackend::next_receive_address`. Platform and Shielded must reuse whatever the Receive dialogs use (WAL-010, WAL-029). It must work for a locked To wallet (xpub only); otherwise, see the 02 spec §9. +- **Auto resolver** = a pure function in `model/` (inputs: candidate maxima, destination kind, amount, same-account flag) so it can be unit tested. The UI only renders it. +- `WalletSendScreen::new_with_wallet()` hard-codes `SourceSelection::CoreWallet`. The new default (Auto) and the presets (SR-19) need a constructor that takes an initial From/To instead. (The DashPay `SendPaymentScreen` has the same Core hard-code. It is out of scope, but should be aligned later.) +- Today the general form shows the wallet read-only; only identity Top up has a `WalletSelector`. A From wallet picker is new and reuses `WalletSelector` (shared label format from user story UX-006, `set_unavailable` for single-key wallets per SND-002). + +## 7. Open questions + +Q1–Q5 with recommendations are in [README.md](README.md#open-questions). diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/02-ux-spec.md b/docs/ai-design/2026-10-23-send-screen-redesign/02-ux-spec.md new file mode 100644 index 000000000..1bc0c7954 --- /dev/null +++ b/docs/ai-design/2026-10-23-send-screen-redesign/02-ux-spec.md @@ -0,0 +1,264 @@ +# Send Screen Redesign — UX Spec + +Requirement IDs (`SR-xx`, `D-xx`) refer to [01-requirements.md](01-requirements.md). Wireframes: [03-wireframes.md](03-wireframes.md). + +## 1. Principles + +1. **Who first, then how.** The recipient decides which routes are possible. The app picks the balance unless the user overrides it. +2. **Auto explains itself.** Every automatic choice comes with a plain sentence saying what it chose and why. +3. **Nothing typed is ever lost.** Changing one section never clears the other (SR-16). +4. **One place for money facts.** The fee, the total and what the recipient gets appear only in the Summary card. +5. **Disable with a reason, never refuse late.** An impossible choice is greyed out with a tooltip; it is not an error after Send. + +## 2. Anatomy (top → bottom) + +``` +Heading "Send Dash" (or the preset heading) +FROM Wallet picker · Pay from options · status line · [option panel] +TO Someone else | My wallets · field or (wallet picker · Receive into options · status line) +AMOUNT AmountInput (DASH) + Max · inline error +SUMMARY You send · Fee · Total from · [Recipient gets] · [Details ▸] +ACTIONS hint line (why Send is disabled) · [Cancel] [Send] +``` + +Option rows are single-select chips (radio semantics). The selected chip shows a fill, a 2 px border **and** a ✓ glyph, so selection does not rely on colour. Each chip shows a short balance (`Core · 0.8123`). The status line sits directly under its chip row. + +## 3. Option catalogue + +### 3.1 Pay from (source) + +| Option | Shown when | Enabled when | Extra control | +|---|---|---|---| +| Auto | always | always | — | +| Core | always | Core spendable > 0 | — | +| Platform | always | Platform balance > 0 | — | +| Identity | the From wallet has ≥ 1 identity | the selected identity has a usable transfer key | identity dropdown if > 1 (default: the app-selected identity if it is in this wallet, else the highest balance) | +| Shielded | shielded feature gate on (protocol v12+, Expert/Developer view) **and** balance > 0 | balance verified (SND-016) | — | +| Advanced | Expert/Developer view | always | §3.3 panel | + +The tooltip on a disabled option says why: "Core has no funds in Main." / "Your private balance is still being checked." / "This identity has no key that can send credits." + +### 3.2 Receive into (destination, *My wallets* only) + +| Option | Shown when | Result | +|---|---|---| +| Auto | always | §4.2 | +| Core | always | the To wallet's next unused Core receive address | +| Platform | always | the To wallet's next unused Platform address | +| Identity | the To wallet has ≥ 1 identity | top up the chosen identity (dropdown) | +| Shielded | shielded gate on | the To wallet's shielded receive address | + +The To wallet picker lists HD wallets on the active network. A single-key wallet can be a destination (Core only, its one address; Auto = Core). + +Disabled (with tooltip): +- The option identical to an explicit source in the same wallet. Tooltip: "You're paying from this balance. Pick a different one, or a different wallet." +- Route-invalid options: Identity→Shielded, Shielded→Identity. Tooltip: "Private funds can't go straight to an identity. Receive into Platform first, then top up the identity." + +### 3.3 Advanced (source) panel + +``` +Spend from (●) Core addresses ( ) Platform addresses +[✓] yXa1…9f 0.5000 DASH +[ ] yQb7…2c 0.3123 DASH +Selected: 0.5000 DASH +Who pays the fee (●) Sender ( ) Recipient ← only when Platform is involved +``` + +- The checklist shows only addresses with a balance. Everything is unticked when first opened. The amount still comes from the single Amount field (D-11). +- Max = everything in the ticked addresses minus the fee. +- Platform: at most `MAX_PLATFORM_INPUTS` ticked. Further boxes are disabled with the tooltip "One payment can use at most {max} Platform addresses." +- The panel replaces the Platform "Source breakdown" box. Without Advanced, the breakdown lives in Summary › Details. + +### 3.4 Several recipients (Expert/Developer view) + +"+ Add another recipient" under the Someone-else field turns it into rows of `[address] [amount] [✕]`, and the single Amount field is hidden. All recipients must be the same kind, either all Core or all Platform (today's backend). A row of a different kind shows: "All recipients in one payment must be the same kind. Send to this address separately." Removing all rows but one returns to the single-recipient layout and keeps that row's amount. + +## 4. Auto resolution + +### 4.1 Source Auto + +Inputs: the destination kind `D` (typed address kind, or the resolved My-wallets option), the amount `A` (or Max), and the per-candidate spendable maximum `max(c, D)`. That maximum is the same value Max would offer for that route, from the #1107 quotes for Core and asset-lock routes, or from the Platform/shield estimators. + +``` +candidates(D): Core → [Core, Platform] + Platform → [Platform, Core] + Identity → [Platform, Core] + Shielded → [Shielded, Platform, Core] + unknown → preview only: the larger of Core and Platform +drop any candidate that is the destination account itself (same wallet + same kind) +drop Shielded if the shielded gate is off or the balance is unverified +pick the first c with max(c, D) ≥ A (A empty → first c with max > 0) +none → "no single balance" state (§8) +``` + +- **Re-resolves** when D changes, when A changes (each valid parse), when balances or quotes change, or when the From wallet changes. +- **Quote pending**: if the candidate being checked has its #1107 quote still loading, the status line reads "Auto: checking balances…". Send stays disabled until the quote arrives. Quotes are requested only for the candidate being checked, never for all candidates. +- **No split**: one payment comes from one source (D-06). +- **Max with Auto**: Max picks the candidate with the largest `max(c, D)` and fixes Auto on it while Max is active. Editing the amount releases the fix. +- An explicit source is never switched automatically, even when it cannot cover the amount (§8 error instead). + +### 4.2 Destination Auto (My wallets) + +``` +kind = source kind (Advanced source → its Core/Platform kind) +if source is Identity → Platform (SR-09) +if To wallet == From wallet: + Core → Platform, Platform → Core, Shielded → Platform +address = next unused receive address of `kind` in the To wallet +``` + +The status line shows "Getting a new address in Savings…" until the address arrives. The address is fetched again only when the To wallet or the kind changes (it stays the same while unused). + +### 4.3 Auto on both sides + +Choosing Auto on side X while side Y is Auto pins Y to the concrete option Y's Auto had resolved to. If Y had no resolution, Y gets its §5 default. A one-time info line appears under Y: "Pay from is set to Platform so Receive into can choose automatically." (or the mirror wording). It disappears on the next change. Auto on Y stays clickable; clicking it flips the pin. + +## 5. Defaults + +| Field | Default | +|---|---| +| From wallet | the wallet the screen was opened from (the app-selected wallet) | +| Pay from | Auto | +| To mode | Someone else, field focused | +| My wallets → To wallet | the From wallet | +| My wallets → Receive into | Different wallet: the kind (Core/Platform) with the most funds in the From wallet (U10). Same wallet: the other kind. Ties go to Core. Auto is never the default here, because Pay from is already Auto | + +## 6. Amount and Max + +- One `AmountInput` in DASH, with Max, a 150 pt minimum width, and the label "Amount". +- **Max is an intent.** The field shows "Max" in the input. A secondary line reads "Everything available in Core · ≈ 0.8121 DASH". Typing any digit returns to an exact amount (#1106 semantics). Core→Shielded Max moves the whole Core balance and is resumable (#1106); the Summary says so. +- Max with no fee coverage: Max is disabled with the tooltip "Core can't cover the network fee right now." (keeps SND-014 / SND-017 behaviour). +- Minimum amounts (asset-lock funding) are inline errors on the field, using today's copy. + +## 7. Summary card + +Shown once there is a destination and an amount (or Max). + +| Row | When | +|---|---| +| Route sentence, e.g. "Pay from Main · Core to yX12…ab" | always (replaces "Transaction type" and the button verb) | +| You send | always | +| Network fee ≈ | the fee is estimable; otherwise "Network fee: calculated when you send" | +| Recipient gets ≈ | the fee is taken from the amount (Core→Platform funding, Recipient pays) | +| Total from Core ≈ | always; names the source | +| Note | route-specific, at most one line (below) | +| Details ▸ | Expert view: the addresses used and the amount from each (today's breakdown) | + +Route notes: +- Platform/Identity → Core: "Withdrawals to a Dash address can take a while to arrive." +- Core → Platform/Identity/Shielded: "Your Dash is moved to Platform first, so this takes a little longer than a regular payment." +- Core → Shielded Max: "Moves your whole Core balance. If the app closes, you can finish it from the Shielded tab." + +## 8. Validation and error copy + +Rule: validate on blur or on a completed paste, never on every keystroke. Errors appear inline under the field they concern, in the `VALIDATION_WARNING` colour with a ⚠ glyph. + +| Situation | Where | Copy | +|---|---|---| +| Unrecognised address | To field | "This isn't a Dash address, username or identity ID. Check it and paste it again." | +| Other network | To field | "This is a Testnet address, but you're on Mainnet. Ask the recipient for a Mainnet address." | +| Username not found | To field | "No one has the username “bob”. Check the spelling." | +| Explicit source can't pay this kind | To field | "You can't send from an identity to a private address. Choose Auto or Platform under Pay from." | +| Own address = source account | To field (warning, not a block) | "This address belongs to Main · Core, the balance you're paying from. You'd only pay a fee." | +| Amount > explicit source max | Amount | "Core can send at most 0.8121 DASH after the fee." + [Use 0.8121] | +| Auto: nothing covers | Amount + status line | "No single balance in Main covers 2.0000 DASH plus the fee. The most one payment can send is 0.8121 DASH, from Core." + [Send 0.8121 instead] | +| Below funding minimum | Amount | today's copy (SND-008 / SND-017) | +| Max quote failed | Amount | today's "The available amount could not be checked." + [Retry available amount check] | +| Recipients of different kinds | recipient row | §3.4 | + +**Disabled Send** always has a hint line above the buttons that names the first missing step: "Enter who you're paying." → "Enter an amount." → "Fix the highlighted field." The button also carries a `disabled_tooltip` with the same text. + +## 9. Locked wallets, sync, network + +- **Locked From wallet**: the form stays usable (D-10) and balances come from the snapshot. Next to the wallet picker, the 🔒 glyph and the line "Locked. You'll be asked for the password when you send." Pressing Send opens `WalletUnlockPopup`. On a successful unlock the confirmation dialog opens. Cancel returns to the form unchanged. *Fallback if snapshot balances are unavailable while locked:* show an inline [Unlock] in the From section only; To stays usable. +- **Locked To wallet** (My wallets): unused-address derivation should need only public keys. If it does not, the status line reads "Unlock Savings to get a receiving address." with an [Unlock] link. +- **Password-protected identity keys** (SEC-001): the existing sign-time prompt; there are no new states. +- **Sync not finished**: the status line adds "Balances are still syncing." Auto still resolves on what is known. Send follows today's rules. +- **Network switch** while open: the form resets to the defaults with the info banner "The network changed, so the send form was cleared." Identity-bound flows keep today's "Back to identity" screen. +- **Single-key wallet as From**: listed but greyed out in the picker with the SND-002 reason. + +## 10. Confirmation and after sending + +`ConfirmationDialog`. Title: "Send 0.5000 DASH?" Body: a two-column grid: + +``` +From Main · Core +To yX12…ab (or "bob (yX12…ab)" / "Savings · new Platform address") +Amount 0.5000 DASH +Fee ≈ 0.0001 DASH +Total ≈ 0.5001 DASH + +``` + +Buttons: [Cancel] [Send] (Confirm on the right; Escape = Cancel). The action is built at the moment Send is pressed, so the dialog shows exactly what will be sent even if Auto would re-resolve later. Danger mode stays as it is today (irreversible send). + +The waiting and success states are unchanged: a spinner with "Sending…", then the success message with [Send another] [Back to wallet]. + +## 11. Entry points and presets (SR-19) + +| Entry | From | To | Fixed (read-only) | +|---|---|---|---| +| Wallet › Send | current wallet · Auto | Someone else | — | +| Shielded › Shield | current wallet · Auto (Core/Platform only) | My wallets · same wallet · Shielded | To | +| Shielded › Send (Private) | Shielded | Someone else (shielded addresses only) | From | +| Shielded › Unshield | Shielded | My wallets · Auto (→ Platform) | From | +| Identity › Send | Identity X | Someone else | From | +| Identity › Top up | wallet picker · Auto (Identity excluded) | My wallets · Identity X | To | +| Identity › Move to wallet | Identity X | My wallets · Core (own addresses only) | From, To mode | + +A fixed section shows its value as text with the label "Set by Shield". It has no chips. + +## 12. Progressive disclosure + +| View | Sees | +|---|---| +| Everyday (Alex) | Auto, Core, Platform, Identity (only if the wallet has identities); Someone else / My wallets; Summary without Details | +| Expert (Priya) | + Advanced, + Add another recipient, + Summary Details, + Shielded (if gate) | +| Developer (Jordan) | same as Expert; amounts may also show credits where the app already does so elsewhere | + +## 13. Responsive layout + +| Width of central panel | Layout | +|---|---| +| ≥ 640 pt | Labels on the left (100 pt column), controls on the right. Chips on one row. Summary as a 2-column grid | +| 420–639 pt | Labels above controls. Chip rows wrap (`horizontal_wrapped`). The Summary stays 2 columns | +| < 420 pt | Chips drop the balance text (shown in their tooltip and the status line). The Summary becomes stacked label/value pairs. Recipient rows stack address over amount. Buttons go full-width, Send on top | + +The form scrolls in the existing `ScrollArea`. The status lines wrap and are never truncated. Addresses are middle-ellipsised (`yX12…9fab`) with the full value in a tooltip and copy-on-click. + +## 14. Accessibility (WCAG 2.2 AA within egui's limits) + +- **Focus order** follows layout: From wallet → Pay from chips → option panel → To mode → To field(s) → Amount → Max → Details → Cancel → Send. Tab and Shift+Tab work; Space/Enter selects a chip. **Enter** in Amount opens the confirmation when valid. +- **Focus visible**: `BORDER_WIDTH_THICK`, 3:1 contrast. Chips meet the minimum target size (24×24 pt, 2.5.8). +- **Not colour alone**: the selected chip has ✓; errors have ⚠ plus text; Locked has 🔒 plus text; Auto status lines always start with the word "Auto:". +- **Status changes**: egui has no live regions. To make up for that, the status line text is complete and self-contained, and the confirmation dialog repeats the resolved route, so nothing is shown only as a change. +- **Tooltips**: `info_tooltip` on chip labels (what Core/Platform/Identity/Shielded mean in one sentence), `disabled_tooltip` on every disabled control, `clickable_tooltip` on copy-able addresses. +- **Dragging** (2.5.7): none needed. **Redundant entry** (3.3.7): values survive section changes (SR-16). +- Tooltip copy for chips: + - Core: "Your regular Dash balance. Works with any Dash address." + - Platform: "Your balance on Dash Platform. Fast and cheap to send to Platform addresses and identities." + - Identity: "Credits held by one of your identities." + - Shielded: "Your private balance. Sending from it to a non-private address reveals the amount." + - Advanced: "Choose exactly which addresses to spend from." + +## 15. Edge cases + +| Case | Behaviour | +|---|---| +| Wallet with only Core funds | Platform chip disabled with "No funds". Auto → Core for any destination it can pay | +| Empty wallet | All funding chips disabled. Auto line: "Auto: Main has no funds to send." Amount is disabled. The hint line reads "Add funds to Main first." with a [Receive] link | +| Only identities hold funds | Auto cannot pay (it never spends identities). Auto line: "Auto: Main's balances are empty. Choose Identity to pay from an identity." | +| Pasted own address of another account | Allowed; Auto skips the same-account candidate | +| User picks an explicit source, then a destination it can't reach | The destination stays; there is an inline reason under the To field; Send is disabled | +| Amount typed before a destination | Auto previews the larger balance and resolves for real once a destination exists | +| Balance changes mid-form (incoming tx) | Auto re-resolves; Max (intent) follows the new maximum | +| Identity dropdown: the app-selected identity is not in the From wallet | Default to the highest-balance identity of that wallet | +| Top up: source wallet holds the target identity | The target is excluded from Pay from › Identity (today's rule) | +| More than `MAX_PLATFORM_INPUTS` Platform addresses needed | Auto treats Platform's max as the top-N sum (today's rule). The Summary note reads "Limited to the {max} largest Platform addresses. Send the rest in another payment." | +| Shielded To kind, shielded gate off | The typed shielded address is refused inline: "Private addresses aren't available in this view. Switch to Expert view to use them." | + +## 16. Implementation notes (non-binding) + +- The Auto resolver and the default-kind rule go in a pure `model/` function, unit tested against the §4 tables. The UI only renders the result. +- Reuse: `WalletSelector` (both wallet pickers), `AddressInput` (Someone else; keep its kind detection, DPNS lookup and `wallet:` search), `AmountInput`, `IdentitySelector`, `ConfirmationDialog`, `WalletUnlockPopup`, `ResponseExt` tooltips. The chip row is the only new widget. If it is reused elsewhere (Shield source toggle), it belongs in `ui/components/` as a generic `ChoiceChips`. +- Delete: the `show_advanced_options` form, `render_advanced_send`, the per-input amount fields, the 4-way `PlatformFeeStrategy` UI (keep the enum and map Sender/Recipient to the `…FirstInput` / `…FirstOutput` variants), the "Transaction type" hint and the verb-per-route button label. diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/03-wireframes.md b/docs/ai-design/2026-10-23-send-screen-redesign/03-wireframes.md new file mode 100644 index 000000000..ea9477b5a --- /dev/null +++ b/docs/ai-design/2026-10-23-send-screen-redesign/03-wireframes.md @@ -0,0 +1,294 @@ +# Send Screen Redesign — Wireframes + +The example data is the same throughout. Wallet **Main**: Core 0.8123, Platform 0.3000, Shielded 0.1000, identity *alice* 0.2000. Wallet **Savings**: Core 2.0000. +Legend: `[✓ X]` selected chip · `[ X ]` chip · `[x X]` disabled chip · `( )`/`(●)` radio · `▾` dropdown · `⚠` error · `ⓘ` info · `🔒` locked. +Rules: [02-ux-spec.md](02-ux-spec.md). + +## W1 — Default (just opened) + +``` +┌─ Send Dash ───────────────────────────────────────────────────────────┐ +│ FROM │ +│ Wallet [ HD: Main — 1.4123 DASH ▾ ] │ +│ Pay from [✓ Auto ] [ Core 0.8123 ] [ Platform 0.3000 ] [ Identity ] │ +│ Auto: picks a balance once you enter who you're paying. │ +│ │ +│ TO │ +│ (● Someone else ) ( My wallets ) │ +│ [ Address, username or identity ID ] │ +│ │ +│ AMOUNT │ +│ [ 0.00 ] DASH [ Max ] │ +│ │ +│ Enter who you're paying. │ +│ [ Cancel ] [x Send ] │ +└───────────────────────────────────────────────────────────────────────┘ +``` +Everyday view. Shielded and Advanced are hidden. Identity is shown because Main has an identity. + +## W2 — Happy path: Auto resolves from the recipient + +``` +│ Pay from [✓ Auto ] [ Core 0.8123 ] [ Platform 0.3000 ] [ Identity ] │ +│ Auto: paying from Core · 0.8123 DASH available │ +│ TO (● Someone else ) ( My wallets ) │ +│ [ yX12pQ…9fab Core ✓ ] │ +│ AMOUNT [ 0.5 ] DASH [ Max ] │ +│ ┌ Summary ───────────────────────────────────────────────────────┐ │ +│ │ Pay from Main · Core to yX12…9fab │ │ +│ │ You send 0.5000 DASH │ │ +│ │ Network fee ≈ 0.0001 DASH │ │ +│ │ Total from Core ≈ 0.5001 DASH │ │ +│ └────────────────────────────────────────────────────────────────┘ │ +│ [ Cancel ] [ Send ] │ +``` + +## W3 — Source options (explicit) + +**Core** +``` +│ Pay from [ Auto ] [✓ Core 0.8123 ] [ Platform 0.3000 ] [ Identity ] │ +``` +**Platform** +``` +│ Pay from [ Auto ] [ Core 0.8123 ] [✓ Platform 0.3000 ] [ Identity ] │ +``` +**Identity** (the dropdown appears only when the wallet has more than one identity) +``` +│ Pay from [ Auto ] [ Core 0.8123 ] [ Platform 0.3000 ] [✓ Identity ] │ +│ Identity [ alice — 0.2000 DASH ▾ ] │ +``` +**Shielded** (Expert view, gate on) +``` +│ Pay from [ Auto ] [ Core ] [ Platform ] [ Identity ] [✓ Shielded 0.1000 ] [ Advanced ] │ +``` +**Disabled examples** +``` +│ Pay from [✓ Auto ] [ Core 0.8123 ] [x Platform 0 ] … │ +│ tooltip: "Platform has no funds in Main." │ +│ [x Shielded 0.1000 ] tooltip: "Your private balance is still being checked." │ +``` + +## W4 — Destination options + +**Someone else, username** +``` +│ TO (● Someone else ) ( My wallets ) │ +│ [ bob ] │ +│ bob · identity 7Hk2…Qp1 ✓ │ +``` +**My wallets: Core / Platform / Identity / Shielded** +``` +│ TO ( Someone else ) (● My wallets ) │ +│ Wallet [ HD: Savings — 2.0000 DASH ▾ ] │ +│ Receive [ Auto ] [✓ Core ] [ Platform ] [ Identity ] [ Shielded ] │ +│ into To a new Core address in Savings · yQb7…2c1d │ +``` +``` +│ Receive [ Auto ] [ Core ] [✓ Platform ] [ Identity ] [ Shielded ] │ +│ into To a new Platform address in Savings · tdash1qx…9f3k │ +``` +``` +│ Receive [ Auto ] [ Core ] [ Platform ] [✓ Identity ] [ Shielded ] │ +│ into Identity [ carol — 0.0500 DASH ▾ ] │ +``` +``` +│ Receive [ Auto ] [ Core ] [ Platform ] [ Identity ] [✓ Shielded ] │ +│ into To your private balance in Savings │ +``` +**Same wallet, explicit source Core**: the identical account is disabled +``` +│ Wallet [ HD: Main — 1.4123 DASH ▾ ] │ +│ Receive [ Auto ] [x Core ] [✓ Platform ] [ Identity ] │ +│ into tooltip: "You're paying from this balance. Pick a different one, or a different wallet." │ +``` + +## W5 — Auto on source: fallback + +``` +│ Pay from [✓ Auto ] [ Core 0.8123 ] [ Platform 0.3000 ] [ Identity ] │ +│ Auto: paying from Core · Platform can't cover 0.5000 DASH plus the fee. │ +│ TO (● Someone else ) ( My wallets ) │ +│ [ tdash1qz8…m4ve Platform ✓ ] │ +│ AMOUNT [ 0.5 ] DASH [ Max ] │ +│ ┌ Summary ───────────────────────────────────────────────────────┐ │ +│ │ Pay from Main · Core to tdash1qz8…m4ve │ │ +│ │ You send 0.5000 DASH │ │ +│ │ Network fee ≈ 0.0002 DASH │ │ +│ │ Recipient gets ≈ 0.4998 DASH │ │ +│ │ Total from Core 0.5000 DASH │ │ +│ │ Your Dash is moved to Platform first, so this takes a little │ │ +│ │ longer than a regular payment. │ │ +│ └────────────────────────────────────────────────────────────────┘ │ +``` +Changing the amount to 0.2 re-resolves live: "Auto: paying from Platform · 0.3000 DASH available". + +## W6 — Auto on destination (pins the source) + +From the defaults, the user picks My wallets, then Auto under Receive into: +``` +│ Pay from [ Auto ] [✓ Core 0.8123 ] [ Platform 0.3000 ] [ Identity ] │ +│ ⓘ Pay from is set to Core so Receive into can choose automatically. │ +│ TO ( Someone else ) (● My wallets ) │ +│ Wallet [ HD: Main — 1.4123 DASH ▾ ] │ +│ Receive [✓ Auto ] [x Core ] [ Platform ] [ Identity ] │ +│ into Auto: to a new Platform address in Main · tdash1qx…9f3k │ +│ (same wallet, so Auto chose the other balance) │ +``` +With the To wallet set to Savings: "Auto: to a new Core address in Savings · yQb7…2c1d". +Clicking Auto under Pay from again pins Receive into to Platform and shows the mirrored ⓘ line. + +## W7 — Identity source, destination Auto (SR-09) + +``` +│ Pay from [ Auto ] [ Core 0.8123 ] [ Platform 0.3000 ] [✓ Identity ] │ +│ Identity [ alice — 0.2000 DASH ▾ ] │ +│ TO ( Someone else ) (● My wallets ) │ +│ Wallet [ HD: Main — 1.4123 DASH ▾ ] │ +│ Receive [✓ Auto ] [ Core ] [ Platform ] [ Identity ] [x Shielded ] │ +│ into Auto: to a new Platform address in Main · tdash1qx…9f3k │ +``` + +## W8 — Advanced (Expert view) + +**Advanced source** +``` +│ Pay from [ Auto ] [ Core ] [ Platform ] [ Identity ] [ Shielded ] [✓ Advanced ] │ +│ ┌──────────────────────────────────────────────────────────────────┐ │ +│ │ Spend from (● Core addresses ) ( Platform addresses ) │ │ +│ │ [✓] yXa1…9f02 0.5000 DASH │ │ +│ │ [ ] yQb7…2c1d 0.3123 DASH │ │ +│ │ Selected: 0.5000 DASH │ │ +│ │ Who pays the fee (● Sender ) ( Recipient ) ← Platform only │ │ +│ └──────────────────────────────────────────────────────────────────┘ │ +``` +**Several recipients** +``` +│ TO (● Someone else ) ( My wallets ) │ +│ [ yX12…9fab ] [ 0.2 ] DASH [✕] │ +│ [ yP44…71aa ] [ 0.1 ] DASH [✕] │ +│ [ tdash1qz8…m4ve ] [ 0.05 ] DASH [✕] │ +│ ⚠ All recipients in one payment must be the same kind. │ +│ Send to this address separately. │ +│ + Add another recipient │ +│ (the single AMOUNT field is hidden; the Summary totals the rows) │ +``` + +## W9 — Max with Auto + +``` +│ Pay from [✓ Auto ] [ Core 0.8123 ] [ Platform 0.3000 ] [ Identity ] │ +│ Auto: paying from Core · Max uses the largest balance. │ +│ TO [ yX12…9fab Core ✓ ] │ +│ AMOUNT [ Max ] DASH [✓ Max ] │ +│ Everything available in Core · ≈ 0.8121 DASH │ +│ ┌ Summary ───────────────────────────────────────────────────────┐ │ +│ │ You send ≈ 0.8121 DASH │ │ +│ │ Network fee ≈ 0.0002 DASH │ │ +│ │ Total from Core 0.8123 DASH (all of it) │ │ +│ └────────────────────────────────────────────────────────────────┘ │ +``` +Core → Shielded Max (#1106) adds the note: "Moves your whole Core balance. If the app closes, you can finish it from the Shielded tab." +While the quote loads (#1107), the field reads "Checking the available amount…" and Max is disabled. + +## W10 — Validation errors + +**No single balance covers the amount (Auto)** +``` +│ Auto: no single balance in Main covers 2.0000 DASH plus the fee. │ +│ AMOUNT [ 2.0 ] DASH [ Max ] │ +│ ⚠ The most one payment can send is 0.8121 DASH, from Core. │ +│ [ Send 0.8121 instead ] │ +│ Fix the highlighted field. [ Cancel ] [x Send ] │ +``` +**Bad address / wrong network** +``` +│ [ XpAbc…zz ] │ +│ ⚠ This is a Mainnet address, but you're on Testnet. │ +│ Ask the recipient for a Testnet address. │ +``` +**Explicit source can't reach this kind** +``` +│ Pay from [ Auto ] [ Core ] [ Platform ] [✓ Identity ] … │ +│ [ dash1z…shield Shielded ] │ +│ ⚠ You can't send from an identity to a private address. │ +│ Choose Auto or Platform under Pay from. │ +``` +**Amount above an explicit source** +``` +│ Pay from [ Auto ] [ Core 0.8123 ] [✓ Platform 0.3000 ] … │ +│ AMOUNT [ 0.5 ] DASH [ Max ] │ +│ ⚠ Platform can send at most 0.2999 DASH after the fee. │ +│ [ Use 0.2999 ] │ +``` + +## W11 — Locked wallet + +``` +│ Wallet [ HD: Main — 1.4123 DASH ▾ ] │ +│ 🔒 Locked. You'll be asked for the password when you send. │ +│ …form fully usable… │ +│ [ Cancel ] [ Send ] │ +``` +Send → `WalletUnlockPopup` → (unlocked) → W12. Cancelling the unlock returns here with nothing changed. + +## W12 — Confirmation + +``` + ┌─ Send 0.5000 DASH? ─────────────────────────────┐ + │ From Main · Core │ + │ To bob (yX12…9fab) │ + │ Amount 0.5000 DASH │ + │ Fee ≈ 0.0001 DASH │ + │ Total ≈ 0.5001 DASH │ + │ │ + │ Check the recipient. Payments can't be undone. │ + │ [ Cancel ] [ Send ] │ + └─────────────────────────────────────────────────┘ +``` +Own-wallet example: "To Savings · new Core address (yQb7…2c1d)". + +## W13 — Narrow (< 420 pt) + +``` +┌─ Send Dash ───────────────────┐ +│ FROM │ +│ Wallet │ +│ [ HD: Main — 1.4123 DASH ▾ ] │ +│ Pay from │ +│ [✓ Auto ] [ Core ] │ +│ [ Platform ] [ Identity ] │ +│ Auto: paying from Core · │ +│ 0.8123 DASH available │ +│ TO │ +│ (● Someone else ) │ +│ ( My wallets ) │ +│ [ yX12…9fab Core ✓ ] │ +│ AMOUNT │ +│ [ 0.5 ] DASH [ Max ] │ +│ Summary │ +│ You send │ +│ 0.5000 DASH │ +│ Network fee │ +│ ≈ 0.0001 DASH │ +│ Total from Core │ +│ ≈ 0.5001 DASH │ +│ [ Send ] │ +│ [ Cancel ] │ +└───────────────────────────────┘ +``` + +## W14 — Preset: Shield (from the Shielded tab) + +``` +┌─ Shield ──────────────────────────────────────────────────────────────┐ +│ Move funds from your wallet or Platform balance into your private │ +│ balance. │ +│ FROM Wallet [ HD: Main — 1.4123 DASH ▾ ] │ +│ Pay from [✓ Auto ] [ Core 0.8123 ] [ Platform 0.3000 ] │ +│ Auto: paying from Platform · 0.3000 DASH available │ +│ TO Your private balance in Main (set by Shield) │ +│ AMOUNT [ 0.2 ] DASH [ Max ] │ +│ …Summary, Send… │ +└───────────────────────────────────────────────────────────────────────┘ +``` diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/README.md b/docs/ai-design/2026-10-23-send-screen-redesign/README.md new file mode 100644 index 000000000..d1fbf1cf4 --- /dev/null +++ b/docs/ai-design/2026-10-23-send-screen-redesign/README.md @@ -0,0 +1,23 @@ +# Send Screen Redesign (2026-10-23) + +This is a proposal for simplifying Wallet › Send. It is design only; no code has changed. + +| File | Contents | +|---|---| +| [01-requirements.md](01-requirements.md) | Inventory of today's screen, UX findings, requirements `SR-xx`, acceptance criteria, deviations `D-xx`, dependencies | +| [02-ux-spec.md](02-ux-spec.md) | Anatomy, option catalogue, Auto resolution rules, defaults, Max, Summary, error copy, locked/network states, presets, disclosure, responsive layout, accessibility, edge cases | +| [03-wireframes.md](03-wireframes.md) | ASCII wireframes W1–W14 | + +User stories: SND-019 … SND-022 in [`docs/user-stories.md`](../../user-stories.md) (`[Gap]`). + +Related open PRs: #1107 (quote-based Max, pooled Core accounts) and #1106 (Core→Shielded Max drain, "Finish now"). + +## Open questions + +| # | Question | Recommendation | +|---|---|---| +| Q1 | Should To open on **Someone else** (empty address field) rather than "current wallet + Core/Platform"? (D-07) | **Yes.** With the literal default plus Auto, the form starts as a send to yourself, and Send is enabled as soon as an amount is typed | +| Q2 | Should Advanced drop per-address amounts and keep only "tick the addresses to spend from"? (D-11) | **Yes.** It is the most error-prone part of today's screen; one Amount field is enough | +| Q3 | Should Auto never spend identity credits, and spend private (shielded) funds only for private destinations? (D-05) | **Yes.** Both would surprise users: identities pay for usernames, and unshielding reveals amounts | +| Q4 | When no single balance covers the amount, should Auto offer the largest single-source amount rather than splitting across Core and Platform? (D-06) | **Yes, no split.** A split is two payments that can partly fail | +| Q5 | Should Advanced and "+ Add another recipient" show only in Expert/Developer view, with the fee choice reduced to Sender / Recipient? (D-12, D-13) | **Yes.** They are used by few people, and "first/last input/output" means nothing to most users | diff --git a/docs/user-stories.md b/docs/user-stories.md index ddeba35f3..8b2ec3cfb 100644 --- a/docs/user-stories.md +++ b/docs/user-stories.md @@ -537,6 +537,50 @@ As a user, I want a payment whose confirmation could not be verified to tell me - Watches do not survive restarting the app or switching networks — the transaction history shows the payment's real status directly in both cases. A payment sent before a network switch is not watched on the network switched to, even when its unverified outcome only arrives afterwards. - While a payment is still unaccounted for, its message outlives other notifications crowding it out: only five show at once, and one pushed off the screen to make room comes back on its own. A message the user closes stays closed — what was lost is restored, what was dismissed is not. +### SND-019: Let the app choose which balance pays [Gap] +**Persona:** Alex, Priya + +As a user, I want the Send screen to pick which of my balances pays for a payment, and tell me what it picked, so that I can pay someone without knowing the difference between Core and Platform. + +- The form has two sections, From and To. From is a wallet plus "Pay from": Auto, Core, Platform, Identity (when the wallet has identities), Shielded (when shielded sending is available) and Advanced (Expert view). Auto is the default. +- Auto pays from the same kind of balance as the recipient (Core address → Core, Platform address → Platform, private address → private balance), then falls back to Platform, then Core. It never spends identity credits, never unshields private funds for a non-private recipient, and never splits one payment across two balances. +- A line under Pay from says what Auto chose and how much that balance holds, and why when it fell back. The line updates as the recipient, amount or balances change. The confirmation repeats the chosen balance. +- When no single balance covers the amount and fee, the form says so and offers the largest amount one payment can send. +- Changing Pay from never clears the recipient. A choice that cannot reach the recipient is disabled or explained inline, never refused after pressing Send. +- Design: `docs/ai-design/2026-10-23-send-screen-redesign/`. + +### SND-020: Move funds between my own wallets and balances [Gap] +**Persona:** Alex, Priya + +As a user, I want to send to one of my own wallets, balances or identities by picking it, so that I never have to copy my own address. + +- To offers "Someone else" (address, username or identity ID) and "My wallets" (a wallet plus "Receive into": Auto, Core, Platform, Identity, Shielded). +- Receive into Core, Platform or Shielded uses an unused receiving address of the chosen wallet, shown on screen. Identity tops up the chosen identity. +- Auto under Receive into uses the same kind of balance as the sender. Within the same wallet it uses the other kind (Core ↔ Platform), and from an identity it always uses a Platform address. A line says where the funds will go. +- Auto can be on only one side. Choosing it on one side fixes the other side to what its Auto had chosen, and says so. +- The balance being paid from cannot also be chosen as the destination. + +### SND-021: One Summary of what a send costs [Gap] +**Persona:** Alex, Priya + +As a user, I want a single summary of the route, fee and total before I press Send, so that I do not have to piece it together from several hints. + +- One Summary card shows: which balance pays and to whom, the amount, the estimated fee, the total taken from the named balance, and what the recipient gets when the fee comes out of the amount. +- Route-specific notes (withdrawals take a while; moving to Platform first) appear at most once, in the Summary. +- The Send button always says "Send". A disabled Send has a line saying the next step needed. +- "Max" means "everything available" and stays that way until the amount is edited. With Auto, Max uses the balance that can send the most. +- A locked wallet does not hide the form; Send asks for the password, then shows the confirmation. + +### SND-022: Choose exactly which addresses pay, or pay several recipients [Gap] +**Persona:** Priya, Jordan + +As a power user, I want to pick the addresses a payment spends from, or pay several recipients at once, from the same Send form, so that I do not have to switch to a separate advanced screen. + +- In Expert or Developer view, Pay from offers Advanced: a checklist of Core or Platform addresses with balances. The amount still comes from the single Amount field. +- When Platform is involved, a "Who pays the fee" choice offers Sender or Recipient. +- "+ Add another recipient" under the recipient field turns it into address-and-amount rows. All recipients in one payment are the same kind. +- Replaces the separate "Advanced Options" form, including its per-address amounts and four fee strategies. + --- ## Asset Locks (ALK) From 6d8fa8f84395a03e64c9f81c5d9ca255c48e4cc0 Mon Sep 17 00:00:00 2001 From: Lukasz Klimek <842586+lklimek@users.noreply.github.com> Date: Fri, 23 Oct 2026 16:32:13 +0000 Subject: [PATCH 2/3] docs(wallet): keep all four fee strategies in the Send redesign Records the user's decisions on the open questions. The four Platform fee strategies stay, with their labels and default, behind a collapsed "Fee options" row in the Summary card shown only in Expert view when an Advanced source or several recipients involve Platform. Co-Authored-By: Claude Opus 5.5 --- .../01-requirements.md | 9 +++--- .../02-ux-spec.md | 28 ++++++++++++++++--- .../03-wireframes.md | 21 +++++++++++++- .../2026-10-23-send-screen-redesign/README.md | 14 +++++----- docs/user-stories.md | 4 +-- 5 files changed, 58 insertions(+), 18 deletions(-) diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/01-requirements.md b/docs/ai-design/2026-10-23-send-screen-redesign/01-requirements.md index 84441ee38..9e18aad8a 100644 --- a/docs/ai-design/2026-10-23-send-screen-redesign/01-requirements.md +++ b/docs/ai-design/2026-10-23-send-screen-redesign/01-requirements.md @@ -100,7 +100,8 @@ Problems found (`UX-NNN`, severity per the `severity` skill): - **SR-18** A locked wallet does not hide the form. Balances stay visible, and **Send** asks to unlock, then continues to the confirmation (D-10). - **SR-19** The presets (Shield, Send (Private), Unshield, identity Send / Top up / Move to wallet) open this same form pre-filled. The fields the preset fixes are shown read-only. - **SR-20** Unsupported routes (Identity→Shielded, Shielded→Identity) cannot be chosen. Their options are disabled with a reason; they are not refused after clicking Send. -- **SR-21** Advanced (source) = "spend only from these addresses": one checklist of Core *or* Platform addresses with balances, plus "Who pays the fee: Sender | Recipient" when Platform is involved (D-11, D-12). Visible in Expert/Developer view only (D-13). +- **SR-21** Advanced (source) = "spend only from these addresses": one checklist of Core *or* Platform addresses with balances (D-11). Visible in Expert/Developer view only (D-13). +- **SR-22** All 4 existing fee strategies are kept. They sit in a collapsed **Fee options ▸** row inside the Summary card. The row is shown only in Expert/Developer view, only while Advanced source or several recipients is active, and only when Platform is involved (today's condition). The default stays "Deduct from first input" (D-12). ### Acceptance criteria (key) @@ -130,7 +131,7 @@ Problems found (`UX-NNN`, severity per the `severity` skill): | D-09 | (gap) | The button always says "Send"; the route verb moves to the summary and confirmation | UX-006. With Auto, a label that changes as you type is unsettling | | D-10 | (gap) | Unlock when Send is pressed, not up front | UX-007. Matches the sign-time unlock pattern already used elsewhere | | D-11 | U2 Advanced = today's hidden contents | Per-address amounts are dropped. The user ticks the addresses to spend from; the amount comes from the one Amount field | Per-address amounts are the most error-prone part of the screen. Coin control means "which addresses", not "how much from each" | -| D-12 | (today) 4 fee strategies | 2 choices: Sender pays (= deduct from first input) / Recipient pays (= reduce first output) | "First/last input/output" means nothing to users. The everyday difference is who pays | +| D-12 | (today) 4 fee strategies in the Advanced form | **All 4 kept**, moved into a collapsed "Fee options ▸" row in the Summary card (Expert view, Advanced/several recipients, Platform involved). The default is unchanged | The Advanced form no longer exists, so the choice needs a new home. Fees belong next to the fee read-out, and collapsing keeps every other view free of it. *User decision: keep all 4.* | | D-13 | U2 lists Advanced for everyone | Advanced and "+ Add another recipient" show only in Expert/Developer view | Progressive disclosure: used by fewer than 20% of users | | D-14 | U2 labels "Core Wallet", "Platform Addresses", "Shielded Balance" | Short labels **Core**, **Platform**, **Shielded**, **Identity**, plus info tooltips | Match the wallet screen's pills; they fit narrow widths | @@ -143,6 +144,6 @@ Problems found (`UX-NNN`, severity per the `severity` skill): - `WalletSendScreen::new_with_wallet()` hard-codes `SourceSelection::CoreWallet`. The new default (Auto) and the presets (SR-19) need a constructor that takes an initial From/To instead. (The DashPay `SendPaymentScreen` has the same Core hard-code. It is out of scope, but should be aligned later.) - Today the general form shows the wallet read-only; only identity Top up has a `WalletSelector`. A From wallet picker is new and reuses `WalletSelector` (shared label format from user story UX-006, `set_unavailable` for single-key wallets per SND-002). -## 7. Open questions +## 7. Decisions -Q1–Q5 with recommendations are in [README.md](README.md#open-questions). +Q1–Q5 are resolved. See [README.md](README.md#decisions-resolved-open-questions). diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/02-ux-spec.md b/docs/ai-design/2026-10-23-send-screen-redesign/02-ux-spec.md index 1bc0c7954..079c33d0c 100644 --- a/docs/ai-design/2026-10-23-send-screen-redesign/02-ux-spec.md +++ b/docs/ai-design/2026-10-23-send-screen-redesign/02-ux-spec.md @@ -61,9 +61,10 @@ Spend from (●) Core addresses ( ) Platform addresses [✓] yXa1…9f 0.5000 DASH [ ] yQb7…2c 0.3123 DASH Selected: 0.5000 DASH -Who pays the fee (●) Sender ( ) Recipient ← only when Platform is involved ``` +The fee strategy is not part of this panel. It lives in Summary › Fee options (§7.1). + - The checklist shows only addresses with a balance. Everything is unticked when first opened. The amount still comes from the single Amount field (D-11). - Max = everything in the ticked addresses minus the fee. - Platform: at most `MAX_PLATFORM_INPUTS` ticked. Further boxes are disabled with the tooltip "One payment can use at most {max} Platform addresses." @@ -139,11 +140,29 @@ Shown once there is a destination and an amount (or Max). | Route sentence, e.g. "Pay from Main · Core to yX12…ab" | always (replaces "Transaction type" and the button verb) | | You send | always | | Network fee ≈ | the fee is estimable; otherwise "Network fee: calculated when you send" | -| Recipient gets ≈ | the fee is taken from the amount (Core→Platform funding, Recipient pays) | +| Recipient gets ≈ | the fee is taken from the amount (Core→Platform funding, or a "Reduce … output" strategy) | | Total from Core ≈ | always; names the source | | Note | route-specific, at most one line (below) | +| Fee options ▸ | §7.1 | | Details ▸ | Expert view: the addresses used and the amount from each (today's breakdown) | +### 7.1 Fee options (SR-22) + +All 4 existing strategies are kept, with today's labels and default. They appear in a collapsed row inside the Summary card. The header shows the current choice, so the row is useful even while collapsed: + +``` +Fee options: Deduct from first input ▸ + (●) Deduct from first input ← default + ( ) Deduct from last input + ( ) Reduce first output + ( ) Reduce last output +``` + +- **Shown when all three hold:** Expert/Developer view, Advanced source or several recipients is active, and Platform is involved (a Platform source or a Platform recipient; today's condition). Otherwise the row is absent: Everyday users never see it, and simple sends keep today's per-route fee behaviour. +- It starts collapsed on every visit. The choice survives collapsing and section changes (SR-16), and resets with the form. +- Choosing a "Reduce … output" strategy adds the "Recipient gets ≈" row and the confirmation sentence "The network fee will be deducted from the output amount, so the recipient will receive less than the entered amount." (today's copy). +- Each option has an `info_tooltip` in plain words, e.g. "Reduce first output: the first recipient receives the amount minus the fee." + Route notes: - Platform/Identity → Core: "Withdrawals to a Dash address can take a while to arrive." - Core → Platform/Identity/Shielded: "Your Dash is moved to Platform first, so this takes a little longer than a regular payment." @@ -213,7 +232,7 @@ A fixed section shows its value as text with the label "Set by Shield". It has n | View | Sees | |---|---| | Everyday (Alex) | Auto, Core, Platform, Identity (only if the wallet has identities); Someone else / My wallets; Summary without Details | -| Expert (Priya) | + Advanced, + Add another recipient, + Summary Details, + Shielded (if gate) | +| Expert (Priya) | + Advanced, + Add another recipient, + Summary Details, + Summary Fee options (§7.1), + Shielded (if gate) | | Developer (Jordan) | same as Expert; amounts may also show credits where the app already does so elsewhere | ## 13. Responsive layout @@ -261,4 +280,5 @@ The form scrolls in the existing `ScrollArea`. The status lines wrap and are nev - The Auto resolver and the default-kind rule go in a pure `model/` function, unit tested against the §4 tables. The UI only renders the result. - Reuse: `WalletSelector` (both wallet pickers), `AddressInput` (Someone else; keep its kind detection, DPNS lookup and `wallet:` search), `AmountInput`, `IdentitySelector`, `ConfirmationDialog`, `WalletUnlockPopup`, `ResponseExt` tooltips. The chip row is the only new widget. If it is reused elsewhere (Shield source toggle), it belongs in `ui/components/` as a generic `ChoiceChips`. -- Delete: the `show_advanced_options` form, `render_advanced_send`, the per-input amount fields, the 4-way `PlatformFeeStrategy` UI (keep the enum and map Sender/Recipient to the `…FirstInput` / `…FirstOutput` variants), the "Transaction type" hint and the verb-per-route button label. +- Keep: `PlatformFeeStrategy` (all 4 variants, same default). Only its combo box moves into Summary › Fee options. +- Delete: the `show_advanced_options` form, `render_advanced_send`, the per-input amount fields, the "Transaction type" hint and the verb-per-route button label. diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/03-wireframes.md b/docs/ai-design/2026-10-23-send-screen-redesign/03-wireframes.md index ea9477b5a..0ac512e1a 100644 --- a/docs/ai-design/2026-10-23-send-screen-redesign/03-wireframes.md +++ b/docs/ai-design/2026-10-23-send-screen-redesign/03-wireframes.md @@ -159,9 +159,28 @@ Clicking Auto under Pay from again pins Receive into to Platform and shows the m │ │ [✓] yXa1…9f02 0.5000 DASH │ │ │ │ [ ] yQb7…2c1d 0.3123 DASH │ │ │ │ Selected: 0.5000 DASH │ │ -│ │ Who pays the fee (● Sender ) ( Recipient ) ← Platform only │ │ │ └──────────────────────────────────────────────────────────────────┘ │ ``` +**Summary with Fee options** (Expert view + Advanced/several recipients + Platform involved; collapsed by default) +``` +│ ┌ Summary ───────────────────────────────────────────────────────┐ │ +│ │ Pay from Main · Platform to tdash1qz8…m4ve │ │ +│ │ You send 0.2000 DASH │ │ +│ │ Network fee ≈ 0.0001 DASH │ │ +│ │ Total from Platform ≈ 0.2001 DASH │ │ +│ │ Fee options: Deduct from first input ▸ │ │ +│ │ Details ▸ │ │ +│ └────────────────────────────────────────────────────────────────┘ │ +``` +Expanded: +``` +│ │ Fee options: Reduce first output ▾ │ │ +│ │ ( ) Deduct from first input │ │ +│ │ ( ) Deduct from last input │ │ +│ │ (●) Reduce first output │ │ +│ │ ( ) Reduce last output │ │ +│ │ Recipient gets ≈ 0.1999 DASH ← added by Reduce │ │ +``` **Several recipients** ``` │ TO (● Someone else ) ( My wallets ) │ diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/README.md b/docs/ai-design/2026-10-23-send-screen-redesign/README.md index d1fbf1cf4..2ac9ce0f8 100644 --- a/docs/ai-design/2026-10-23-send-screen-redesign/README.md +++ b/docs/ai-design/2026-10-23-send-screen-redesign/README.md @@ -12,12 +12,12 @@ User stories: SND-019 … SND-022 in [`docs/user-stories.md`](../../user-stories Related open PRs: #1107 (quote-based Max, pooled Core accounts) and #1106 (Core→Shielded Max drain, "Finish now"). -## Open questions +## Decisions (resolved open questions) -| # | Question | Recommendation | +| # | Question | User decision | |---|---|---| -| Q1 | Should To open on **Someone else** (empty address field) rather than "current wallet + Core/Platform"? (D-07) | **Yes.** With the literal default plus Auto, the form starts as a send to yourself, and Send is enabled as soon as an amount is typed | -| Q2 | Should Advanced drop per-address amounts and keep only "tick the addresses to spend from"? (D-11) | **Yes.** It is the most error-prone part of today's screen; one Amount field is enough | -| Q3 | Should Auto never spend identity credits, and spend private (shielded) funds only for private destinations? (D-05) | **Yes.** Both would surprise users: identities pay for usernames, and unshielding reveals amounts | -| Q4 | When no single balance covers the amount, should Auto offer the largest single-source amount rather than splitting across Core and Platform? (D-06) | **Yes, no split.** A split is two payments that can partly fail | -| Q5 | Should Advanced and "+ Add another recipient" show only in Expert/Developer view, with the fee choice reduced to Sender / Recipient? (D-12, D-13) | **Yes.** They are used by few people, and "first/last input/output" means nothing to most users | +| Q1 | Should To open on **Someone else** rather than "current wallet + Core/Platform"? (D-02, D-07) | **Yes.** Someone else / My wallets switch; the default is Someone else | +| Q2 | Should Advanced drop per-address amounts and use one Amount field? (D-11) | **Yes** | +| Q3 | Should Auto never spend identity credits, and spend shielded funds only for shielded destinations? (D-05) | **Yes** | +| Q4 | Should Auto never split a payment across sources and offer the largest single-source amount instead? (D-06) | **Yes** | +| Q5 | Should Advanced and multiple recipients be Expert/Developer only, and should fee strategies be reduced? (D-12, D-13) | **Expert-only: yes. Fee strategies: keep all 4.** They sit in a collapsed "Fee options ▸" row in the Summary card, with the default unchanged (SR-22) | diff --git a/docs/user-stories.md b/docs/user-stories.md index 8b2ec3cfb..9493252b6 100644 --- a/docs/user-stories.md +++ b/docs/user-stories.md @@ -577,9 +577,9 @@ As a user, I want a single summary of the route, fee and total before I press Se As a power user, I want to pick the addresses a payment spends from, or pay several recipients at once, from the same Send form, so that I do not have to switch to a separate advanced screen. - In Expert or Developer view, Pay from offers Advanced: a checklist of Core or Platform addresses with balances. The amount still comes from the single Amount field. -- When Platform is involved, a "Who pays the fee" choice offers Sender or Recipient. +- When Platform is involved, a collapsed "Fee options" row in the Summary offers the same four fee strategies as today (deduct from first/last input, reduce first/last output), with the same default. - "+ Add another recipient" under the recipient field turns it into address-and-amount rows. All recipients in one payment are the same kind. -- Replaces the separate "Advanced Options" form, including its per-address amounts and four fee strategies. +- Replaces the separate "Advanced Options" form and its per-address amounts. --- From 99aef556b1b700247e4bc2c2598064c60b800e41 Mon Sep 17 00:00:00 2001 From: Lukasz Klimek <842586+lklimek@users.noreply.github.com> Date: Fri, 23 Oct 2026 16:54:07 +0000 Subject: [PATCH 3/3] docs(wallet): add HTML wireframes for the Send redesign MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Renders wireframes W1–W14 as an interactive HTML page in the same visual style as the usernames redesign wireframes, linked from the design README. Co-Authored-By: Claude Opus 5.5 --- .../2026-10-23-send-screen-redesign/README.md | 1 + .../wireframes.html | 987 ++++++++++++++++++ 2 files changed, 988 insertions(+) create mode 100644 docs/ai-design/2026-10-23-send-screen-redesign/wireframes.html diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/README.md b/docs/ai-design/2026-10-23-send-screen-redesign/README.md index 2ac9ce0f8..672b6e86f 100644 --- a/docs/ai-design/2026-10-23-send-screen-redesign/README.md +++ b/docs/ai-design/2026-10-23-send-screen-redesign/README.md @@ -7,6 +7,7 @@ This is a proposal for simplifying Wallet › Send. It is design only; no code h | [01-requirements.md](01-requirements.md) | Inventory of today's screen, UX findings, requirements `SR-xx`, acceptance criteria, deviations `D-xx`, dependencies | | [02-ux-spec.md](02-ux-spec.md) | Anatomy, option catalogue, Auto resolution rules, defaults, Max, Summary, error copy, locked/network states, presets, disclosure, responsive layout, accessibility, edge cases | | [03-wireframes.md](03-wireframes.md) | ASCII wireframes W1–W14 | +| [wireframes.html](wireframes.html) | The same W1–W14 rendered as interactive HTML mock-ups (open in a browser) | User stories: SND-019 … SND-022 in [`docs/user-stories.md`](../../user-stories.md) (`[Gap]`). diff --git a/docs/ai-design/2026-10-23-send-screen-redesign/wireframes.html b/docs/ai-design/2026-10-23-send-screen-redesign/wireframes.html new file mode 100644 index 000000000..f13500c44 --- /dev/null +++ b/docs/ai-design/2026-10-23-send-screen-redesign/wireframes.html @@ -0,0 +1,987 @@ + + + + + +Send Screen Redesign — Wireframes (2026-10-23) + + + + +

Send screen redesign — wireframes

+

Dash Evo Tool, 2026-10-23. HTML rendering of the ASCII frames in 03-wireframes.md; rules in 02-ux-spec.md, requirements in 01-requirements.md. Today's Send screen asks people to understand Core, Platform, Identity and Shielded before it knows who they are paying, and runs two separate forms (Simple and "Advanced Options"). The redesign is one form with two sections, From and To. Auto is the default way to pick the balance: once the recipient is known, the app picks the cheapest balance that can pay and says what it chose in a plain sentence. Paying your own wallets is its own mode (My wallets), so nobody copies their own address. Advanced becomes an Expert-view option inside each section, and every fee fact lives in one Summary card. Same visual system as the 2026-10-01 usernames canvas. Chips, switches, Max, checkboxes, Fee options and Details are live: click, hover (chip tooltips) and Tab through them. Narrow the window below 640 px to see labels move above their controls (spec §13).

+

Example data, the same throughout: wallet Main: Core 0.8123, Platform 0.3000, Shielded 0.1000, identity alice 0.2000 (total 1.4123 DASH). Wallet Savings: Core 2.0000, identity carol 0.0500. Network: Testnet.

+ + + + +
+
Q

Decisions (resolved open questions)

+
+ + + + + + + +
#QuestionUser decision
Q1Should To open on Someone else rather than "current wallet + Core/Platform"? (D-02, D-07)Yes. Someone else / My wallets switch; the default is Someone else.
Q2Should Advanced drop per-address amounts and use one Amount field? (D-11)Yes.
Q3Should Auto never spend identity credits, and spend shielded funds only for shielded destinations? (D-05)Yes.
Q4Should Auto never split a payment across sources and offer the largest single-source amount instead? (D-06)Yes.
Q5Should Advanced and multiple recipients be Expert/Developer only, and should fee strategies be reduced? (D-12, D-13)Expert-only: yes. Fee strategies: keep all 4, in a collapsed "Fee options ▸" row in the Summary card, default unchanged (SR-22).
+
+
+ + +
+
L

Legend

+
+
+
Chip, selected (fill, 2 px border and ✓, not colour alone)
+
Chip, available (hover, Tab for focus)
+
Chip, disabled (always with a tooltip reason)
+
Auto status line (always starts with "Auto:")

Auto: paying from Core · 0.8123 DASH available

+
One-time info line
ⓘPay from is set to Core so Receive into can choose automatically.
+
Inline error (⚠ + text, warning colour)
⚠Fix shown under the field it concerns.
+
Tooltip (shown statically in frames)Platform has no funds in Main.
+
Designer annotation (not UI copy)

explains the frame, not shown to users

+
+
+
+ + +
+
W1

Default (just opened)

Alex · Everyday
+

The form Alex sees from Wallet › Send: who is paying is filled in, the cursor waits in the recipient field, and Auto promises to pick a balance.

+
    +
  • One form, From then To, then Amount and actions; no "Advanced Options" checkbox (SR-01, D-01).
  • +
  • Defaults: From = the current wallet + Auto; To = Someone else with the field focused (SR-12, D-07, Q1).
  • +
  • Everyday view: Shielded and Advanced are hidden; Identity shows because Main has an identity (spec §3.1, D-13). Short chip labels with info tooltips (D-14); hover a chip.
  • +
  • Send is disabled and the hint names the first missing step; the button always says Send (SR-17, D-09, spec §8).
  • +
+
+
Wallets › Main › Send
Testnet · Connected
+
+ +
+
+

Send Dash

+
From
+
+
Pay from
+
+ + + + +
+

Auto: picks a balance once you enter who you're paying.

+
+
To
+
+
+
+
+
Amount
+
+
DASH
+
+
Enter who you're paying.
+
+
+
+
+
+ + +
+
W2

Happy path: Auto resolves from the recipient

Alex · Everyday
+

Alex pastes a Core address and types 0.5. Auto picks Core, says so, and the Summary shows the only money facts on the screen.

+
    +
  • The address kind is detected in the field (Core ✓) and drives Auto (SR-11). For a Core destination Auto tries Core, then Platform (SR-06, AC-01).
  • +
  • The status line names the balance and what it holds, and updates live (SR-07).
  • +
  • Summary appears once there is a destination and an amount. The route sentence replaces the old "Transaction type" hint and the per-route button verb; the total names its source (SR-14, D-08, spec §7).
  • +
+
+
Wallets › Main › Send
Testnet · Connected
+
+ +
+
+

Send Dash

+
From
+
+
Pay from
+
+ + + + +
+

Auto: paying from Core · 0.8123 DASH available

+
+
To
+
+
+
Core ✓
+
+
Amount
+
+
DASH
+
+

Summary

+

Pay from Main · Core to yX12…9fab

+
You send0.5000 DASH
+
Network fee≈ 0.0001 DASH
+
Total from Core≈ 0.5001 DASH
+
+
+
+
+
+
+
+
+ + +
+
W3

Source options (explicit)

AlexPriya · Expert
+

Every Pay from option a person can pick by hand, plus how an unavailable one looks.

+
    +
  • An explicit choice is never switched automatically, even when it can't cover the amount; an inline error explains instead (spec §4.1, W10).
  • +
  • Identity: the dropdown appears only when the wallet has more than one identity (shown here as if it does). Default: the app-selected identity, else the highest balance (spec §3.1).
  • +
  • Shielded needs Expert view, the feature gate and a balance; Advanced is Expert/Developer only (SR-21, D-13).
  • +
  • Disable with a reason, never refuse late (SR-20). Tooltips are drawn as bubbles below; hovering the chips shows the same text.
  • +
+
+

Core

+
Pay from
+ + + +
+
+

Platform

+
Pay from
+ + + +
+
+

Identity

+
Pay from
+ + + +
+
+
+

Shielded Expert view, gate on

+
Pay from
+ + + + + +
+
+

Disabled examples

+
Pay from
+ + + + …
+ Platform:Platform has no funds in Main.
+
+
+ Shielded:Your private balance is still being checked.
+
+
+
+ + +
+
W4

Destination options

AlexPriya · Expert
+

Paying someone else by username, and every Receive into choice when moving money between your own wallets.

+
    +
  • Someone else: one field takes an address, username or identity ID; a username resolves inline to its identity (SR-03, SR-11).
  • +
  • My wallets: To wallet picker plus Receive into. The line under the chips names the wallet, the kind and the short address; Core/Platform use a fresh unused address (SR-08, SR-10, AC-05). No Advanced chip on this side (D-03).
  • +
  • Same wallet with an explicit Core source: the identical account is disabled, with a reason (spec §3.2, SR-20). Shielded appears only with the shielded gate on.
  • +
+
+

Someone else, username

+
To
+
+
+

bob · identity 7Hk2…Qp1 ✓

+
+
+

My wallets · Core

+
To
+
+
Receive into
+ + + + +
+

To a new Core address in Savings · yQb7…2c1d

+
+

My wallets · Platform

+
Receive into
+ + + + +
+

To a new Platform address in Savings · tdash1qx…9f3k

+
+

My wallets · Identity

+
Receive into
+ + + + +
+
+
+

My wallets · Shielded

+
Receive into
+ + + + +
+

To your private balance in Savings

+
+

Same wallet, explicit source Core

+
+
Receive into
+ + + +
+ Core:You're paying from this balance. Pick a different one, or a different wallet.
+
+
+
+ + +
+
W5

Auto on source: fallback

Alex · Everyday
+

A Platform address and 0.5 DASH: Platform (0.3) can't cover it, so Auto falls back to Core and says why.

+
    +
  • For a Platform destination Auto tries Platform, then Core; it never spends Identity and never splits one payment (SR-06, D-05, D-06, AC-03).
  • +
  • The status line says why it fell back (SR-07). Core → Platform takes the fee from the amount, so Recipient gets appears, plus one route note (spec §7).
  • +
+
+
+
Pay from
+
+ + + + +
+

Auto: paying from Core · Platform can't cover 0.5000 DASH plus the fee.

+
+
To
+
+
Platform ✓
+
+
Amount
+
DASH
+
+

Summary

+

Pay from Main · Core to tdash1qz8…m4ve

+
You send0.5000 DASH
+
Network fee≈ 0.0002 DASH
+
Recipient gets≈ 0.4998 DASH
+
Total from Core0.5000 DASH
+
Your Dash is moved to Platform first, so this takes a little longer than a regular payment.
+
+
+
+
+

After changing the amount to 0.2 (re-resolves live)

+

Auto: paying from Platform · 0.3000 DASH available

+
+
+
+ + +
+
W6

Auto on destination pins the source

Priya · Expert
+

From the defaults, Priya picks My wallets, then Auto under Receive into. Only one side can be Auto, so Pay from is pinned to what its Auto had chosen.

+
    +
  • The side touched last wins; the other side is pinned, not disabled, and a one-time info line says so (SR-05, D-04, AC-04, spec §4.3).
  • +
  • Same wallet, so destination Auto uses the other kind and shows the new address (SR-08, SR-10). Core under Receive into is disabled because it is the explicit source.
  • +
+
+
+
Pay from
+
+ + + + +
+
ⓘPay from is set to Core so Receive into can choose automatically.
+
+
To
+
+
Receive into
+
+ + + + +
+

Auto: to a new Platform address in Main · tdash1qx…9f3k

+

same wallet, so Auto chose the other balance

+
+
+
+

Variant: To wallet set to Savings

+

Auto: to a new Core address in Savings · yQb7…2c1d

+
+

Variant: Auto clicked under Pay from again

+
Pay from
+ + +
+
Receive into
+ + +
+
ⓘReceive into is set to Platform so Pay from can choose automatically.
+

mirror wording of the line above (spec §4.3); exact copy to confirm

+
+
+
+
+ + +
+
W7

Identity source, destination Auto

Priya · Expert
+

Moving alice's credits back into the wallet: destination Auto always lands on a new Platform address.

+
    +
  • Source Identity → destination Auto = a new Platform address (SR-09, AC-05).
  • +
  • Identity → Shielded is not a supported route, so Shielded is disabled with a reason instead of failing after Send (SR-20, spec §3.2).
  • +
+
+
Pay from
+ + + +
+
+
To
+
+
Receive into
+
+ + + + + +
+

Auto: to a new Platform address in Main · tdash1qx…9f3k

+ Shielded:Private funds can't go straight to an identity. Receive into Platform first, then top up the identity. +
+
+
+ + +
+
W8

Advanced (Expert view): coin control, Fee options, several recipients

Priya · ExpertJordan · Developer
+

Everything the old "Advanced Options" form did, now as options inside the one form, visible only in Expert and Developer view.

+
    +
  • Advanced source = "spend only from these addresses": one checklist of Core or Platform addresses that hold a balance. No per-address amounts; the amount still comes from the one Amount field (SR-21, D-11, Q2). Everything starts unticked; shown after ticking one. Platform allows at most {max} ticks (spec §3.3).
  • +
  • Fee options keeps all 4 strategies in a collapsed row inside the Summary. The header shows the current choice, so it's useful while collapsed. Shown only in Expert/Developer view, with Advanced source or several recipients, and Platform involved; default "Deduct from first input" (SR-22, D-12, Q5). Choosing a "Reduce … output" strategy adds Recipient gets.
  • +
  • Several recipients live under Someone else, not as a To option; all rows must be the same kind (SR-04, D-03, D-13, spec §3.4).
  • +
+
+

Advanced source

+
Pay from
+
+ + + + + + +
+
+
Spend from +
+ + +

Selected: 0.5000 DASH

+
+
+
+
+

Summary with Fee options, collapsed (default)

+
+

Summary

+

Pay from Main · Platform to tdash1qz8…m4ve

+
You send0.2000 DASH
+
Network fee≈ 0.0001 DASH
+
Total from Platform≈ 0.2001 DASH
+
Fee options: Deduct from first input + + + + +
+
Details

Addresses used and the amount from each (today's "Source breakdown").

+
+
+

Fee options expanded, "Reduce first output" chosen

+
+

Summary

+

Pay from Main · Platform to tdash1qz8…m4ve

+
You send0.2000 DASH
+
Network fee≈ 0.0001 DASH
+
Total from Platform≈ 0.2001 DASH
+
Fee options: Reduce first output + + + + +
+
Recipient gets≈ 0.1999 DASH
+

row added by the "Reduce … output" choice

+
+
+
+

Several recipients

+
To
+
+
DASH
+
DASH
+
DASH
+
⚠All recipients in one payment must be the same kind. Send to this address separately.
+ +

the single Amount field is hidden; the Summary totals the rows

+
+
+
+
+ + +
+
W9

Max with Auto

Alex · Everyday
+

Max means "everything I can send". With Auto, it picks the largest single balance and stays Max until the amount is edited.

+
    +
  • Max is an intent: the field reads "Max", a second line says what it means, typing any digit returns to an exact amount (SR-13, spec §6, #1106).
  • +
  • With Auto, Max fixes Auto on the candidate with the largest maximum while Max is active (spec §4.1).
  • +
+
+
+
Pay from
+
+ + + + +
+

Auto: paying from Core · Max uses the largest balance.

+
+
To
Core ✓
+
Amount
+
DASH
+

Everything available in Core · ≈ 0.8121 DASH

+
+

Summary

+
You send≈ 0.8121 DASH
+
Network fee≈ 0.0002 DASH
+
Total from Core0.8123 DASH (all of it)
+
+
+
+

Core → Shielded Max (#1106): Summary note

+
Moves your whole Core balance. If the app closes, you can finish it from the Shielded tab.
+
+

While the quote loads (#1107)

+
DASH
+
+
+
+ + +
+
W10

Validation errors

Alex · Everyday
+

Each problem appears under the field it concerns, says what to do, and where possible fixes itself in one click.

+
    +
  • Validated on blur or a completed paste, never on every keystroke. ⚠ glyph plus text, never colour alone (spec §8, §14).
  • +
  • Nothing covers: names the largest single-payment amount and offers it (SR-15, D-06, Q4, AC-02). Changing Pay from keeps the typed address and explains under it (SR-16, AC-06). An explicit source is never switched for you.
  • +
+
+

No single balance covers the amount (Auto)

+

Auto: no single balance in Main covers 2.0000 DASH plus the fee.

+
Amount
+
DASH
+
⚠
The most one payment can send is 0.8121 DASH, from Core.
+
+
Fix the highlighted field.
+
+

Bad address / wrong network

+
To
+
+
⚠This is a Mainnet address, but you're on Testnet. Ask the recipient for a Testnet address.
+
+
+

Explicit source can't reach this kind

+
Pay from
+ + + + …
+
To
+
Shielded
+
⚠You can't send from an identity to a private address. Choose Auto or Platform under Pay from.
+
+
+

Amount above an explicit source

+
Pay from
+ + + …
+
Amount
+
DASH
+
⚠
Platform can send at most 0.2999 DASH after the fee.
+
+
+
+
+ + +
+
W11

Locked wallet

Alex · Everyday
+

A locked wallet no longer hides the form. Alex fills it in, sees what will happen, and is asked for the password only when pressing Send.

+
    +
  • Balances come from the snapshot; 🔒 glyph plus text (SR-18, D-10, AC-07, spec §9).
  • +
  • Send → the existing WalletUnlockPopup → on success the confirmation (W12). Cancelling the unlock returns here with nothing changed.
  • +
+
+
+ +

Locked. You'll be asked for the password when you send.

+
+

form fully usable: Pay from, To, Amount and Summary as in W2

+
+
+ Send→Unlock popup (password)→ unlocked →Confirmation (W12) +  ·  Cancel unlock → back here, nothing changed +
+
+
+ + +
+
W12

Confirmation

Alex · Everyday
+

The last look before money moves: the resolved route, in full, in one place.

+
    +
  • The button still says Send; the dialog states source, destination, amount, fee and total, plus the route note if any (SR-17, D-09, spec §10).
  • +
  • The action is built when Send is pressed, so the dialog shows exactly what will be sent even if Auto would re-resolve later. Escape = Cancel; Send on the right.
  • +
+
+
+
Wallets › Main › Send
Testnet · Connected
+ +
+ +
+
+

Own-wallet example: the To row

+
ToSavings · new Core address (yQb7…2c1d)
+
+
+
+ + +
+
W13

Narrow (< 420 pt)

Alex · Everyday
+

The same W2 send on a narrow window: everything stacks, nothing is cut off.

+
    +
  • Labels above controls; chips wrap and drop their balance text (it stays in the chip tooltip and the status line). The Summary becomes stacked label/value pairs. Buttons go full width, Send on top (spec §13).
  • +
  • Status lines wrap and are never truncated; addresses are middle-ellipsised with the full value in a tooltip.
  • +
+
+
+
+

Send Dash

+
From
+
+
Pay from
+
+ + + + +
+

Auto: paying from Core · 0.8123 DASH available

+
+
To
+
+
Core ✓
+
Amount
+
DASH
+
+

Summary

+
You send0.5000 DASH
+
Network fee≈ 0.0001 DASH
+
Total from Core≈ 0.5001 DASH
+
+
+
+
+
+ + +
+
W14

Preset: Shield (from the Shielded tab)

Priya · ExpertJordan · Developer
+

Shield opens this same form with To already set to the private balance; only what Shield doesn't decide stays editable.

+
    +
  • Presets reuse the one form; a fixed section shows its value as text with "Set by Shield" and has no chips (SR-19, spec §11).
  • +
  • Pay from offers Core and Platform only. For a shielded destination Auto tries Shielded → Platform → Core and skips the destination account itself, so here it picks Platform (SR-06).
  • +
+
+
+

Shield

+

Move funds from your wallet or Platform balance into your private balance.

+
From
+
+
Pay from
+
+ + + +
+

Auto: paying from Platform · 0.3000 DASH available

+
+
To
+

Your private balance in Main Set by Shield

+
Amount
+
+
DASH
+
Summary and Send, as in W2
+
+
+
+
+ + +
+
IDs

Referenced IDs

+

One-line digests; the authoritative text is in 01-requirements.md (§4 requirements and acceptance criteria, §5 deviations).

+
+
    +
  • SR-01One form: From, To, then Amount, Summary, actions. No separate Advanced form.
  • +
  • SR-02From = wallet picker + Pay from: Auto · Core · Platform · Identity · Shielded · Advanced.
  • +
  • SR-03To = Someone else | My wallets; My wallets = wallet picker + Receive into.
  • +
  • SR-04Several recipients = "+ Add another recipient" under the Someone-else field.
  • +
  • SR-05Auto on at most one side; the side touched last wins, the other is pinned.
  • +
  • SR-06Source Auto candidate order per destination kind; never Identity, Shielded only for private destinations, no split, skip the destination account.
  • +
  • SR-07Source Auto status line names the balance and amount, updates live, says why on fallback.
  • +
  • SR-08Destination Auto receives into an unused address; same wallet → the other kind.
  • +
  • SR-09Source Identity → destination Auto = a new Platform address.
  • +
  • SR-10Destination Auto status line names wallet, kind and short address.
  • +
  • SR-11Someone else: the destination kind comes from the typed value.
  • +
  • SR-12Defaults: current wallet + Auto; To = Someone else, field focused; My wallets defaults.
  • +
  • SR-13Max works on the resolved source and is an intent until the amount is edited.
  • +
  • SR-14One Summary card holds all fee information; Details in Expert view.
  • +
  • SR-15Nothing covers → inline error offers the largest single-payment amount in one click.
  • +
  • SR-16Changing one section never clears the other; incompatibility shows an inline reason.
  • +
  • SR-17The button always says Send; the confirmation states route, source, destination, amount, fee, total.
  • +
  • SR-18A locked wallet keeps the form; Send asks to unlock, then confirms.
  • +
  • SR-19Presets open the same form pre-filled; fixed fields are read-only.
  • +
  • SR-20Unsupported routes are disabled with a reason, not refused after Send.
  • +
  • SR-21Advanced source = checklist of Core or Platform addresses; Expert/Developer only.
  • +
  • SR-22All 4 fee strategies in a collapsed Fee options row in the Summary (Expert, Advanced/several recipients, Platform involved).
  • +
  • D-01Advanced is an option inside the one form, not a separate form.
  • +
  • D-02Someone else / My wallets switch instead of a wallet choice and a typed address competing.
  • +
  • D-03No Advanced chip under To; several recipients belong to Someone else.
  • +
  • D-04Last-touched side wins; the other is pinned, not disabled.
  • +
  • D-05Full candidate order; Identity never spent automatically; Shielded only for shielded destinations.
  • +
  • D-06Auto never splits one payment across two sources.
  • +
  • D-07Default To = Someone else; U10 applies in My wallets (same wallet → the other kind).
  • +
  • D-08One Summary card replaces four fee/route read-outs.
  • +
  • D-09The button always says "Send"; the route verb moves to the Summary and confirmation.
  • +
  • D-10Unlock when Send is pressed, not up front.
  • +
  • D-11Advanced drops per-address amounts; one Amount field.
  • +
  • D-12All 4 fee strategies kept, moved to Summary › Fee options.
  • +
  • D-13Advanced and "+ Add another recipient" are Expert/Developer only.
  • +
  • D-14Short chip labels (Core, Platform, Identity, Shielded) plus info tooltips.
  • +
  • AC-01Core address + 0.5 → "Auto: paying from Core · … available"; Send enabled.
  • +
  • AC-02Amount 1.0 → "no single balance in Main covers …"; max-offer link; Send disabled.
  • +
  • AC-03Platform address + 0.5 → Auto falls back to Core and says Platform can't cover it.
  • +
  • AC-04Auto picked under To → From pinned to its resolved option, with an info line.
  • +
  • AC-05From Identity alice, To My wallets · Auto → "Auto: to a new Platform address in Main · …".
  • +
  • AC-06Changing Pay from keeps the typed address; an inline reason appears if it can't be paid.
  • +
  • AC-07Locked wallet: Send → unlock → confirmation; cancelling the unlock changes nothing.
  • +
  • AC-08Shielded destination with Shielded balance 0 → Auto resolves to Platform, then Core.
  • +
+
+
+ + +