D3 — Scanner in the wallet
Statement of Work: Deliverable 3 · Target: Week 3 (21–27 Sep) · Status: Planned
The six-stage scanner will run in the wallet's pre-sign review: a block_confirm verdict will hold the Sign button, registry screening will run live per counterparty, and the AI sentence will be served by the Lantern API with no key in the client. This is where the SOW's §6.3 metrics (transactions scanned, wallets that ran a scan) will start to accrue.
Evidence
| SOW §6.1 evidence | Where | What it shows | Status |
|---|---|---|---|
| Installable wallet build (load-unpacked zip or store link) | — | — | Planned |
| Screen recording: connect → pre-sign summary + verdict + screening → one-click report to the registry | — | — | Planned |
| QA sign-off against the manual plan | docs/qa/d3-wallet-integration-test-plan.md |
A thirteen-section plan executable from the installed extension and APK alone: wallet regression, every converted review screen, the three screening states, the high-risk gate (including keyboard-only and TalkBack), the AI fallback, the one-click report, the two-profile re-check drift case, fail-closed cases, the Mainnet carve-out and metrics — with a coverage table mapping each case to the three D3 slices (pipeline in the review, one-click report, re-check before submit) and to the SOW §3.9 risk rows. The results table ships blank for an independent tester | Plan written; not yet executed |
What a user can do when this is done
To be written when the deliverable ships.
Traceability
| SOW clause | Change | Evidence | Status |
|---|---|---|---|
| To be listed from the SOW text | — | — | Planned |
Scope notes
None yet.
Implementation choices
None yet.