Post
Topic
Board Bitcoin Technical Support
Re: Sent A Few Btc Accidentally with no Trnsaction fee Attached
by
imnotarobot
on 01/09/2016, 10:11:16 UTC
Something  you are saying doesn't make sense.

You claim that you are running

a very old wallet (0.8.3 i think)

But then you say
i tried to use the code
Code:
abandontransaction
in the help>console, but it came back: Invalid or non-wallet transaction id (code -5)

abandontransaction didn't exist until 0.12.0

Did you upgrade after sending your transaction, or were you actually running the very recent 0.12.0 and not the 0.8.3 that you thought you were running?

Assuming that you are running some version of Bitcoin Core, it will not "drop out of the memory pool at some point and return to my wallet" on its own.  Bitcoin Core is designed to remember the transactions that you have sent and re-braodcast them regularly to remind the rest of the network if they drop the transaction from their memory pool.

If you want your Bitcoin Core to drop the transaction from it's memory pool, you'll need to tell it to do so.

Once option is to run the wallet with the -zapwallettxes command line option.

Another option is to broadcast a different transaction that uses at least one of the same inputs and pays a high enough fee to get confirmed.  Once the new transaction becomes confirmed, your old one will become invalid so your wallet will drop it.

If you want to broadcast a different transaction that uses at least one of the same inputs, I can help you build and broadcast it.  You'll just need to provide the raw transaction.

You can get the raw transaction by running the following in the console:
Code:
getrawtransaction 417b1e741a30571bf27138a965864c27d5bb99c617a7b5864a3d3a24c959b928
Danny,

i did have an old wallet, 0.8.3.,  which constantly gave me the dreaded I/O Database Error. i suffered through having to reopen it after it would crash repeatedly for about ten days to get it to sync up, i was not sure the data would transfer over to the new wallet or if i could even upgrade with such a distance between my wallet and 0.13.0. it did and i really had nothing to worry about, guess i should have come here first, oh well.

yes, i sent the transaction while it was out of sync and it had been so long since i made a transaction, i just sent it without realizing that it needed a fee sent along with it for processing.'

do i need to enter the transaction ID with the -zapwallettxes? and then will the amount show in my wallet again?

how do i broadcast a different transaction that uses at least one of the same inputs and pays a high enough fee to get confirmed?

the raw transaction is: 0100000001e81744912de02ab727f10e551ce1d58ff0707e1f7732dde3568af65149b2cfcc00000 0006b483045022100f5b2398e6ab62a65a2db147051b0c302f272c634e6c7f303bf04f2bb0a69f1 b502206a194aa42aa2a0a92a48b1440aebb03ec7aba9ba979b8f2939b61513bc2ba4bf0121025c5 21e2e1858a33fe0942e8c114a78fd4b4fcdf5e9696ac6f605b204399c1231ffffffff029b05fe1a 000000001976a9140114f4219ee59e426ff608df1dd4b4abc378298488ac20c8561100000000197 6a914d968ca8825d27c3e20e5653a978548516099726888ac00000000

thank you for your help.