Skip to content

Fix: stuck / unconfirmed transactions (zapwallettxes)

Support safety (read this first)

  • Admins/devs will not DM you first. Keep support conversations public (Telegram group / GitHub issues).
  • Never share your seed phrase, private keys, or wallet.dat with anyone.
  • Use only official download links (https://reddcoin.com / https://redd.love / https://download.reddcoin.com). Beware look‑alike sites.
  • If someone asks you to “verify” by sending coins, installing remote-control software, or sharing secrets (seed/private key), it’s a scam.
  • When sharing logs/screenshots publicly, redact personal info (paths, IPs, usernames). Do not redact block hashes needed for fork checks.
  • If you’re not sure what to back up (and where it lives), see Reference → Wallet files & locations in this knowledgebase.

Applies to: Core desktop wallets (mostly v3.x; still relevant conceptually in v4)

Symptoms

  • You sent RDD but it stays unconfirmed
  • Transaction shows as “stuck”
  • Balance looks “locked” by an unconfirmed tx

The standard fix

Community support repeatedly points users to the legacy wiki runbook for zapwallettxes, and recommends setting a small custom fee afterward to avoid repeats. 1 2

  1. Follow the runbook:
  2. Legacy wiki: “Remove stuck transactions with zapwallettxes”
  3. After clearing the stuck tx, resend with a custom fee (example settings below).

Fee settings (field-tested)

In the Send window:

  • Choose Custom
  • Choose total at least
  • Set total at least = 1 RDD
  • Ensure “Send as zero-fee transaction if possible” is unchecked

With those settings, admins noted the fee typically becomes 0.1 RDD. 1

Footnotes

  1. Telegram export (ReddCoinOfficial), obito, 2 Mar 2024 03:47 UTC-05, message1984569 (messages947.html). (zapwallettxes wiki link + fee settings.) ↩↩

  2. Telegram export (ReddCoinOfficial), Kpcrypt0, 21 Feb 2024 16:11 UTC-05, message1982275 (messages945.html). (zapwallettxes wiki link + set custom fee.) ↩