difficulty should not have been started so low ugh

We're at difficulty 2 (or whatever the next one was) now

i0.btcguild.com : [5], 84 bytes, 189 ms (189 avg, 0% loss)
i0.btcguild.com : [6], 84 bytes, 189 ms (189 avg, 0% loss)
^C
i0.btcguild.com : xmt/rcv/%loss = 7/7/0%, min/avg/max = 189/189/189
nmc@nmcpc:~/i0coin$

At 189 ms I'll never get a block...

110 share, none accepted

holy shit did I just get decimated.  All my blocks disappeared.

that sucks!!!!!!!!!!

I was expecting some to disappear but I guess i0guild took dominance over the chain and as a result, poof.  Oh well.  Interesting to say the least.

Some people are reporting the same thing.  I saw a few of my blocks disappear too, even ones that had confirmations.  But now that I think about it, it didn't make sense that I had mined 80 blocks out of 240 so far lol

Crap, I need some IP address to bootstrap, since it looks like I got the IRC k-line too and I'm dead in the water with 2 connections...

Post some IPs from the IRC channel or your firewall connection log please!

Or if you have more than 8 connections, upload your addr.dat file to mediafire.com (it has the ip addresses of other network clients) and share or pm please!

stop i0coind then run "i0coin.exe -server" instead


For all current bitcoin/forks, you can start the client with the -server flag instead. This will allow you to solo mine and use the GUI client at the same time.

I'm just watching because I was curious to see how the network/protocol would behave in this situation.

It looks like from look at btcguild's block page, they believe they're finding ALL the blocks from their perspective. In periods where they're finding >50% of the blocks, they're effectively coming up with their own block chain where they're the winner to everything. When they don't manage to muscle out everyone else, they end up losing their whole forked chain.

Is this right? Anyone with more experience with how the block collision scheme works could probably answer this better, but it's kinda interesting to watch the debug log showing the battles.