Quote from: satoshi on August 16, 2010, 02:16:10 … Of the nodes I’m connected to, more than half are already 0.3.10. … That’s great news! How did you figure that out, though? I was considering writing a client specially tailored to put itself out there and try to get as […]

Of course, this happened right after the difficulty kicked up to 511.7, so all these new “good” blocks will have to contend with that.  And a good chunk of the network grind power is off on the wrong chain, so new blocks may take a lot longer than 10min to […]

Quote from: trebronics on August 16, 2010, 01:02:35 Most people running clients are not reading this message thread. So… Silly questions: 1) How will this continue to affect version 3.8.1 (pre-catastrophe) clients with bad block chain? 2) How will this affect clients that upgrade to 3.8.10 but don’t remove their […]

Quote from: kosovito on August 16, 2010, 00:39:17 I did all steps, now my client is 0.3.10 and it stopped at block 74638. Is all fine? If you still show 74638 blocks then you aren’t connected to any 0.3.10 nodes. For today, try adding these parameters: -addnode=75.158.131.108 -addnode=99.27.237.13 -addnode=68.68.99.14 See […]

Quote from: Ground Loop on August 16, 2010, 00:29:55 Question about fallout: I had a transaction that I submitted after the bad block, using the bad block chain. What is the status of that transaction? From what I can tell, my (updated) sending client wallet shows the deducted amount. Will […]

There are 74643 blocks as I write this. The split is causing some network problems. You should connect your computers to each other with the addnode parameter. For now, can some people running 0.3.10 with static IP who can receive incoming connections post their IP?  Then we can -addnode= them […]

There are 74643 blocks as I write this. The split is causing some network problems. You should connect your computers to each other with the addnode parameter. I suspect there’s some difficulty receiving blocks if all the nodes you’re connected to are 0.3.9 or lower.  We need enough of us […]

Version 0.3.10 patches the block 74638 overflow bug.   http://bitcointalk.org/index.php?topic=823 The Linux version includes tcatm’s 4-way SSE2 SHA-256 that makes generating faster on i5, i7 (with hyperthreading) and AMD CPU’s.  Try the “-4way” switch to enable it and check if it’s faster for you. Download from sourceforge: http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.10/ SHA1 16645ec5fcdb35bc54bc7195309a1a81105242bb […]

Quote from: Joozero on August 15, 2010, 23:32:43 I think that you should add something about this: http://bitcointalk.org/index.php?topic=259.0 There must be a label on the client that show a warning message if needed 🙂 Now everyone have always to check the website, and I think that this is bad. Agree, wanted […]

It’s around 67k. It only took me about 3 minutes to get to the current block. Starting at 67000 is perfect. Yeah, at the moment you’ll stop at 74638.  It should start slowly creeping up as more nodes upgrade and generate. Linux build links below. The Linux version includes tcatm’s […]