Sent A Few Btc Accidentally with no Trnsaction fee Attached

[imnotarobot]

long story but the short of it is:

i had a very old wallet (0.8.3 i think) and sent a few Btc with what i later discovered to be a o.o transaction fee. it is now stuck i believe. how do i get it unstuck? all help will be greatly appreciated.

also, i am kind of a noob so not sure i will understand tech speak so if it could be explained like i am a five year old, that would be greatly appreciated as well.

TYIA

[1715317556]

1715317556

[1715317556]

1715317556

[1715317556]

1715317556

[bitkilo]

Showing us the transaction might get you the help you need a little quicker.

[imnotarobot]

sorry, bitkilo. i tried to post it after i realized i hadn't but being a newbie i had to wait 360 seconds to repost and i got lost trying to research it in another thread.

the transaction code is: 417b1e741a30571bf27138a965864c27d5bb99c617a7b5864a3d3a24c959b928

i tried to use the code

Code:

abandontransaction <txid>

in the help>console, but it came back: Invalid or non-wallet transaction id (code -5)

so i'm stumped at this point.

[imnotarobot]

looking at the details of the transaction:

Status: 0/unconfirmed, in memory pool
Date: 8/29/2016 20:35
To: 1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv
Debit: -2.90900000 BTC
Net amount: -2.90900000 BTC
Transaction ID: 417b1e741a30571bf27138a965864c27d5bb99c617a7b5864a3d3a24c959b928
Output index: 0

i see that it is in the memory pool. will it drop out of the memory pool at some point and return to my wallet?

[DannyHamilton]

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 <txid>

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

[achow101]

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?

Furthermore, if he upgrades to/is using 0.13, then he can just right click the transaction in the transaction list and select Abandon transaction instead of going to the console.

Code:

dumprawtransaction 417b1e741a30571bf27138a965864c27d5bb99c617a7b5864a3d3a24c959b928

It's actually getrawtransaction not dumprawtransaction

[DannyHamilton]

Code:

dumprawtransaction 417b1e741a30571bf27138a965864c27d5bb99c617a7b5864a3d3a24c959b928

It's actually getrawtransaction not dumprawtransaction

Thanks.  I fixed my post.  Silly mistake on my part, I should know better.

For some reason I seem to get dumpprivkey and getrawtransaction mixed up regularly.  More than once I've suggested using "getprivkey" and/or "dumprawtransaction".

[Wind_FURY]

Newbie question here. Can "Abandon transaction" be done on SPV or light wallets or do I have to use the core wallet to do that? I have the impression that light wallets should have that feature too but I am not really sure that there is one at the moment.

[imnotarobot]

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 <txid>

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.

[imnotarobot]

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?

Furthermore, if he upgrades to/is using 0.13, then he can just right click the transaction in the transaction list and select Abandon transaction instead of going to the console.

Code:

dumprawtransaction 417b1e741a30571bf27138a965864c27d5bb99c617a7b5864a3d3a24c959b928

It's actually getrawtransaction not dumprawtransaction

hi knightdk, thank you for responding.

i had tried the 'abandon transaction' feature by right clicking the transaction, however it was not highlighted and as such, would not let me select it. i wonder why it is not highlighted?

[DannyHamilton]

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.

Looking at the raw transaction it appears you're attempting to spend the 7.43755195 BTC output that was received in transactionID cccfb24951f68a56e3dd32771f7e70f08fd5e11c550ef127b72ae02d914417e8 on April 2, 2013. This input into your new transaction provides 7.43755195 BTC of value for your transaction to re-assign in new outputs.

It looks like your transaction is probably sending 2.909 BTC to 1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv in one output while sending the remaining 4.52855195 BTC back into your wallet at the new internal address of 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67 in a second output.  As such (since 4.52855195 + 2.909 = 7.43755195) there are no bitcoins remaining for the transaction fee.

If I've understood correctly what you are trying to do (send 2.909 BTC to 1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv while keeping control of the rest of the bitcoins, then you can just reduce the value of the output to 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67 by the amount that you want the transaction fee to be.

The following command (if copied and pasted into your Bitcoin Core console) will create a raw transaction that spends the exact same 7.43755195 BTC output, and still sends 2.909 BTC to 1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv, but only sends 4.52835195 BTC back into your wallet at 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67.  The remaining unaccounted for 0.0002 BTC will become a transaction fee.

Code:

createrawtransaction '[{"txid":"cccfb24951f68a56e3dd32771f7e70f08fd5e11c550ef127b72ae02d914417e8","vout":0}]' '{"1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv":2.90900000,"16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67":4.52835195}'

That command re-uses as an input the exact same 7.43755195 BTC input from cccfb24951f68a56e3dd32771f7e70f08fd5e11c550ef127b72ae02d914417e8 as your current transaction uses.  That means that ONLY one of these two transactions can ever confirm.  If your current transaction confirms soon, then this new transaction will become immediately invalid and the entire network will reject it.  If this new transaction confirms, then your current transaction will become immediately invalid and the entire network will reject it.  As such, you won't run the risk of accidentally transferring 5.818 BTC to 1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv (2.909 BTC twice).

