Also the software should not spend unconfirmed outputs, that's a bad idea.
Topic: Has the double spend, never confirming transactions bug been fixed? (Read 1096 times)
July 01, 2014, 03:52:00 PM
That's the problem. There was a problem where a double spend would remain in the wallet and the wallet would try to spend from unconfirmed double spends, so you would try to make transactions but they would end up unconfirmed.
Using -salvagewallet is one way to fix this, but it shouldn't be a problem in the first place. I'm wondering if it is fixed?
Also the software should not spend unconfirmed outputs, that's a bad idea.
Using -salvagewallet is one way to fix this, but it shouldn't be a problem in the first place. I'm wondering if it is fixed?
Also the software should not spend unconfirmed outputs, that's a bad idea.
July 01, 2014, 03:23:36 PM
I'm not sure what you're talking about precisely— obviously double spends will never confirm, so thats not going to be "resolved".
July 01, 2014, 02:52:33 PM
I know that in at least earlier versions of bitcoins there was a significant problem with transactions that would never confirm due to double spend: https://bitcointalksearch.org/topic/help-transactions-not-confirming-4-btc-bounty-85689
Has this problem been resolved? If so, which version? And if anyone could point to the particular code/commit that fixes it, I would be most grateful.
Thanks,
Matthew
Has this problem been resolved? If so, which version? And if anyone could point to the particular code/commit that fixes it, I would be most grateful.
Thanks,
Matthew
Jump to: