Topic: Previously confirmed transactions now unconfirmed - page 2. (Read 2756 times)
You did try "-rescan" right?
It will be fixed by the time you wake up 
Automagically....
Automagically.... It wasn't.
Maybe the downloaded blocks didn't carry with confirmed blocks? It will be fixed by the time you wake up Automagically....
Automagically....
Yes to the first question, no to the second.
I'll have to deal with this tomorrow. Bedtime now.
I'll have to deal with this tomorrow. Bedtime now.
Blah. Using all 8 connect switches and I'm only getting 5 connections.
This echos the results of another user who did the same using the first eight of the published fallback nodes. Is this what you did? This means that three of the eight fallback nodes have been knocked of the Internet.
Are teh connections that you are getting, are they working?
Blah. Using all 8 connect switches and I'm only getting 5 connections.
Doesn't appear to be working. Should I just keep adding more nodes?
Use -noirc and -connect=ipaddress instead. This will connect you to only the ip address of the node you specify and not announce your address to the irc bootstrapping channel. You can use up to 8 -connect= switches.
Doesn't appear to be working. Should I just keep adding more nodes?
Try restarting the client with the -addnode= switch and an IP address of one of the fallback nodes. I suspect there is an attack underway against the p2p network itself, or the IRC bootstrapping method. Your not the first to mention weirdness.
Any clues why this might be?
What has changed since then is that I uninstalled Bitcoin and reinstalled it in a new location (USB drive). But Bitcoin has been running for several minutes since then without a single (re)confirmation, and only 1 connection. What gives?
What has changed since then is that I uninstalled Bitcoin and reinstalled it in a new location (USB drive). But Bitcoin has been running for several minutes since then without a single (re)confirmation, and only 1 connection. What gives?
Jump to: