A user downloads Cake Wallet, restores a Monero wallet from a 25-word seed phrase they saved six months ago, and watches the balance display zero even after the synchronization appears complete. The wallet shows the correct address and transaction history loads, but no funds appear. This is not a lost recovery phrase or a compromised wallet. The issue is a restore height mismatch—the wallet was told to start scanning the blockchain at a point in time after the funds actually arrived. The scanner never sees the transactions because it is looking in the wrong place on the ledger.
Restore height errors are among the most common sources of confusion for users recovering Monero wallets. The mechanism is straightforward once understood, but it catches even experienced users because it looks like a balance loss rather than a scanning starting point problem. When a user restores from a seed phrase, the wallet does not download the entire transaction history from the beginning of the Monero network. Instead, it asks the user to specify a block height—a point on the blockchain—and scans forward from there. If that starting point is too recent, and the funds were received before it, the wallet will sync completely and still show zero balance because it never examined the blocks containing the original transactions.

How restore height works and why it matters for sync troubleshooting
The restore height is not an arbitrary choice. It is a practical optimization. The Monero Project’s design requires scanning transactions to determine which ones belong to a specific private key. On a mobile device with limited bandwidth and storage, downloading and examining every block since the network’s genesis would be wasteful. Instead, a user provides a hint: the approximate block where this wallet first received funds. The wallet then scans from that point forward, verifying which blocks contain outputs matching the wallet’s public address and spending keys.
The reason this creates a false zero-balance problem is that the hint is easy to guess wrong. If a user says “start scanning at block 2,800,000” but the funds actually arrived at block 2,700,000, the wallet will never see the deposit. It will scan every block from 2,800,000 to the current height, find no matching transactions, and report a zero balance. The funds are not lost. They exist on the immutable ledger. The wallet simply never looked at the blocks containing them because it was told to start further down the chain.
A Monero wallet’s restore height is typically entered as a block number or, more conveniently, as a calendar date that the wallet converts to an approximate block number. Most users restoring from a seed will not remember the exact block where they last used the wallet. Instead, they enter the approximate date they believe they last received funds. If they are wrong by more than a few weeks, the mismatch becomes a scanning problem. The wallet syncs normally—it asks the Monero node for blocks, verifies them, and searches for matching outputs—but it appears frozen in time before the actual transaction date.
When you perform a cake wallet download and restore an existing Monero wallet, you will encounter a restore height option early in the setup process. This is the moment where precision matters most, yet precision is hardest to achieve. Many users either enter a date from memory that is too recent, or they skip the restore height entirely and let the wallet default to the current block height. Both choices can produce hours of apparent inactivity followed by a zero-balance panic.
Diagnosing zero balance: Is it restore height or something else?
The first diagnostic step is to confirm that you are actually synced. “Synced” means the wallet has downloaded and verified all blocks up to the current network tip and has scanned them for your transactions. In Cake Wallet, you can check the sync status in the settings or wallet details panel. If the wallet shows a block height that is weeks or months behind the current Monero network height, it is still downloading. This is not a zero-balance error; it is a waiting game. Monero’s network height advances roughly every two minutes, so a wallet that is significantly behind will take time to catch up.
Once you confirm the wallet is fully synced—the displayed block height matches the network height—you can verify the address. Open the receive section and confirm that the address displayed in Cake Wallet matches the address where you believe you sent funds. For Monero, this is the primary receiving address derived from your private key. If the address is different, you may have imported the wrong seed phrase or restored to a different wallet entirely. Copy the address and check it against any transaction records you kept, email confirmations, or exchange withdrawal histories.
If the address is correct and the wallet is fully synced but shows zero balance, the restore height is almost certainly the problem. The wallet is functioning normally; it is just looking at the wrong section of the blockchain. Test this hypothesis by temporarily lowering the restore height—move it backward by weeks or months—and trigger a rescan. In Cake Wallet, you can often adjust the restore height in the wallet settings and force the wallet to rescan from an earlier point. Watch the balance change. If funds suddenly appear after you lower the restore height, you have confirmed the diagnosis.
A second diagnostic is to check the transaction history view. If the wallet shows incoming transactions with dates and amounts, but the balance is zero, something is wrong with the output verification rather than the height scanning. This is rare but can happen if the wallet’s private view key is corrupted or if there is a mismatch between the seed and the wallet file. In this case, restoring from the seed phrase again—or verifying the seed phrase itself—becomes necessary.
Finding the correct restore height: Methods and tools
The most reliable method to find the correct restore height is to identify the date you first created or last used the wallet. If you have an email confirmation from an exchange where you withdrew Monero to this address, use that date. If you know approximately when you last checked the balance or received funds, that is your starting point. You want to be conservative: if you think it was March 2024, pick February 2024 instead. A restore height that is too early will take longer to scan but will not miss transactions.
Cake Wallet includes a date-to-block converter that approximates which block number corresponds to a given date. When you select a date during restore setup, the app converts it automatically. This is a convenience, but it is still approximate. The conversion assumes an average block time and does not account for network hashrate fluctuations. If the estimate puts the restore height a few days off, it is not a failure; it just means you might scan a few extra blocks or need to go back further if transactions are still missing.
A secondary resource is to check the Monero Project documentation for historical block information. Monero block explorers can also help. If you know the transaction ID (hash) of a payment you received, you can look it up on a block explorer and note the exact block height. Then subtract a few thousand blocks as a safety margin—this ensures you start scanning well before the transaction, accounting for any timestamp confusion.
If you have no record of transaction dates or amounts, a cautious approach is to set the restore height to several months before your best guess, then let the wallet scan. Yes, this will take longer. But it guarantees you will not miss funds due to an overly recent starting point. Once the wallet is fully synced and the balance appears, you have confirmed the correct restore height.
The restore height reset and rescan process
Most users encountering a zero-balance problem do not need to delete the wallet or create a new one. Instead, they need to perform a rescan from a lower restore height. In Cake Wallet, this is typically accessed through the wallet settings. Look for an option labeled “Restore Height,” “Rescan,” or similar. When you adjust the restore height to an earlier block, the wallet will usually offer to rescan automatically or prompt you to do so manually.
During a rescan, the wallet re-examines blocks starting from the new restore height. On a mobile device connected to a Monero node (either your own or a public node), this can take minutes to hours depending on how far back you go and how busy the node is. The wallet will display progress as it scans. Do not force-quit the application during this process. Let it run to completion, even if there are no visible updates on screen.
If Cake Wallet is connected to a node operated by Cake Labs or a third party, the rescan speed depends on the node’s responsiveness. If you have control over your restore height and still see zero balance after a full rescan from a much earlier date, the problem may be with the node connection or with the seed phrase itself. Try connecting to a different node—Cake Wallet allows you to configure custom nodes or switch between public node pools—and rescan again.
For users with critical balances or repeated sync issues, running a personal Monero node eliminates reliance on third-party nodes and gives you direct control over block scanning. This is more complex to set up but provides the most reliable restore experience. If you are restoring a large balance or high-value holdings, the effort may be justified.
Seed phrase validity and the import process
A secondary cause of zero-balance errors is an invalid or incorrectly entered seed phrase. Cake Wallet supports multiple seed types: 25-word Monero seeds (in the Monero seed format), 24-word Polyseed for Monero (a newer format), and standard BIP39 seeds for Bitcoin, Litecoin, and Ethereum. If you are restoring a Monero wallet, the seed phrase must be in one of the Monero formats. If you accidentally enter a Bitcoin seed into the Monero wallet restore, the wallet will derive a different address and show zero balance because it is looking for funds sent to an entirely different key.
When you restore, Cake Wallet will validate the seed phrase syntax—it will confirm that the words are real and that the checksum is correct. However, it will not confirm that you have the right seed for the right coin type. The validation is cryptographic, not semantic. A valid Monero seed will always produce a wallet; the question is whether it produces the correct wallet. If you are unsure which seed type you have, test by entering it and checking the resulting address against a record you kept. If the address does not match, you have the wrong seed or seed type.
A third possibility is a typo in the seed phrase. A single wrong word will produce a completely different wallet with a different address and zero balance. Monero seeds use a wordlist, and if you misremember a word, the wallet will either reject it as invalid or accept it and derive a wrong address. When re-entering a seed from memory or from a written backup, double-check every word. If you have the seed written down, copy it carefully. If you are typing from memory, consider whether you might have mixed up similar words or misremembered the order.
Preventing restore height problems: Best practices for backup and recovery
The strongest defense against restore height confusion is to record the date you created the wallet in addition to the seed phrase itself. Write down the date your wallet was created or the date you last confirmed a balance. This single piece of information, stored with your seed phrase backup, makes the restoration process unambiguous. When you restore months or years later, you will not need to guess.
For Monero wallets in particular, some users also record a transaction ID or block height of a known transaction. If your first deposit was 50 XMR at block 2,750,000, write that down. During restoration, you now have an exact reference point. You know the restore height must be at or below block 2,750,000 to capture that transaction.
Another best practice is to test your backup before you need it. After creating a wallet in Cake Wallet and confirming it has received funds, export the seed phrase and restore it to a fresh wallet on another device or in another app (if you have access). Confirm the address matches and the balance appears correctly. This is a recovery drill. It costs nothing except time and reveals problems—wrong seed type, incorrect restore height, seed phrase typos—while your original wallet is still intact.
For users migrating from a closed service, Cake Wallet provides guidance on restoring wallets from MyMonero, Exodus, and other legacy wallets. These migrations often involve determining the correct restore height based on account creation dates or transaction histories from the old service. Review the migration guide carefully before attempting a restore to avoid re-entering an incorrect starting point.
When restore height is correct but balance remains zero
If you have confirmed the restore height is set early enough to capture your transactions, the wallet is fully synced, and the address is correct, but the balance is still zero, a few less common issues could be at fault. The first is a corrupted wallet file. If the wallet file on disk is damaged or partially overwritten, the wallet may load but fail to display balances correctly. In this case, delete the wallet and restore from the seed phrase again to get a fresh wallet file.
The second is an issue with the node connection. Some public Monero nodes are out of sync, behind the network tip, or returning incorrect data. If you are connected to a questionable node, switch to a different one and rescan. Cake Wallet offers a choice of public node operators. Try a few different ones to isolate whether the problem is specific to one node or network-wide.
The third is a genuinely incorrect seed phrase. If you have tested the seed against a known address and the address does not match what you expect, the seed is wrong. You may have written it down incorrectly, forgotten a word, or have a seed phrase from a different wallet altogether. In this case, you will need to retrieve the correct seed phrase from its original source (a written backup, a password manager, or the original device where the wallet was created).
Finally, confirm that your funds were actually sent to this wallet’s address. If you received Monero to a different address, a different wallet, or a centralized exchange deposit address, this wallet will not show the balance even if everything is configured correctly. Check your exchange history or payment records and verify the destination address against the Cake Wallet address. Monero addresses are long and can be easy to misread; copy and paste rather than comparing by eye.
Beyond Monero: Restore height and other supported coins
Restore height is specific to Monero’s privacy and scanning model. Bitcoin, Litecoin, Ethereum, and other coins supported by Cake Wallet use different scanning methods. Bitcoin and Litecoin derive multiple addresses from a single seed and scan public ledgers to find transactions matching any of those addresses. They do not use a restore height in the same sense; instead, they use a creation date or block height as a hint to skip unnecessary scanning.
Bitcoin wallets typically default to scanning from a fixed point in the past or from the wallet creation date. If you create a Bitcoin wallet today and restore from a seed that received funds five years ago, the wallet will still find the transactions because it scans backward from the current time, not from a specified point forward. Litecoin and Ethereum follow similar patterns.
However, the principle remains relevant: a wallet must know where to start scanning to find your funds efficiently. For Bitcoin, this is usually managed automatically, but for Monero, it requires user input. When you use Cake Wallet to manage multiple coins, keep in mind that restore procedures and scanning behavior differ. A Monero restore needs careful restore height selection; a Bitcoin restore typically does not.
Frequently asked questions
I did a cake wallet download, restored my Monero seed, and see zero balance even though the wallet is synced. What went wrong?
The most common cause is an incorrect restore height. You specified a block number or date that is too recent, so the wallet scanned forward from a point after your funds arrived and never saw them. Lower the restore height to an earlier date—weeks or months before you believe you last received funds—and rescan. Once the balance appears, you have found the correct starting point.
How do I know if my restore height is too recent?
Check your backup records for the date you created the wallet or last confirmed a balance. If you have a transaction ID from a known payment, look it up on a Monero block explorer to see which block it is in. Your restore height must be at or below that block number. If you have no records, set the restore height to several months before your best guess and let the wallet rescan. You can always move backward; moving too far forward causes you to miss transactions.
Can I change the restore height after the wallet is already created?
Yes. In Cake Wallet, you can access the wallet settings and adjust the restore height, then trigger a rescan. The wallet will re-examine blocks starting from the new height. This does not create a new wallet or affect your seed phrase; it simply tells the wallet to scan a different section of the blockchain. Once you find the correct height and the balance appears, you can leave it set to that point.