Quote from: georgem on April 25, 2016, 07:41:29 PM

Quote from: spready on April 25, 2016, 07:33:13 PM

Quote from: georgem on April 25, 2016, 07:27:06 PM

yeah, I think we already have atleast 2 forks because of low participation (I've seen one stuck at block 500, and the other at 782), lol

Wait guys, I need to create a new blockchain and spread it over 2 servers and hardcode them into the wallet, or else this might repeat itself.

I might also add a checkpoint or two.

Please stop mining for now.

PS: It's also cool to learn about such things in realworld experiments, so thanks alot to whoever spends a few CPU cycles for this. Awesome!

Shouldn't the clients just use the longest chain they find so the fork wouldn't matter? Just asking I really don't know Huh

Ofcourse, ofcourse.

No, forget everything I said, I need to use my brain more.

It's just a stupid error! Roll Eyes

There was still an old checkpoint set in the code that expected block nr. 500 to be a certain hash. (goes back to mr. spread)
I forgot to remove those checkpoints, aahrg! And that's what created this mess.

Wait, I'll look over everything once more, and restart a new chain.

Ok cool, I look forward to playing with the voting tomorrow again