I can understand if you might be concerned that I could be misleading you. That's why I've posted publicly here instead of sending a PM. You can wait and see if any other knowledgable people see this post and warn you not to do it.

The result of the command should be:

0100000001e81744912de02ab727f10e551ce1d58ff0707e1f7732dde3568af65149b2cfcc00000 00000ffffffff0220c85611000000001976a914d968ca8825d27c3e20e5653a9785485160997268 88ac7bb7fd1a000000001976a9140114f4219ee59e426ff608df1dd4b4abc378298488ac0000000 0

You can then use the following command in the console to sign the transaction so that it is ready for broadcast:

Code:

signrawtransaction 0100000001e81744912de02ab727f10e551ce1d58ff0707e1f7732dde3568af65149b2cfcc0000000000ffffffff0220c85611000000001976a914d968ca8825d27c3e20e5653a978548516099726888ac7bb7fd1a000000001976a9140114f4219ee59e426ff608df1dd4b4abc378298488ac00000000

or if you prefer not to trust the raw transaction that I've created for you, then you can replace that hex string with the results you get when you run the createrawtransaction command yourself.

You can then copy the hex output from the signrawtransaction command and paste it into the forms at the following websites to broadcast it to the network:

https://btc.blockr.io/tx/push
https://blockexplorer.com/tx/send
https://live.blockcypher.com/btc/pushtx/
https://coinb.in/#broadcast
http://eligius.st/~wizkid057/newstats/pushtxn.php
https://blockchain.info/pushtx
https://insight.bitpay.com/tx/send

Note that some of these websites will refuse to broadcast your raw transaction if they are still aware of your currently existing transaction.  In that case you'll want to save a copy of this new signed raw transaction, shut down your wallet for a few days (so it doesn't re-broadcast the current transaction), and then re-try pasting the raw transaction to the websites once they've forgotten your current transaction.

[imnotarobot]

Looking at the raw transaction it appears you're attempting to spend the 7.43755195 BTC output that was received in transactionID cccfb24951f68a56e3dd32771f7e70f08fd5e11c550ef127b72ae02d914417e8 on April 2, 2013. This input into your new transaction provides 7.43755195 BTC of value for your transaction to re-assign in new outputs.

It looks like your transaction is probably sending 2.909 BTC to 1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv in one output while sending the remaining 4.52855195 BTC back into your wallet at the new internal address of 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67 in a second output.  As such (since 4.52855195 + 2.909 = 7.43755195) there are no bitcoins remaining for the transaction fee.

If I've understood correctly what you are trying to do (send 2.909 BTC to 1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv while keeping control of the rest of the bitcoins, then you can just reduce the value of the output to 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67 by the amount that you want the transaction fee to be.

The following command (if copied and pasted into your Bitcoin Core console) will create a raw transaction that spends the exact same 7.43755195 BTC output, and still sends 2.909 BTC to 1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv, but only sends 4.52835195 BTC back into your wallet at 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67.  The remaining unaccounted for 0.0002 BTC will become a transaction fee.

Code:

createrawtransaction '[{"txid":"cccfb24951f68a56e3dd32771f7e70f08fd5e11c550ef127b72ae02d914417e8","vout":0}]' '{"1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv":2.90900000,"16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67":4.52835195}'

That command re-uses as an input the exact same 7.43755195 BTC input from cccfb24951f68a56e3dd32771f7e70f08fd5e11c550ef127b72ae02d914417e8 as your current transaction uses.  That means that ONLY one of these two transactions can ever confirm.  If your current transaction confirms soon, then this new transaction will become immediately invalid and the entire network will reject it.  If this new transaction confirms, then your current transaction will become immediately invalid and the entire network will reject it.  As such, you won't run the risk of accidentally transferring 5.818 BTC to 1LpZAeJthyUueRwZMjv7K471L7Vyg4Abqv (2.909 BTC twice).

I can understand if you might be concerned that I could be misleading you. That's why I've posted publicly here instead of sending a PM. You can wait and see if any other knowledgable people see this post and warn you not to do it.

The result of the command should be:

0100000001e81744912de02ab727f10e551ce1d58ff0707e1f7732dde3568af65149b2cfcc00000 00000ffffffff0220c85611000000001976a914d968ca8825d27c3e20e5653a9785485160997268 88ac7bb7fd1a000000001976a9140114f4219ee59e426ff608df1dd4b4abc378298488ac0000000 0

You can then use the following command in the console to sign the transaction so that it is ready for broadcast:

Code:

signrawtransaction 0100000001e81744912de02ab727f10e551ce1d58ff0707e1f7732dde3568af65149b2cfcc0000000000ffffffff0220c85611000000001976a914d968ca8825d27c3e20e5653a978548516099726888ac7bb7fd1a000000001976a9140114f4219ee59e426ff608df1dd4b4abc378298488ac00000000

or if you prefer not to trust the raw transaction that I've created for you, then you can replace that hex string with the results you get when you run the createrawtransaction command yourself.

