Arqma Wallet not syncing — fix guide

What “syncing” actually means

The wallet doesn’t hold your balance — the blockchain does. To compute your balance the wallet has todownload recent blocks (either directly, when running a full node, or via a remote node that does it for you) and scan them for transactions belonging to your keys. Syncing is that download + scan step.

When syncing stalls, one of four things is wrong: network, node, wallet version, or the wallet’s scan starting point. We’ll check each.

Quick triage (try this first)

1. Close the wallet completely and reopen it.
2. Confirm your computer is online — load any website to be sure.
3. Wait two minutes. Many “stuck” reports are just the wallet catching up after a sleep.

If the block counter is moving, you’re fine — let it finish. If it’s still frozen, continue below.

Cause 1: Network or firewall is blocking the wallet

The wallet talks to a node over the internet. Corporate networks, public Wi-Fi captive portals, and overly strict firewalls will silently block that traffic.

Check

• Try a different network (phone hotspot is a good test).
• Temporarily disable your VPN and try again.
• Disable your firewall briefly as a test; re-enable it after.

Fix

If hotspot fixes it, your home or office network is blocking outbound connections. Add an outbound allow rule for the wallet binary, or switch to a remote node on an open port.

Cause 2: Your node is down or unreachable

In remote-node mode the wallet connects to a third-party node operator. Nodes go offline for updates, maintenance, or hardware failures. You’ll see the wallet stop at a specific block height and refuse to progress.

Check

Open Settings → Node. Look for “Disconnected” or a stale block height. Compare the wallet’s “current block” with the public block explorer’s latest block — if the explorer is much higher, your node is behind.

Fix

• Pick a different remote node from the dropdown.
• Or run your own node — see community channels for current operator recommendations.
• If you’re on a full node, give it more time. Initial full-node sync can take hours on slow connections.

Cause 3: The wallet is out of date

After a network upgrade, older wallet versions can refuse to sync past the upgrade block. The symptom is a wallet that stops cleanly at the same block every time you restart it.

Check

Open Help → About. Compare the version with the latest on the download page.

Fix

Download the latest version, install it over the old one, and reopen the wallet. Your wallet file and seed are unaffected by an upgrade.

Cause 4: The wallet is scanning from too early

A freshly-restored wallet has to scan every block from its creation height forward. If you set the restore height too low (or left it at 0), the wallet is scanning years of blocks. That looks “stuck” but is actually slow progress.

Check

Open the sync status. If it’s slowly counting upward but a long way from current, this is your cause.

Fix

Close the wallet. Reopen it and use Tools → Set restore height to a block close to your first deposit. The wallet will resync from there in minutes instead of hours. If you don’t remember when you first deposited, look up the date and use the block-height-by-date lookup on a public block explorer.

How long should sync take?

• Remote node, casual use: 30 seconds to 2 minutes after launch.
• Remote node, fresh restore with correct restore height: 5–15 minutes.
• Full node, initial sync: 2–8 hours depending on disk and internet speed.

Verify on a block explorer

If the wallet says you have a different balance than you expect, paste your public address into a block explorer. The explorer is the source of truth; if it shows your transactions, they exist, and the wallet just hasn’t scanned them yet.

Still stuck?

Capture: wallet version, OS, node setting, the block height the wallet is stuck at, and the explorer’s current block height. Post those four in the community channels and someone will help quickly. Don’t share your seed phrase, address, or wallet file.