XELIS Wallet troubleshooting — solve common problems

1. Confirm your internet connection is working.
2. Open Settings → Network.
3. Switch from the default remote node to another listed node, or enable the built-in node toggle.
4. Restart the wallet.
5. If you're on a corporate or restrictive network, allow the XELIS Wallet executable through your firewall.

Persistent connection issues are usually network-side. Try from a phone hotspot to rule out your home network.

1. Note the block height you're stuck on and wait 5 minutes — sometimes the wallet is fetching a large chunk.
2. If still stuck, switch to a different remote node in Settings → Network.
3. Close other heavy applications to free CPU.
4. Confirm you have at least 1 GB of free disk space.
5. As a last resort, quit the wallet, reopen it, and let it resume sync.

• Wallet must be fully synced — check the sync indicator.
• You need enough balance for the amount plus the network fee.
• Recipient address must be a valid XELIS address (typically starts with xel: or similar).
• If it still fails, send a small test amount first to confirm the workflow.

There is no password reset — the password encrypts the file locally and only you have it. If you have your seed phrase, you can recover:

1. Open XELIS Wallet and choose Restore wallet.
2. Follow our recovery guide.
3. Set a new password during the restore.

Without the seed phrase and without the password, the funds are unrecoverable.

1. Update to the latest version from the download page.
2. Check the system log (Event Viewer / Console / journalctl) for an error message.
3. Reinstall the wallet — your encrypted wallet file is stored separately and won't be touched.
4. If the wallet file itself is corrupt, restore from your seed phrase using the recovery guide.

This is expected during initial sync — the wallet verifies cryptographic proofs as it catches up. Once sync hits 100%, CPU usage should drop to near zero.

If it stays high after sync completes, quit and reopen the wallet. If the issue persists, switch to a remote node in Settings → Network to reduce verification load.

Treat antivirus warnings seriously. Before overriding anything, confirm the file came from an official source:

1. Check that you downloaded from xeliswallet.com or the official GitHub release page.
2. If you're unsure, delete the file and re-download from the official source.
3. If you are confident the file is genuine, you can decide whether to add an antivirus exception, following your antivirus vendor's official documentation.

Never disable your antivirus globally for any wallet installer.

• Confirm the sender used the exact address you provided — they should have copy/pasted it.
• Make sure your wallet is fully synced.
• Because XELIS uses confidential transactions, public block explorers cannot show you the amount. Trust your wallet's view of incoming transactions.
• If hours pass with no incoming transaction shown, ask the sender to confirm the transaction hash and check that hash in their wallet's transaction history.

The wallet acquires an exclusive lock on its data directory so two processes can't corrupt the same encrypted file. The lock is released when the wallet exits cleanly.

1. Close every visible XELIS Wallet window.
2. Check for a background process: Windows Task Manager, macOS Activity Monitor, or pgrep -fa xelis_wallet on Linux.
3. If a stale lockfile remains after a crash, delete the LOCK file inside your wallet data directory (never delete the wallet file itself, only the empty LOCK marker).
4. If two installs (e.g. portable + installed) point at the same data directory, decide on one and remove the other from autostart.

1. Open Settings → Network and switch to a different remote node. Public node lists rotate frequently.
2. Verify outbound TCP port 2125 is allowed by your firewall and not blocked by a corporate / hotel / mobile-carrier network.
3. Test from a phone hotspot to isolate whether the issue is your local network.
4. For maximum reliability, run your own xelis_daemon on the same machine or on a VPS and point the wallet at 127.0.0.1:2125. See the setup guide for the full walkthrough.
5. Tor users: route the wallet's RPC client through a SOCKS5 proxy at 127.0.0.1:9050 — flaky Tor circuits look identical to peer drops.

'Pending' in XELIS Wallet means the transaction has been broadcast but the wallet hasn't yet observed it inside a confirmed tip block. Two checks resolve almost every case:

1. Confirm your wallet is fully synced (height matches a public node). A wallet 50 blocks behind will report its own recent send as pending even though the network sees it confirmed.
2. If still pending after a fresh sync, the transaction may have been rejected for an insufficient fee. Re-broadcast from the wallet's transaction history — XELIS Wallet keeps the signed payload locally for exactly this case.
3. Never re-create the same transaction from scratch. Two competing signed transactions spending the same balance create UI confusion even though the protocol only accepts one.

Because XELIS uses confidential transactions, you cannot verify the amount on a public block explorer — only the sender and recipient wallets can decrypt the encrypted balance commitment. This is by design, not a bug.

1. Let the wallet finish the initial scan. The progress indicator at the bottom of the window shows scan height vs. chain height — both numbers must match.
2. If you typed the seed instead of pasting from your hardware backup, double-check word order and spelling. A single transposed word produces a valid-looking but completely different wallet that will always show zero balance.
3. Confirm you restored on the same network (mainnet vs. testnet). The dropdown in the restore dialog matters.
4. If balance is still wrong after a full re-scan on the correct network and correct seed, force a rescan from a specific height in Settings → Advanced → Rescan from height.