My bitcoins keep going back into the mempool !

[sirstevie6]

Hi

I hope someone can help me.

I am running node and have a pc based bitcoin wallet (bitcoin-qt ver 0.15.1 64 bit) running on MS Windows 10.

I decided to transfer some bitcoins to another address and clearly did not offer the miners enough money (I used the default recommendation that the bitcoin-qt suggested).

The transaction stayed in the mempool and was unconfirmed.

I then decided I did not want to send the transaction - I was told about the following two command line parameters i.e.

-walletbroadcast=0 and
-zapwalletttxes=1

I tried both and they worked perfectly cancelling the transaction which is now no longer in the mempool and is now showing up as bitcoins in my wallet, BUT and this is the odd part, every other day the original transaction shoots of again and appears in the mempool as unconfirmed - if I repeat the above two command line parameters it is once again fixed but only for a day or so when they once again fire of - does anyone know how I can stop the transactions going ahead? Any help or thoughts would be hugely welcomed.

Thanks
Stephen

[DannyHamilton]

every other day the original transaction shoots of again and appears in the mempool as unconfirmed - if I repeat the above two command line parameters it is once again fixed but only for a day or so when they once again fire of

As long as the original transaction is a valid transaction, ANYBODY in the world that saw the original transaction (including the original recipient) can re-broadcast it if they want to.

does anyone know how I can stop the transactions going ahead? Any help or thoughts would be hugely welcomed.

If the original transaction becomes invalid, then nobody will be able to rebroadcast it any longer.  You can invalidate the original transaction by creating a transaction that spends at least one of the same inputs and which gets confirmed.