Fix common errors in a minute

“Server not responding” / balance or history will not load

Looks like: a notice saying the chain-data server cannot be reached, a balance stuck on “—”, an empty history.

Why it happens: the wallet reads the chain from a public data server. Your VPN exit, your network’s filtering, or a rate limit can block that route for you while it works for everyone else. The wallet itself is fine, it just cannot see the chain from where you are.

1. Click “Try the next server” right on the error, or pick another server under Settings → General → Chain-data server. One click is usually the whole fix.
2. Toggle your VPN: if it is on, turn it off and refresh. If it is off, turn it on (a different route often clears a block).
3. Test with your phone’s hotspot, VPN off. If the wallet loads there, your normal network or VPN was the blocker, not the wallet.
4. Wait a minute and refresh. Rate limits pass on their own.

Send fails: “the broadcast could not reach the network”

Looks like: balance loads fine, but pressing Confirm ends with a blocked or dropped connection message.

Why it happens: a signed BTX transaction is a large upload (post-quantum signatures are big). Antivirus “web protection”, a firewall, or a VPN often lets small reads through and kills exactly this bigger upload. Classic signature: everything loads, only sending fails.

1. Check History or the explorer first. The wallet tells you when nothing left the wallet, and it protects you from double-sending either way.
2. Pause your antivirus’s web shield for a minute (the module with “web” or “online” in its name), then press Confirm again. Turn it back on after.
3. Toggle your VPN (on if off, off if on) and try again.
4. Switch networks: the phone-hotspot test again. If it sends there, the blocker is on your normal network.
5. Try the next chain-data server in Settings → General, then Confirm again.

“Your previous send is still confirming”

Looks like: right after one send, the next send says there is nothing to spend yet.

Why it happens: this one is not an error at all. The change from a send becomes spendable when that send confirms (BTX blocks come roughly every 90 seconds). Two sends back to back cannot chain on an unconfirmed one.

1. Wait one or two minutes, refresh, send again. That is the whole fix.

“Could not check all your coins” / coins set aside

Looks like: a send is refused with a note that some coins were set aside this round.

Why it happens: the data server answered incompletely, and the wallet refuses to guess. Some of your coins can carry relics or NFTs, and spending one blindly would destroy it, so anything the wallet cannot fully verify is parked, never spent. This is protection working, not a bug.

1. Try again in a moment, or switch to the next chain-data server and retry.
2. Your artifacts and coins are untouched either way; the wallet fails on the safe side by design.

On an old version, or the update banner is blinking

Newer versions fix real problems. If your wallet shows an update banner, or your version is older than the one on the site, get the current build and verify its SHA-256 before running it.

1. Download the newest installers here: pq-wallet.com/download
2. Compare the SHA-256 on the verify table before you open the file.

macOS will not open the app the first time

Why it happens: the app is not code-signed yet, so Gatekeeper flags the first launch. Normal for a new independent app, and you only clear it once.

1. Follow the two-step guide: pq-wallet.com/macinstall

Still stuck?

If none of the above clears it, tell us properly so it gets fixed for everyone: what you did, the exact error text, your OS, and whether the hotspot test changed anything.

1. Open an issue: github.com/MendeMatthias/pq-wallet/issues
2. Check what changed recently: the changelog