Restore height in CLI workflows
The CLI may ask for restore height during restore. The setting narrows the scan window so the wallet does not need to scan irrelevant early blocks.
Choosing a technical scan start
If you have transaction records, choose a height before the earliest incoming XMR. If you only have a date, estimate earlier. If you have no reliable date, height 0 is the conservative fallback.
Wallet cache and transaction metadata
Rescanning rebuilds wallet history from the chain. Locally stored metadata can be incomplete after restore and may differ from the original wallet file.
Operational safety
- Never paste seed phrases into shell commands copied from strangers.
- Avoid command history exposure on shared machines.
- Use official Monero binaries and documentation.
- Do not send wallet files or keys to support DMs.
Official sources to verify
Use official wallet and project documentation before installing software or changing sensitive wallet settings. External links below are for verification and further reading.
- Official Monero: restore from mnemonic seed
- Official Monero: change wallet restore height
- Cake Wallet docs: Monero
FAQ
What restore height should I use in Monero CLI?
Use a height before the first incoming XMR transaction.
Is height 0 safe?
It is broad but slow; use it when the wallet start date is unknown.
Does CLI restore height change funds?
No. It changes scanning, not ownership.
Reviewed for wallet-safety clarity. This page is an independent educational guide and does not provide financial, legal, privacy, security, or recovery advice.