Cake Wallet not syncing: how to fix a stuck sync
If Cake Wallet will not sync, pull down on the home screen to reconnect, try another network, then switch to a different node in Settings. Monero and Litecoin MWEB need a long first sync, so keep the app open on Wi-Fi until the Blocks Remaining counter reaches zero. If you use a .onion node, built-in Tor must be on.
Quick steps
- Pull down to reconnect. On the home screen, pull down to reconnect to the current node and watch the status at the top.
- Change network or VPN. Switch between Wi-Fi and mobile data, and turn your VPN on or off, to rule out a network that blocks crypto nodes.
- Switch to another node. Open Settings, the coin's settings, then Nodes, and select a different node that responds.
- Check custom node settings. For your own node, confirm the address, port and SSL setting match what the node actually serves.
- Turn Tor on for onion nodes. If you use a .onion node, enable built-in Tor under App settings, Connections, or use a clearnet node.
- Keep the app open. For Monero and MWEB, keep the app open on Wi-Fi until Blocks Remaining reaches zero. On Android, turn on background sync.
- Fix the restore height. If a restored Monero wallet scans from far back or misses funds, rescan from a date shortly before your first deposit.
Syncing means your wallet downloads blockchain data from a node and finds the transactions that belong to you. Until it finishes, your balance and history may be incomplete and sending can fail. Cake Wallet's documentation stresses that funds stay safe on the blockchain while you sync: syncing only affects whether you can see and spend them (Cake Wallet docs, 2026).
What the sync status means
The status appears at the top of the home screen. These labels come from the app's English text files (Cake Wallet 6.x source):
| Status | Meaning | Next step |
|---|---|---|
DISCONNECTED / NOT CONNECTED | The wallet cannot reach the node | Change network or VPN, then change node |
CONNECTING | A connection is starting but is not stable yet | Wait a minute; if it stays, change node |
ATTEMPTING SYNC | The node answered and data is being exchanged before syncing | If it stays for minutes, switch to another node |
Blocks Remaining | Syncing is in progress | Keep the app open until it reaches zero |
TIMED OUT / Sync Timed Out | The node stopped responding | Reconnect or change node |
UNSUPPORTED NODE | The node does not offer what this wallet needs | Choose a different node |
SYNCHRONIZED or no status | The wallet is up to date | Nothing to do |
You can switch the progress display between blocks remaining and an estimated time with the "Sync Status Display" option.
Quick fixes for every coin
- Pull down to reconnect. Cake Wallet's docs give this as the quick fix.
- Try another network. Cake Wallet says some mobile carriers and Wi-Fi networks block crypto connections. Switch between Wi-Fi and mobile data.
- Adjust your VPN. A VPN can get around a blocking network, but some VPN providers block crypto nodes, so also try with the VPN off.
- Change node. Open Settings (top right), choose the coin's settings, then Nodes, and pick another node. The node list can re-test nodes so you can see which ones respond.
- Update the app from an official source, then force close and reopen it.
Monero sync is slow or stuck
Monero is the coin people most often report as slow. Your phone must check every block since the restore height, so an old restore height means a long first sync. Cake Wallet's advice (Cake Wallet docs, 2026):
- Use a reliable node close to you, or run your own Monero node.
- Use a stable network without filtering, ideally Wi-Fi.
- Keep the app open in the foreground. Syncing pauses when the app is fully closed.
- If the block count has not changed for a long time, switch to another node.
If a newly created wallet seems to scan from very far back, check the restore height. A 16-word Polyseed stores its own creation date, but a 25-word seed does not, so a restore with no height scans from the start of the chain. Use our restore height finder to pick a date shortly before your first deposit. Setting it a little early is safe; setting it too late hides funds.
Bitcoin and Litecoin
Bitcoin and Litecoin wallets connect to Electrum-style servers, so sync is usually quick. If it stalls, change node. On a custom node, check the port and SSL setting: Cake Wallet's docs say the most common cause of an unreachable node is SSL turned on for a non-SSL port, or the reverse. Electrum servers over SSL commonly use port 50002 (Cake Wallet docs, 2026).
If you use Bitcoin Silent Payments, the wallet also scans blocks on your device for payments to your sp1 address, shown as "Silent Payments Scanning". This uses battery and data and is separate from the normal sync. See Silent Payments.
Litecoin MWEB first sync
When you turn on MWEB (Settings, Litecoin Settings, MWEB, then "Enable MWEB"), the app shows this warning: Using MWEB will initially download ~600MB of data, and may take up to 30 minutes depending on network speed. The download happens once per device for all Litecoin wallets. Start it on Wi-Fi with the app open. If you turn MWEB off, your MWEB address still works, but you must turn scanning back on to see funds sent to it. MWEB is available on iOS and Android (Cake Wallet docs, 2026). More in Litecoin MWEB.
Tor and .onion nodes
A .onion node only works while Tor is running. Turn on "Enable built-in Tor" under Settings, App settings, Connections, or switch to a clearnet node. Cake Wallet labels built-in Tor as experimental and says syncing over Tor is much slower than over clearnet, especially large rescans (Cake Wallet docs, 2026). If you see Tor connection timeout, try again or turn Tor off to test whether Tor is the cause. See Tor and privacy settings.
Background sync on Android
On Android, Cake Wallet can sync while the app is closed. Go to Settings, App settings, Connections, Background sync, turn it on and allow the app to run unrestricted in the background. Modes run roughly every 18 hours, every hour or every 15 minutes. Cake Wallet says it works for all wallets except hardware wallets and Decred, and that Monero background sync uses only the private view key (Cake Wallet docs, 2026). It is not available on iOS.
Still not syncing?
Contact support from inside the app or at [email protected] with your app version, device, coin and node. Do not send your seed: Cake Wallet never asks for it and never messages you first. Never "fix" sync by importing your seed into a website or an unknown app.
Frequently asked questions
How long does Cake Wallet take to sync?
It depends on the coin, the node, your network and the restore height. Bitcoin is usually quick. Monero with an old restore height and the first Litecoin MWEB sync (about 600 MB, up to 30 minutes according to the app) take longest.
Are my funds safe while the wallet is not syncing?
Yes. Funds are on the blockchain. Syncing only affects whether the app can show and spend them.
Why does Cake Wallet stay on Attempting sync?
The node accepted the connection but is not serving data. Cake Wallet's docs recommend switching to another node.
Does Cake Wallet sync in the background on iPhone?
Cake Wallet documents background sync for Android only. On iPhone, keep the app open until sync finishes.
Does Tor make syncing slower?
Yes. Cake Wallet says syncing over Tor is much slower than clearnet, especially for large rescans.