Troubleshooting common Electrum RVN issues.
The fixes for ~90% of support requests, written out so you don't have to wait for a thread to be answered.
Most issues fall into one of seven categories.
After enough support threads it becomes clear that almost every problem reduces to a small set of root causes: a stuck network connection, a derivation-path mismatch on restore, a wrong-chain deposit, a hardware-device handshake issue, a fee that is too low for current mempool conditions, or a misunderstanding about what a 'pending' transaction actually is. The fixes are short; the diagnosis takes most of the time.
Check the server under Tools → Network. Try a different server from the list, or temporarily set "Auto-connect" if it's off.
Firewalls (corporate, ISP-level, or third-party security software) account for the majority of "won't sync" reports. The wallet connects on a non-standard port; some firewalls block it by default. If switching servers doesn't help, test on a different network (mobile hotspot) to isolate whether the issue is local or network-wide. Confirm with a fresh install if a recent upgrade coincided with the issue starting.
Transaction is stuck unconfirmed
Two causes: fee too low for current mempool conditions, or mempool congestion that is clearing on its own. On Ravencoin both are rare and short-lived — the chain has ample block space and 1-minute blocks — but they happen. If the transaction has been pending for hours, bump the fee with Replace-By-Fee (Transactions tab → right-click → Bump fee), which broadcasts a higher-fee replacement that miners prefer.
- Check fee on the original transaction — under-paid sends sit in the mempool indefinitely.
- Use Replace-By-Fee to broadcast a higher-fee replacement.
- If the transaction was zero-fee or near-zero, expect it to drop out of the mempool eventually and free the inputs.
- Don't broadcast a second transaction spending the same inputs without RBF — you'll have two competing transactions confusing the wallet.
Ravencoin uses base58 addresses starting with the letter R. If an exchange withdrawal form asks for an Ethereum-style 0x... address, you are on the wrong deposit page — confirm the deposit network is "Ravencoin (RVN)" and not an ERC-20 wrapper, a Binance Smart Chain version, or any other bridged token. Sending RVN to an ETH-format address on the wrong chain is the most common way to lose funds during a withdrawal.
Close every other application that might be talking to the device — Ledger Live, Trezor Suite, any browser tab with a web wallet open, any other Electrum wallet. On Linux, install the vendor's udev rules so the device is reachable without root (Trezor publishes a trezorpackage on most distributions; Ledger documents the equivalent rule file). Then unplug, replug, unlock the device, open the Ravencoin app (Ledger) or just confirm the device is unlocked (Trezor), and retry the wallet's "Detect hardware wallet" action.
Restored wallet shows zero balance
Almost always a derivation-path mismatch. The 12 words are correct; the wallet is correctly restored; the addresses being scanned are just not the ones your funds live on. Try the alternate Ravencoin derivation path the wallet offers, or restore using the original software you created the wallet with. Verify on a public block explorer that the addresses the wallet shows in the Receive tab match the addresses you expect funds at — wrong derivation produces valid-but-empty addresses that are nobody's funds.
If you have the seed phrase, restore into a new wallet file with a new password — the old encrypted file can be deleted. If you do not have the seed and do not have the password, the funds are unrecoverable. Brute-forcing a strong password is not realistic. The lesson is operational: the seed is the only true backup, and it must exist before the password is ever forgotten.
First, wait for confirmations — issuance transactions need to confirm before the asset appears in the balance list, and asset history sometimes takes a few extra refresh cycles to populate. Right-click the issuance transaction in History and choose "Rebroadcast" if it's been more than a few blocks. If the transaction is confirmed but the asset still doesn't show, switch to a different server in Tools → Network and let the wallet re-fetch.
- Confirmed issuance + missing asset balance: switch servers, then re-scan.
- Unconfirmed issuance: wait, then rebroadcast if needed.
- Asset transferred to a non-asset-aware wallet: import that wallet's seed into Electrum RVN to recover.
- Asset sent to a wrong address: nothing the wallet can do — addresses are bearer.
When a balance looks wrong
First, confirm the chain rescan has actually finished — a partial scan shows partial balances. Second, confirm the wallet is using the same derivation path that originally created the seed. Third, check a public block explorer against the addresses the wallet has derived; if the explorer shows the funds and the wallet doesn't, the problem is on the client side and a restore-from-seed into a fresh wallet usually clears it.
Most connection failures are local network issues — a firewall blocking outbound on the Electrum-style ports, a captive portal, or a VPN routing the traffic through a dead exit. Try toggling the network, switching servers in the wallet settings, and confirming the system clock is roughly correct (TLS handshakes fail on skewed clocks). If the wallet still won't connect, the public server pool may be temporarily degraded — wait a few minutes and retry.
Frequently asked
Continue with Electrum RVN
- restore Ravencoin wallet — rebuild from your 12-word backup
- Electrum RVN setup — walk through setup from scratch
- Electrum RVN download — fetch a clean build if yours is broken
Run your own Ravencoin wallet.
Open-source, lightweight, and built for the desktop user who wants real control over keys and assets. Download the wallet directly from our download page — signed installers for every operating system.