Nope - not mining
re: downloading all blocks... that'll be why. My client says "133901", Bitcoin charts says 135218.
It claims to have one connection - oop... now it's zero... now it's one again. The 133901 appears not to change... no... I lie, after about 5 minutes, it's gone up to 133902
Now it has two connections and it's gone up to 133903.
So... 135218-133903=1315 ... at about 12 blocks downloaded an hour - that comes to about 4.5 days... about the time it would take to send money in cash, by plane.
Down to zero connections again.
I've got client version .3.17 - do I need to upgrade it or something?
re: downloading all blocks... that'll be why. My client says "133901", Bitcoin charts says 135218.
It claims to have one connection - oop... now it's zero... now it's one again. The 133901 appears not to change... no... I lie, after about 5 minutes, it's gone up to 133902
Now it has two connections and it's gone up to 133903.
So... 135218-133903=1315 ... at about 12 blocks downloaded an hour - that comes to about 4.5 days... about the time it would take to send money in cash, by plane.
Down to zero connections again.
I've got client version .3.17 - do I need to upgrade it or something?
All right, I know what is happening, as I have had it happen to me. Restart your client using the -rescan, -noirc and -addnode= switches. The addnode= switch needs the IP address of a fallback node just after the equal sign. Use two or more fallback nodes. The client should then rescan the blockchain and then not announce it's presence on the IRC channel, but it will get more nodes from the fallback nodes, and other nodes should do the same for you.