You can then copy the hex output from the signrawtransaction command and paste it into the forms at the following websites to broadcast it to the network:

https://btc.blockr.io/tx/push
https://blockexplorer.com/tx/send
https://live.blockcypher.com/btc/pushtx/
https://coinb.in/#broadcast
http://eligius.st/~wizkid057/newstats/pushtxn.php
https://blockchain.info/pushtx
https://insight.bitpay.com/tx/send

Note that some of these websites will refuse to broadcast your raw transaction if they are still aware of your currently existing transaction.  In that case you'll want to save a copy of this new signed raw transaction, shut down your wallet for a few days (so it doesn't re-broadcast the current transaction), and then re-try pasting the raw transaction to the websites once they've forgotten your current transaction.

Danny,

thank you for all of your help, very much appreciated.

i waited to see if anyone questioned your advice and being as it has been a day and a half and no one has, i am assuming this is good advice.

i looked at what you did with the code and believe i understand what you did and is going on there, it makes good sense.

one final question if you do not mind..

is there a way to verify that the address: 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67 is indeed an internal address created by my wallet? i don't see it in my previously used addresses and i don't want to send it to someone else, obviously.

 

[cr1776]

To verify if that address is one of your's, in the console you can

dumpprivkey theaddress

You should get back the private key. If not, something is wrong.  And DH did give good advice, as usual.



 

[imnotarobot]

hey cr1776,

thanks for the response.

i tried to do what you said, i entered:

Code:

dumpprivkey 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67

in the Console,  but it came back with:
Error: Please enter the wallet passphrase with walletpassphrase first. (code -13)

what is this? my wallet password? i tried
 

Code:

walletpassphrase <passphrase>

and it didn't work. i got:
Error: Error parsing JSON:it

what am i doing wrong?

[cr1776]

hey cr1776,

thanks for the response.

i tried to do what you said, i entered:

Code:

dumpprivkey 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67

in the Console,  but it came back with:
Error: Please enter the wallet passphrase with walletpassphrase first. (code -13)

what is this? my wallet password? i tried
 

Code:

walletpassphrase <passphrase>

and it didn't work. i got:
Error: Error parsing JSON:it

what am i doing wrong?

Yeah, you'll have to unlock it first. You didn't put it in <> did you? 

https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list

[DannyHamilton]

As cr1776 mentioned, the <> is not supposed to be used.

Also, to limit your exposure, you can put a timeout on the unlocking by adding a number of seconds after the passphrase.

So, if your wallet password was ThisIsNotMyRealPassword

And you wanted to unlock your wallet for 60 seconds while you entered the dumpprivkey command, you would enter the following in the console:

Code:

walletpassphrase ThisIsNotMyRealPassword 60

Also note that you can change the createrawtransaction command that I provided and replace the 16in5R5UH4LkbA9hhvU2z6ZGYHPxyve67 address with some other address that you feel more confident about if you like.

You don't see it in your previously used addresses because it is an address the wallet used to send back the excess value provided by the output that was being spent. (Much like the $5.26 in "change" that you would get back if you paid for a $14.74 item with a $20 bill) The user interface doesn't typically show you the internal addresses that the wallet uses for "change", but there isn't anything special about those addresses.  You can send the "change" from your transaction to any address you like.

[imnotarobot]

Okay...

i had an issue with the walletpassphase. no matter what i did, i kept getting an error. so i thought maybe it doesn't like the spaces in my current passphrase, so that gave me pause to think that if it didn't like it in the concole, would i even be able to change the passphrase as it needed to be entered to change it. i changed it with no worries. then went back to the console and it worked, so perhaps it was that it did not like the spaces.

anyhoo, i have rebroadcast and hope my next report here will be that the transaction was completed.

[imnotarobot]

quick update.

this appears to have worked.

the initial transaction now has an 'x' (which when hovered over with the cursor says conflicted) in the 'transaction status' box instead of the'?' that previously existed. now there is a new transaction with a 'clock' in the 'transaction status' box with it already having 1 confirmation.



 

[achow101]

Okay...

i had an issue with the walletpassphase. no matter what i did, i kept getting an error. so i thought maybe it doesn't like the spaces in my current passphrase, so that gave me pause to think that if it didn't like it in the concole, would i even be able to change the passphrase as it needed to be entered to change it. i changed it with no worries. then went back to the console and it worked, so perhaps it was that it did not like the spaces.

No, the console will not like spaces. Each parameter is space separated, so it will think whatever you type is is multiple parameters. Rather what you should have done is put quotes (") around your password. That should have fixed the problem.

quick update.

this appears to have worked.

the initial transaction now has an 'x' (which when hovered over with the cursor says conflicted) in the 'transaction status' box instead of the'?' that previously existed. now there is a new transaction with a 'clock' in the 'transaction status' box with it already having 1 confirmation.

Yes. That X means that transaction is conflicted (by your second one). The thing is, it will remain there, so if you want it gone, you will need to use -zapwallettxs

[imnotarobot]

thanks, knightdk.

i should have thought about using " marks. it's all good though, i needed to change it anyways.