Title: Transaction ID not found after using zapwallettxes Post by: dware on May 04, 2017, 12:46:23 PM Hello,
Please help me understand the following issue: 1. I made 3 transactions yesterday, their IDs are (starting from the last one): Code: 5567be46f8dccbbe4c775c58768745e87e8cfb5ec2b336436700d389afb737ce 2. This morning there still were no confirmations on any tx, so I restarted Bitcoin Core with -zapwallettxes, and after rescanning the unconfirmed transactions were not visible anymore. 3. I made a new tx with the highest recommended fee possible in Bitcoin Core, the ID is Code: c1c357cd554b5b288f08c959464c33c458fe1de727c3ad8f5a0421e34565bafa 4. After that the two top transactions from p. 1 returned, so now I have (starting from the last one): Code: 2456fe35add543962d34548442f8f80b36548769d2092d22be514e17fc01f8fb 5. Now I'm unable to find the tx created at p. 3 Code: c1c357cd554b5b288f08c959464c33c458fe1de727c3ad8f5a0421e34565bafa 6. Here is how the tx looks in my Bitcoin Core Code: Status: 0/unconfirmed, in memory pool, broadcast through 8 nodes Can you advise anything guys? Tell me that I'm not losing my BTC... :) Title: Re: Transaction ID not found after using zapwallettxes Post by: achow101 on May 04, 2017, 01:36:47 PM Since you used zapwallettxes, your transaction made at p.3 is a double spend. The transaction fee for your other transactions is not so low that they are rejected from many nodes' mempools. Because of that, your p.3 transaction is rejected by nearly all nodes since it is considered a double spend. Thus that transaction did not propagate well so you won't find it on block explorers.
Your Bitcoin is safe. Bitcoin does not just "disappear". It will either go to who you sent it to (i.e. the transaction will confirm) or it will not and you can spend it again (i.e. the transactions are dropped from the network after a while). Title: Re: Transaction ID not found after using zapwallettxes Post by: dware on May 04, 2017, 02:09:19 PM Thanks for your answer, achow101.
So as I understand, c1c is actually rejected and 34c is actually considered as my first tx. And my BTC should be confirmed or returned in some time (3 days?). Will my Transactions tab synchronize automatically later? because now I have c1c instead of 34c there. Also, I sent more BTC with c1c than 34c, and my wallet is still showing balance minus the c1c amount. Title: Re: Transaction ID not found after using zapwallettxes Post by: achow101 on May 04, 2017, 02:17:12 PM Thanks for your answer, achow101. Yes. 34c is the original transaction as considered by every other node so c1c is rejected as a double spend of 34c.So as I understand, c1c is actually rejected and 34c is actually considered as my first tx. And my BTC should be confirmed or returned in some time (3 days?). Will my Transactions tab synchronize automatically later? because now I have c1c instead of 34c there. Yes. The blockchain is what determines that a transaction is the "real" one. Once one transaction confirms, then your wallet will automatically update to fit what the blockchain says.Also, I sent more BTC with c1c than 34c, and my wallet is still showing balance minus the c1c amount. Since you did zapwallettxes, you removed 34c from your wallet before you sent c1c. Thus your wallet saw c1c first and uses that as the "real" transaction and not 34c which is what all other nodes will think is the "real" one. Once one of those transactions confirm, your wallet will automatically update to fit what the blockchain says.Title: Re: Transaction ID not found after using zapwallettxes Post by: dware on May 04, 2017, 02:45:37 PM So why did I use -zapwallettxes at all? :)
I followed an article saying that pp. 2-3 is what you need when you want to cancel unconfirmed / re-send with a higher fee. Why didn't it work in my case? Is it because 34c fee is not too low to be rejected and a lot of nodes "cached" it to their mempool? Title: Re: Transaction ID not found after using zapwallettxes Post by: DannyHamilton on May 04, 2017, 03:08:41 PM Some things to be aware of to help clarify what happened...
Title: Re: Transaction ID not found after using zapwallettxes Post by: DannyHamilton on May 04, 2017, 03:15:27 PM So why did I use -zapwallettxes at all? :) So that YOUR wallet would forget the original transactions. Your wallet would not allow you to create a new replacement transaction as long as it was aware of the old transaction. I followed an article saying that pp. 2-3 is what you need when you want to cancel unconfirmed / re-send with a higher fee. It is impossible to "cancel" a transaction in bitcoin. Once you send a transaction, you no longer have any control over what other nodes and miners will choose to do with it. The best you can do is broadcast a competing transaction, and provide an incentive for it to hopefully be accepted into the blockchain. Whichever of the two transactions makes it into the blockchain will become the "real" transaction, and any competing transaction will then become invalid. Why didn't it work in my case? Is it because 34c fee is not too low to be rejected and a lot of nodes "cached" it to their mempool? It did work. You did create a competing transaction. Your wallet is aware of it. Since you are using Bitcoin Core, it will continue to re-broadcast this new competing transaction (as long as it is running and connected to peers) until one of the following:
If your original transaction remains unconfirmed, eventually peer nodes will begin to forget about it. Then when your wallet re-broadcasts the competing transaction, they will add the new transaction to their memory pool and will attempt to relay it to their peers. Title: Re: Transaction ID not found after using zapwallettxes Post by: dware on May 04, 2017, 03:53:39 PM It appears that c1c beat up 34c, now I have the other two, 556 and 245, unconfirmed only. Thanks achow101 and DannyHamilton, your information was very interesting and useful for me. |