Genuine Check is easiest to understand when it is placed inside an arrival timeline. Before the check, the user records packaging and device state. During the check, the user compares Ledger Wallet prompts with what the device screen shows. After the check, the user keeps a simple completion note. The point is not to turn one prompt into a dramatic conclusion, but to match observable states in order.
Before Genuine Check, record the arrival state
Before opening a setup path, write down the package condition, accessory set, device model, and first screen state. Keep this note factual and short. If the article is being used during unboxing, What Ledger Authenticity Checking Really Is is a useful companion because it separates package, device, app, and record dimensions.
During Genuine Check, compare app prompt and screen
Open Ledger Wallet from the fixed entry and watch both the app prompt and the device screen. The app can guide recognition, while the screen confirms what the device is asking the user to do. If the app entry itself needs review, use Ledger Wallet Download and Installation Guide before continuing the device check.
After Genuine Check, keep the completion note narrow
A good completion note contains the date, app entry, device model, screen state, and result wording. It does not contain PIN details, recovery phrase words, or private backup notes. If setup is the next task, move into What Is Ledger Initialization so Genuine Check and first setup are not mixed into one unclear action.
When states do not match, pause and repeat the same order
If package state, app prompt, or device screen cannot be matched, pause and repeat the same sequence from the fixed entry. Do not add new steps just to force a conclusion. A stable review path protects the record: arrival state first, Genuine Check prompt second, setup path third, and local completion note last.
