Do you mean abandontransaction?
In that case, if you didn't see an error message, i wouldn't worry about it anymore.. You abandoned the transaction, that's all you needed to do
Yes, abandontransaction. OK, so everything is fine. Thank you for help.
Topic: Transaction still unconfirmed after 2 weeks (Read 1577 times)
Do you mean abandontransaction?
In that case, if you didn't see an error message, i wouldn't worry about it anymore.. You abandoned the transaction, that's all you needed to do
Yes, abandontransaction. OK, so everything is fine. Thank you for help.
I'm glad to see you got it solved, however, there is one thing i wanted to clarify:
walletbroadcast => Make the wallet broadcast transactions
zapwallettxes => Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup
source: https://en.bitcoin.it/wiki/Running_Bitcoin
There is a big difference between the two: the option you used just makes sure your wallet doesn't rebroadcast your transaction. The second option (zapwallettxes) makes sure the transaction is deleted from your wallet, so it'll never be rebroadcasted (since your wallet simply deleted the transaction).
OH! Well, the destination address is my account at a BTC broker's, but this could even cause trouble.
Question: So as I used walletbroadcast=0 and RPC aborttransaction $txid, should I restart BC core once with -zapwallettxes?
Do you mean abandontransaction?
In that case, if you didn't see an error message, i wouldn't worry about it anymore.. You abandoned the transaction, that's all you needed to do
I'm glad to see you got it solved, however, there is one thing i wanted to clarify:
walletbroadcast => Make the wallet broadcast transactions
zapwallettxes => Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup
source: https://en.bitcoin.it/wiki/Running_Bitcoin
There is a big difference between the two: the option you used just makes sure your wallet doesn't rebroadcast your transaction. The second option (zapwallettxes) makes sure the transaction is deleted from your wallet, so it'll never be rebroadcasted (since your wallet simply deleted the transaction).
OH! Well, the destination address is my account at a BTC broker's, but this could even cause trouble.
Question: So as I used walletbroadcast=0 and RPC aborttransaction $txid, should I restart BC core once with -zapwallettxes?
If you only have 1 unconfirmed transaction, they're equal in security... The main differences are that abandontransaction is a command you can run from the cli or the debug window while your client is running and it only abandons the 1 unconfirmed transaction you enter as a parameters. -zapwallettxes is a startup parameter, it can only be issued when starting the client, and it usually takes a lot longer to do this compared to using abandontransaction. Zapwallettxes also removes ALL unconfirmed transactions you have broadcasted...
On the other hand, abandontransaction doesn't always work (you get an error message that the transaction cannot be abandoned). In this case, you'll have to use the zapwallettxes parameter (i'm to lazy to look up the spelling, but i think -zapwallettxes might be misspelled).
BTW: next time you have a problem, it might be better to start your own topic, replying to a 6 month old topic is usually considered necroposting, eventough you have a valid question (just a tip)
I am sorry, using -zapwallettxes is not the primary solution. Before trying this workaround you should restart bitcoin-qt with -walletbroadcast=0 and try again. This way it worked in my case.
Thanks for the quick response and sorry for necroposting, I didn't want to ask a question to a similar topic again.
I'm glad to see you got it solved, however, there is one thing i wanted to clarify:
walletbroadcast => Make the wallet broadcast transactions
zapwallettxes => Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup
source: https://en.bitcoin.it/wiki/Running_Bitcoin
There is a big difference between the two: the option you used just makes sure your wallet doesn't rebroadcast your transaction. The second option (zapwallettxes) makes sure the transaction is deleted from your wallet, so it'll never be rebroadcasted (since your wallet simply deleted the transaction).
If you only have 1 unconfirmed transaction, they're equal in security... The main differences are that abandontransaction is a command you can run from the cli or the debug window while your client is running and it only abandons the 1 unconfirmed transaction you enter as a parameters. -zapwallettxes is a startup parameter, it can only be issued when starting the client, and it usually takes a lot longer to do this compared to using abandontransaction. Zapwallettxes also removes ALL unconfirmed transactions you have broadcasted...
On the other hand, abandontransaction doesn't always work (you get an error message that the transaction cannot be abandoned). In this case, you'll have to use the zapwallettxes parameter (i'm to lazy to look up the spelling, but i think -zapwallettxes might be misspelled).
BTW: next time you have a problem, it might be better to start your own topic, replying to a 6 month old topic is usually considered necroposting, eventough you have a valid question (just a tip)
I am sorry, using -zapwallettxes is not the primary solution. Before trying this workaround you should restart bitcoin-qt with -walletbroadcast=0 and try again. This way it worked in my case.
Thanks for the quick response and sorry for necroposting, I didn't want to ask a question to a similar topic again.
Which wallet are you using? For example, bitcoin core keeps rebroadcating a transaction untill you start it with -zapwallettxes or issue an abandontransaction from the cli
Sorry to interrupt, because I have the same problem. I am using Bitcoin Core v0.15. So I have to restart it with -zapwallettxes? Or is it better just to abandon the transaction? Which of these two options shouls I take? (Note: I'd like to use the most secure way)
Thanks for help.
Regards
Christian
If you only have 1 unconfirmed transaction, they're equal in security... The main differences are that abandontransaction is a command you can run from the cli or the debug window while your client is running and it only abandons the 1 unconfirmed transaction you enter as a parameters. -zapwallettxes is a startup parameter, it can only be issued when starting the client, and it usually takes a lot longer to do this compared to using abandontransaction. Zapwallettxes also removes ALL unconfirmed transactions you have broadcasted...
On the other hand, abandontransaction doesn't always work (you get an error message that the transaction cannot be abandoned). In this case, you'll have to use the zapwallettxes parameter (i'm to lazy to look up the spelling, but i think -zapwallettxes might be misspelled).
BTW: next time you have a problem, it might be better to start your own topic, replying to a 6 month old topic is usually considered necroposting, eventough you have a valid question (just a tip)
Which wallet are you using? For example, bitcoin core keeps rebroadcating a transaction untill you start it with -zapwallettxes or issue an abandontransaction from the cli
Sorry to interrupt, because I have the same problem. I am using Bitcoin Core v0.15. So I have to restart it with -zapwallettxes? Or is it better just to abandon the transaction? Which of these two options shouls I take? (Note: I'd like to use the most secure way)
Thanks for help.
Regards
Christian
got same issue as TS. I had transaction created on 05.19 via multibit with small fee. But it was updated yesterday to a new date.
Multibit HD.
https://blockchain.info/tx-index/047c16f61949c36bf586476e1f59f5e1bf89553dceeb10bbf2eada926f88c748
btc.com also says it is double-spend. I would do it if I could but multibit doesn't allow to export private keys...
Any idea how do I cancel that transation and get my btc back?
i think you can't cancel a transaction once it was broadcasted since it was double spent and it has a low fee (14sats per byte) i suggest that wait until 3 days for the mempool drops your transaction and the coins will automatically return to your wallet. hope this helpsMultibit HD.
https://blockchain.info/tx-index/047c16f61949c36bf586476e1f59f5e1bf89553dceeb10bbf2eada926f88c748
btc.com also says it is double-spend. I would do it if I could but multibit doesn't allow to export private keys...
Any idea how do I cancel that transation and get my btc back?
regards
lighpulsar07
got same issue as TS. I had transaction created on 05.19 via multibit with small fee. But it was updated yesterday to a new date.
Multibit HD.
https://blockchain.info/tx-index/047c16f61949c36bf586476e1f59f5e1bf89553dceeb10bbf2eada926f88c748
btc.com also says it is double-spend. I would do it if I could but multibit doesn't allow to export private keys...
Any idea how do I cancel that transation and get my btc back?
Multibit HD.
https://blockchain.info/tx-index/047c16f61949c36bf586476e1f59f5e1bf89553dceeb10bbf2eada926f88c748
btc.com also says it is double-spend. I would do it if I could but multibit doesn't allow to export private keys...
Any idea how do I cancel that transation and get my btc back?
Maybe your wallet is trying to rebroadcast... https://live.blockcypher.com/btc/tx/12f0ecc32a70cd5c85115a6906d0cc09bef149e1c13c8a0887017fedcd370457/
Says it was received less than 1 minute ago as of 2017-05-19 0850 UTC and was relayed by: 78.106.145.186:8333 which is located in Russia apparently...
Says it was received less than 1 minute ago as of 2017-05-19 0850 UTC and was relayed by: 78.106.145.186:8333 which is located in Russia apparently...
This was actually my first idear to... But then the OP told that he's using multibit HD, and AFAIK, that wallet doesn't rebroadcast transactions automatically (or am i missing something?)
To be perfectly honest: i did try to search if multibit HD automatically rebroadcasts, but since i didn't find anything related to this topic, i just assumed it didn't... But i can be wrong on this
Maybe your wallet is trying to rebroadcast... https://live.blockcypher.com/btc/tx/12f0ecc32a70cd5c85115a6906d0cc09bef149e1c13c8a0887017fedcd370457/
Says it was received less than 1 minute ago as of 2017-05-19 0850 UTC and was relayed by: 78.106.145.186:8333 which is located in Russia apparently...
Says it was received less than 1 minute ago as of 2017-05-19 0850 UTC and was relayed by: 78.106.145.186:8333 which is located in Russia apparently...
accelerated
I'm scared I will never get my money back 
For some reason this is showing up as a double spend. Did you double spend these coins?
I'm scared I will never get my money back
Is it possible for someone to help the transaction being confirmed in exchange of some btc ?
Yes. btc.com has a paid accelerator service. You can find it here: https://pushtx.btc.com/#/
I think they overcharge us though. I would wait till the end and if the coins come back, i would send them again with a proper fee if i were you.
That service can save your life in an emergency situation though.
I put his transaction ID (12f0ecc32a70cd5c85115a6906d0cc09bef149e1c13c8a0887017fedcd370457) into the site you mentioned (https://pushtx.btc.com/#/) just to see what the fee would be and I got:
Quote
This is a double-spent tx, unavailable for acceleration
So something funny is going on with this transaction.
Is it possible for someone to help the transaction being confirmed in exchange of some btc ?
Yes. btc.com has a paid accelerator service. You can find it here: https://pushtx.btc.com/#/
I think they overcharge us though. I would wait till the end and if the coins come back, i would send them again with a proper fee if i were you.
That service can save your life in an emergency situation though.
Is it possible for someone to help the transaction being confirmed in exchange of some btc ?
Thank you for your replies guys. When I first made the transaction it also wasn't showed in all blockchain explorer at the begining. It seems like it the confirmation process restarted again yesterday. The question is Why ? My btcs aren't supposed to come back to my wallet after the transaction stays unconfirmed fo a long time ??
What do you think I should now do guys ?
What do you think I should now do guys ?
I'm using Multibit HD. I tried to repair the wallet but nothing better came out of it.
blockchain.info says their node received the transaction about ~24hrs ago, so somebody must be rebroadcasting it... Strange.
My node doesn't have this tx in it's mempool, so i either didn't received it, or i received it +10 days ago
I'm using Multibit HD. I tried to repair the wallet but nothing better came out of it.
blockchain.info says their node received the transaction about ~24hrs ago, so somebody must be rebroadcasting it... Strange.
My node doesn't have this tx in it's mempool, so i either didn't received it, or i received it +10 days ago
Code:
bitcoin-cli getmempoolentry 12f0ecc32a70cd5c85115a6906d0cc09bef149e1c13c8a0887017fedcd370457
error code: -5
error message:
Transaction not in mempool
Jump to: