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.
