Monero restore height: how to avoid an incomplete balance

A Monero restore height set too late can miss incoming funds. Choose an earlier scan point and preserve wallet files and cache metadata before rescanning.

Monero restore height: how to avoid an incomplete balance

A restored Monero wallet can show an incomplete balance or history despite having the correct seed if scanning starts after its first incoming transaction. Restore height does not change the keys: it tells the wallet where to begin looking for transactions belonging to them. If you do not know the exact point, starting earlier is safer than starting later, although the first synchronisation must inspect more blocks.

This decision belongs to the Monero wallet you are restoring. Do not convert the seed to another format or paste it into a website to “check” it. Preserve the working installation, the files specified by its client, its notes and an independent offline backup of its recovery material. Do not confuse that backup with seed photographs or cloud copies.

What Monero restore height means

The official Monero restore guide defines restore height as the block from which wallet software starts looking for transactions. Ideally it is the block containing the first incoming transaction to that wallet. A height that is too high excludes earlier blocks and can make a correctly restored wallet look empty or show less money. A lower height only causes unnecessary scanning; the guide says the wallet will still work, although its first synchronisation takes longer.

Restore height is not a universal creation date and it is not something that repairs a seed. It is local scan state. The seed and derived keys remain the same; what changes is how far back the wallet checks before catching up. A known address or a valid seed therefore does not prove that the first scan covered the right block.

How to choose a safe point from your own records

Look for the closest evidence of the first incoming transaction without exposing the seed or keys:

  1. Review the wallet that still works, its backups and private notes about the first receipt.
  2. Check the date of a withdrawal from a service you controlled or your private record of when you began using the wallet. This is a clue, not necessarily the exact block.
  3. If a reliable record contains the first incoming block, use that block or a point somewhat earlier. If you only have an approximate date, choose a conservative date or height before the earliest possible receipt.
  4. Record the date, height and software version used. Do not overwrite the working installation while experimenting.

Do not confuse the new installation's date with the original wallet's creation. The latter can provide a conservative starting point because it precedes the first receipts. A known point after creation but still before the first incoming transaction can also work. The goal is to include the first block that could contain funds, rather than using today's date or the network's current height.

Manual fields and dates carried by a backup

Monero documents GUI and CLI recovery, but field names and prompts can change between releases. The current restore guide describes a height field—and, where that version supports it, a date—when restoring from a seed. Follow the help and screen for the version you actually run and confirm the value before creating the restored copy.

Polyseed shows why not every seed needs a manually chosen height. Its documentation explains that it carries an approximate creation date, which a compatible client can convert into a scan point. That date is not an exact block number. Confirm the format and value proposed by your client; do not automatically apply a legacy-seed procedure or assume all Monero seeds have the same length.

Check which scan start was actually applied. Leaving a field blank may lead to a prompt or a value calculated by the client. It does not by itself prove that the entire chain was examined. Nor should you change words or a seed offset to correct a date: that is a different operation from adjusting the scan.

What happens when the height is too high

The usual symptom is a wallet that opens correctly, derives its keys and synchronises, but cannot find an older incoming transfer or shows a lower balance than expected. The official guide to changing restore height recommends scanning again from a lower height. This corrects synchronisation state; it does not generate new keys.

Changing it can affect local cache data. The guide warns that the GUI may clear recipient addresses, transaction keys and descriptions; it also says the current cache is saved as a backup in the same wallet folder so it can be restored later. Before accepting, preserve an independent copy of the original folder and its metadata. A backup created next to the wallet is not a reason to skip that precaution.

A wider scan means inspecting more blocks. The Moneropedia entry on remote nodes warns about the privacy-control tradeoff of open nodes; lowering the height does not remove it. Do not give seeds or private keys to a supposed fast-synchronisation service.

Wait for synchronisation to finish. The guide says that, if your local node is not yet up to date, you must also wait for that node. A connection or a moving counter is not enough to conclude that the balance is final. Adjusting height does not remove the need for blockchain data: an offline key check and a history scan are different tasks.

What restore height cannot fix

An earlier height cannot replace the correct keys, a required seed offset or the original network and wallet file selection. It does not prove that funds were not spent or that every missing balance is a scan problem. Also review the format, version, selected account and synchronisation. Do not change recovery secrets in an attempt to make a balance appear.

A seed is not a history file. It may derive the keys, while labels, descriptions, transaction keys and other metadata live in local files. Keep the original wallet file and those records separately. Rehearse first with a separate wallet and fictional data. Restoring a copy with its real seed still grants access to its funds; use a trusted environment and preserve the working installation.

Compare a known address of the same type: do not confuse the primary address with a different subaddress. A match helps identify the wallet, but does not prove that the scan covered all its funds and history. Do not erase the original copy merely because the restore accepted the words.

Should I always choose height zero?

Not necessarily. Zero can start from the beginning when the client applies it as the scan height; it can be conservative if you have no known point before your earliest receipts. It means more work than a reliable, later date. Check the effective value and your version's procedure, especially when the format proposes a date automatically. A recent height chosen for another wallet is not a universal reference.

Where SeedAddress fits

SeedAddress does not generate native Monero seeds, adjust restore heights, scan transactions or validate balances. It derives a BIP39 mnemonic in the browser from coordinates, a password, a language and a word count. The method adds no random entropy: a public location is not a secret and choosing 24 words does not guarantee 256 bits of random security. See what a seed phrase is and what SeedAddress does for that method's context.

Never enter a seed, password, offset, private key or funded-wallet data into SeedAddress or an online checker. For Monero recovery, preserve the original format, the original wallet files and an independent backup; choose the height inside the official wallet you are restoring.

Sources