An unofficial update prompt should be handled as an entry-check question. The goal is not to turn every unusual page into a major concern, but to verify whether the prompt belongs to Ledger Wallet, whether the device screen shows the same task, and whether the source path can be recognized from normal use.
Source path comes before prompt wording
Start with where the prompt appeared. If it came from Ledger Wallet after a normal app open, record the app version and device model. If it came from a browser page or message path, return to the known app entry first. The Ledger Wallet download guide is the correct reference for checking the entry before reading the prompt.
Ledger Wallet state and device screen should agree
An update prompt should be understandable in both places: Ledger Wallet gives the workflow context, and the device screen shows the device-side action. If the app state, browser page, and device screen do not align, stop the flow and read the update layer again. Do not enter recovery-phrase or PIN details into a page that is not part of the device-led workflow.
- Record app version, device model, and source path.
- Compare the browser or app prompt with the device screen.
- Return to the app entry before repeating the check.
Use update context without claiming the latest state
This article is a dated product-update note. It can explain a reading method, but it should not claim that a specific prompt is current for every user. If the update wording is confusing, the firmware update workflow gives a clearer sequence for source, screen, and completion checks.
The final action is a short verification record
Finish by writing a compact record: source path, app state, screen wording, and whether the workflow was completed or paused. That record gives the next check a stable starting point. If the same prompt returns, compare it against the record and the known app entry instead of following a new page path.
