Bitcoin Forum
May 03, 2024, 04:58:53 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Has the double spend, never confirming transactions bug been fixed?  (Read 1077 times)
MatthewLM (OP)
Legendary
*
Offline Offline

Activity: 1190
Merit: 1004


View Profile
July 01, 2014, 07:52:33 PM
 #1

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://bitcointalk.org/index.php?topic=85689.0

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
You can see the statistics of your reports to moderators on the "Report to moderator" pages.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714755533
Hero Member
*
Offline Offline

Posts: 1714755533

View Profile Personal Message (Offline)

Ignore
1714755533
Reply with quote  #2

1714755533
Report to moderator
1714755533
Hero Member
*
Offline Offline

Posts: 1714755533

View Profile Personal Message (Offline)

Ignore
1714755533
Reply with quote  #2

1714755533
Report to moderator
1714755533
Hero Member
*
Offline Offline

Posts: 1714755533

View Profile Personal Message (Offline)

Ignore
1714755533
Reply with quote  #2

1714755533
Report to moderator
gmaxwell
Staff
Legendary
*
Offline Offline

Activity: 4158
Merit: 8382



View Profile WWW
July 01, 2014, 08:23:36 PM
 #2

I'm not sure what you're talking about precisely— obviously double spends will never confirm, so thats not going to be "resolved".
MatthewLM (OP)
Legendary
*
Offline Offline

Activity: 1190
Merit: 1004


View Profile
July 01, 2014, 08:52:00 PM
 #3

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.
DannyHamilton
Legendary
*
Offline Offline

Activity: 3388
Merit: 4615



View Profile
July 01, 2014, 09:09:21 PM
 #4

Also the software should not spend unconfirmed outputs, that's a bad idea.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!