An urgent device message should be slowed down into a normal Ledger Wallet and device-screen check. The reader does not need broad claims; the reader needs to know what the app says, what the hardware screen says, and what information should stay private.
App context should be read before reacting
Open Ledger Wallet from a known path and read the task context. If the message asks for migration, verification, recovery, or unlocking, compare that wording with the app workflow before taking any next step.
The app versus firmware update guide helps separate interface messages from device-side update or approval steps.
Device-screen wording is the second check
The hardware screen should describe the device action clearly enough for the user to read it. If the app and device screen describe different tasks, pause and record the difference instead of continuing quickly.
- Record the exact message wording.
- Compare app context with device-screen wording.
- Keep recovery phrase and PIN values out of all message flows.
Backup boundaries do not change under pressure
Recovery phrase words remain private backup material. The recovery phrase explainer is the stable reference for what belongs in a backup record and what should never be typed into a prompt.
Finish with a calm decision record
Close with message wording, Ledger Wallet state, device-screen text, backup boundary, and final decision. That turns urgency into a normal review path without making the message the authority.
