Download Best Wallet
Download your #1 Monero wallet
Wallet Setup and Recovery

Why does restoring a wallet require a restore height?

Setting a restore height optimizes the recovery process, though it is not always a mandatory requirement.

Quick Answer

A restore height allows the wallet to skip irrelevant history, significantly saving time during the synchronization process. It is not always a mandatory secret or known exact value. If the restore height is unknown, starting at 0 is always safe, though slower. Some wallet schemes automatically encode the approximate birthday. If you choose a height that is too late, the wallet will miss payments until you rescan from an earlier point. Key derivation remains unchanged regardless of the restore height.

Efficiency in Recovery

The restore height is used to skip history that occurred before your wallet existed. By doing this, the wallet saves significant time during the initial scanning and synchronization phase.

While helpful, it is not always mandatory to have an exact value. If you are unsure, using 0 is the default and safest method to ensure no transactions are missed.

Handling Unknown Heights

If you do not know the restore height, some systems use an approximate creation date to estimate it. However, if you start too late, you will miss your transaction history.

If payments do not appear, rescan from an earlier height. The underlying key derivation is never affected by the restore height chosen.

Recovery and backups in Best Wallet

Best Wallet provides documented wallet-creation and seed-restoration workflows, so you can manage recovery from the same desktop interface as your XMR. Match the original seed type, passphrase, and restore height, and back up local wallet files when you need their labels or transaction metadata. Best Wallet cannot reset a lost seed or reverse a payment made by an attacker.

Explore Best Wallet recovery features

Sources

Related reading

Key takeaways

  • Saves time by skipping irrelevant blocks.
  • 0 is always a safe default.
  • Choosing late heights hides transactions.
  • Key derivation is not affected.