Never confirmed transaction, how to get it back in the wallet ?

[Alesia]

I didn't want to hijack I just thought it would be easier since it's the same problem.

Anyway thanks for your time and reply I did : abandontransaction 1d150ad498c23524dcb60198d41676f3b44060fc37ac2d7e76f8625be4e5562c-000

But I had : Transaction not eligible for abandonment (code -5)

Remove the -000 part, it isn't actually part of the transaction ID.

Unfortunately same thing and what is weird is that when I did the transaction on the 16th it went on blockchain until this morning (but was unconfirmed the whole time). It disappeared and now it's back with the same ID and the 2 good wallets' adresses, only difference the time which is now 23rd at 6pm.

[1714058285]

1714058285

[1714058285]

1714058285

[1714058285]

1714058285

[Alesia]

Any idea ?

[merelcoin]

Any idea ?

Your wallet probably rebroadcasted the transaction, since you were unable to abandon it...
IMHO, you have a couple options:

• fix the issue you have with zapwallettxes (like knightdk said)
• fix the issue you have with abandontransaction (like knightdk said)
• wait untill it's confirmed
• create a double-spend/RBF

The first 2 options are already explained, the third is pretty obvious, the last one shouldn't be to hard, since your tx has 1 input, 1 output and you're using core (so you can easily create raw transactions, sign them, broadcast them)

[Alesia]

Thanks Merelcoin :

- fix the issue you have with zapwallettxes (like knightdk said)
I opened the terminal and did : open /Applications/bitcoin-qt.app --args zapwallettxes
It opened but nothing changed

- fix the issue you have with abandontransaction (like knightdk said) :
I did abandontransaction 1d150ad498c23524dcb60198d41676f3b44060fc37ac2d7e76f8625be4e5562c
But Transaction not eligible for abandonment (code -5) came

- create a double-spend/RBF
I can't since my balance is at 0

[merelcoin]

Thanks Merelcoin :

- fix the issue you have with zapwallettxes (like knightdk said)
I opened the terminal and did : open /Applications/bitcoin-qt.app --args zapwallettxes
It opened but nothing changed

- fix the issue you have with abandontransaction (like knightdk said) :
I did abandontransaction 1d150ad498c23524dcb60198d41676f3b44060fc37ac2d7e76f8625be4e5562c
But Transaction not eligible for abandonment (code -5) came

- create a double-spend/RBF
I can't since my balance is at 0

To be honest, i have no mac to test out the command line arguments. I'm just going on what knightdk said, so it's basically up to you to get it working.
The last option tough, creating a double spend means you re-use the inputs used to create transaction 1d150ad498c23524dcb60198d41676f3b44060fc37ac2d7e76f8625be4e5562c . This means you can create a double spend, even if your wallet shows you have no more inputs to spend, as long as the transaction in which your inputs were used isn't confirmed, you can create a double spend.

In short:
* open your bitcoin-qt, go to the console, use createrawtransaction to generate a raw transaction. Make sure you leave a fee this time!!!
* copy the raw, unsigned transaction, sign it with signrawtransaction
* check the signed transaction with decoderawtransaction or online with tools like this: https://blockchain.info/decode-tx
* broadcast the signed transaction with sendrawtransaction or online tools like https://blockchain.info/pushtx

I can even do the first step for you... I'll update this post in a minute
Here is an unsigned transaction:

Code:

010000000171d708d452d6644f7cda462d5e27f891f0e1f365db85df77d147ead39b114f4b030000001976a9145f73795739fa9f424a293ffb436c83e5afe1402588acffffffff01828deb01000000001976a914a9342f9303c899dfd73ac42095d493fa5431315488ac00000000

Please note that the output is less than your initial transaction since i did add a 0.00015BTC fee, which should be sufficient for a 192 bytes transaction with a current fee of 60 bytes/satoshi


Now:

• verify my unsigned transaction, either in bitcoin core or in https://blockchain.info/decode-tx
• if you're OK with what i did, sign the transaction in your wallet (debugwindow => signrawtransaction 010...8ac00000000)
• verify the signed transaction, either in bitcoin core or in https://blockchain.info/decode-tx
• broadcast with bitcoin core or https://blockchain.info/pushtx

Now, you should have double-spent the inputs, "cancelling" out your original transaction

****Disclaimer****: if i generate transactions for you, it's up to you to doublecheck and verify everything... If you're unsure, ask a second opinion. I'm not liable if i made an error or typo when generating the unsigned transaction

Don't forget: there is always the option of just waiting untill the transaction gets confirmed, or even searching a pool operator on this forum and pay him some satoshi's in order to include your transaction in the next block he/she mines... This is by far the easyest way of solving the problem, and it might be the "cleanest" to

[Alesia]

Thanks a lot for you help !

So I did check the transaction and when I do sign the transaction that comes :

Error: Error parsing JSON:010000000171d708d452d6644f7cda462d5e27f891f0e1f365db85df77d147ead39b114f4b03000 0001976a9145f73795739fa9f424a293ffb436c83e5afe1402588acffffffff01828deb01000000 001976a914a9342f9303c899dfd73ac42095d493fa5431315488ac00000000

I'll try to find a miner on the forum.

[achow101]

Thanks a lot for you help !

So I did check the transaction and when I do sign the transaction that comes :

Error: Error parsing JSON:010000000171d708d452d6644f7cda462d5e27f891f0e1f365db85df77d147ead39b114f4b03000 0001976a9145f73795739fa9f424a293ffb436c83e5afe1402588acffffffff01828deb01000000 001976a914a9342f9303c899dfd73ac42095d493fa5431315488ac00000000

I'll try to find a miner on the forum.

What was the command that you did?

[Alesia]

1) I did : signrawtransaction 010000000171d708d452d6644f7cda462d5e27f891f0e1f365db85df77d147ead39b114f4b03000 0001976a9145f73795739fa9f424a293ffb436c83e5afe1402588acffffffff01828deb01000000 001976a914a9342f9303c899dfd73ac42095d493fa5431315488ac00000000

But said that I need to put my walletpassword first so I did :

2) signrawtransaction (mywalletpassword) 010000000171d708d452d6644f7cda462d5e27f891f0e1f365db85df77d147ead39b114f4b03000 0001976a9145f73795739fa9f424a293ffb436c83e5afe1402588acffffffff01828deb01000000 001976a914a9342f9303c899dfd73ac42095d493fa5431315488ac00000000

I did try (mywalletpassword) sigrawtransaction ... but an other error came

[achow101]

What you need to do are actually 2 commands.

The first is to unlock your wallet with

Code:

walletpassphrase <passphrase> 120

where <passphrase> is your passphrase. The 120 indicates how long your wallet will remain unlocked, in this case 120 seconds (2 minutes). You have 2 minutes to do the next command.

Code:

signrawtransaction 010000000171d708d452d6644f7cda462d5e27f891f0e1f365db85df77d147ead39b114f4b03000 0001976a9145f73795739fa9f424a293ffb436c83e5afe1402588acffffffff01828deb01000000001976a914a9342f9303c899dfd73ac42095d493fa5431315488ac00000000

This will sign the transaction.

[Alesia]

Thanks a lot Knightdk & Merelcoin especially for your patience : I did succeed by using zapwallettxes

The right command on mac is : open /Applications/bitcoin-qt.app --args -zapwallettxes

[Alesia]

So now I double spent it with fees hope it will go through.