A message that mentions a device model should be reviewed as a contact-path check. The model detail may make the message feel relevant, but the next step should still come from a known Ledger entry, Ledger Wallet context, and the device screen.
Model detail should be treated as context
Record the model mentioned, contact path, requested action, and visible timing. The detail is useful for describing the situation, but it does not decide whether the user should act from that contact path.
Use the entry verification checklist as a reference for separating contact source, app observation, device observation, and local record.
Known entry should confirm the task
Return to a known Ledger app or support entry and check whether the same task appears there. If the task is not visible from the known entry, keep the message as a record and avoid moving the device workflow forward.
- Record model detail without adding secret backup content.
- Compare the requested task from the known entry.
- Keep recovery phrase and PIN values out of replies and forms.
Ledger Wallet context should align with the screen
If the known entry leads to a Ledger Wallet task, compare the app state with the hardware screen. The Ledger Wallet download guide is a stable reference when the app path needs to be checked again.
End with a local decision, not a contact decision
Close with contact path, model detail, known entry result, app state, device-screen wording, and final decision. That keeps the article focused on a repeatable comparison method rather than on the message's confidence.
