Release gate: physical-device validation (INCOMPLETE)

User-reported physical-device observations — 2026-11-08
These are owner reports, not independently reproduced release-gate passes.
The owner reports that sending a transaction on a physical phone worked.
The tested app build, connection mode, TXID/confirmation, destination/change
comparison and restore results were not recorded; case 4 remains incomplete.
Do not request or publish recovery phrases, private keys or unredacted backups.

Peer connectivity: the owner observed what appeared to be connections only to
peers in the smartphone user's country, especially on mobile data. A domestic
PC peer connected while overseas peers appeared unavailable. Wi-Fi behaved
differently, and a later observation reached eight connections. Peer geolocation
and independence were not verified. Source review found no intentional country
restriction; this does not rule out an implementation or network-path defect.
The owner suspects carrier restrictions on overseas connections. This is an
unconfirmed hypothesis, not an established carrier policy or diagnosed cause;
NAT64, routing, address selection and peer availability remain alternatives.
Both public VPS nodes were separately observed synchronized and reachable from
each other; this does not prove reachability from the affected mobile network.
Record device/OS/build, network type, timestamps and redacted peer diagnostics
before assigning a cause. No further PC shutdown test is required here.

Prerequisites
A dedicated Resatoshi Core + reviewed Electrum backend on a reachable server,
correct mainnet genesis, trusted TLS hostname certificate, explicit operator/
privacy/log policy, two Android devices, small disposable test funds, paper backup.
The local loopback backend lab is not a public deployment recipe. No real keys
or phone backup data should be sent to the developer or committed to Git.

Record model, Android/build version, app version, backend/Core revisions, case,
expected/actual result and redacted evidence. Use at least one API24–29 device
and one API30+ device where available. The formal cases below remain NOT RUN unless explicitly supported by evidence.

1 Create with SecureRandom; record phrase/path, compare first receive address.
2 PIN-only and biometric+PIN devices: create/unlock/send; record prompt count,
  cancel, failed auth, timeout, background/foreground and repeated operation.
3 Receive small test payment: capture sender broadcast/server arrival/UI receipt
  timestamps separately; check pending amount, confirmed transition and warning.
4 Send to independent wallet: compare raw tx destination/fee/change with Core;
  wait for confirmation, then spend the change and check balances on both sides.
5 Restore on a disposable installation from phrase and exact passphrase; compare
  receive/change balances and first address. Verify wrong passphrase opens a
  different wallet rather than an error. Test blank/nonblank passphrase cases.
6 Export/import encrypted backup via Android file picker; wrong password,
  interrupted write and old-backup/new-password behavior. Preserve a working
  original until the restored wallet and funds are independently verified.
7 Two phones: watch pairing first-address check, multipart QR, unsigned request,
  offline review/sign, signed response, online broadcast, replay/wrong wallet/
  wrong QR handling and background invalidation. Keep signer radio-disconnected.
8 Wi-Fi/mobile-network loss, reconnect, stale results, server restart and phone
  lock: no duplicate credits, no false success, no leaked secret screens/logs.
9 Update existing preview without uninstalling: credentials/funds remain intact.
10 Privacy/license screens readable on narrow display and larger font settings.

11 Discovery: first full scan, app restart then quick refresh, manual Full recovery
   scan in hot/watch-only screens, missing/corrupt cache and failed cache save.
   Compare balances with Core, repeat deposits to an older address, and create
   distant change on the other device: manual full scan must find it. Measure
   phone/network timings independently of the local lab.

A developer cannot mark these passed without actual device evidence. VPS/phone
access remains the dependency for completing this gate; do not substitute mocks.
