Offline Device Confirmation | Prepared Request, Screen Prompt, and Local Record
Offline device confirmation is easiest to understand when the prepared request, device screen prompt, and local record are separated. The app or page prepares context; the device screen is where the reader checks the prompt; the local record keeps what was reviewed.
Start with the prepared request
Before an offline moment, the reader needs to know what request was prepared by the app or page. Ledger offline-use FAQ and Ledger online-use FAQ give the surrounding network-use context.
Read the screen prompt as the device step
The device screen should be checked separately from the app view. It is the place where the reader reviews the device-side prompt. Hardware wallet working principles explains why this screen step matters.
Keep the record narrow
- Prepared request or app view.
- Device screen prompt.
- Local note of what was checked.
- Next app or device step.
The local record should not include private backup materials or unnecessary page text.
Close with the boundary
An offline confirmation question should end with a clear boundary: prepare the request, read the device screen, then record the result. Do not merge network state, app view, and device prompt into one conclusion.
