For the last and final time, we are not going to relaunch just because some Windows people missed an hour or two of early mining. And it wasn't until like block 443 that the Windows people forked, so they didn't really miss out on the early mining anyway. Furthermore, if we did relaunch, the amount of energy wasted would be absolutely huge compared to the insignificant amount wasted by Windows miners.

Everything in life is a fight over resources. And I'm in exactly the same boat as you, I only have a crappy laptop and a gaming pc. Granted the gaming setup is a bit of a beast, but since I can only CPU mine there's not much point trying with such a high difficulty. I either have to rent out mining rigs or buy XCN directly. In fact I'm looking to buy about 1 or 2 thousand XCN if anyone is selling. I might try out Bter, looks like a decent exchange. And for those people who think there's something suspicious about Bter adding XCN to their exchange, I didn't even know about it until just now. I've been asleep for the last 9 hours and when I returned I had multiple PM's from Bter saying they had added XCN to their exchange.

If you downloaded it near the start of the launch then it's probably the old version. Just download it again to be safe.

The diff is now at 28k, that's probably to be expected.

Using the broken Windows build I assume?

Looks like you were mining on the wrong chain. Using the first Windows build?

Yes that is the correct chain.

Well if I remember correctly you got it working on Win8.1 in the test thread after you downloaded the dll's. You're not still using the -testnet flag are you? I'm sure if you mess around with it a bit you'll get it to work.

EDIT: the other thing I would recommend trying is redownloading the .exe file and see if that helps.

Some more nodes posted by catia on IRC:

54.210.111.104
54.91.54.222
54.237.164.185
122.192.189.208
83.212.102.224
54.81.74.247
54.234.32.117
54.204.209.48
183.93.235.186

Btw folks it looks like some of that recent weirdness could be due to someone attempting to clone Cryptonite, because there appears to be blocks from an unknown genesis point floating around. It doesn't seem to pose any threat to the current chain, but it might cause weird issues when syncing.

Well I'm not sure what else you could try, it might be a Win8 related issue, maybe try a different OS if possible.

If you're implying that we have an unreleased GPU miner I can assure you we don't. It's possible someone has created one, but it's highly improbable. We will try our best to have a GPU miner available before anyone else creates their own private GPU miner, but I can't guarantee anything. There seems to be a ridiculously huge number of nodes connecting to the main seed node, it can hardly keep up with it, so the network is probably at a natural hash rate for this many miners.

Yes that is the correct chain. The difficulty should be about 23k and the block count should be about 1575.

Sounds like you might still be running the old Windows binary or something. Did you read that the first Windows binary was broken? We released a fixed version which you can download from here.

You might need to delete the Cryptonite folder in /Users/UserName/AppData/Roaming/

There are currently 1500 blocks. And there was anything but an instamine. We posted the announcement literally seconds after we started mining and the difficulty algorithm adjusted so quickly that it become very hard for me to solo mine after like 5 minutes.

Yes it is quite strange, what version did you download? If you could paste your debug.log file on pastebin or something it could be helpful.

It's a 64bit binary so if you're using a 32bit system it wont work. Sounds like you are using a 64bit OS though, you should have two Program Files folders. You don't want to use the folder with x86 at the end, you want the one without it, just Program Files.

The seed nodes appear to be getting quite overloaded, the network is growing much faster than we imagined. It's a fairly common issue with new altcoins, but you can manually add peers to your conf file to help it sync using addnode. Someone posted this link before with a bunch of IP's: http://pastebin.com/6R0nvvnj

And btw the correct block height is about 1500.

Lol no that is definitely wrong. Where did you get that value from? Are you still getting that error about the secret chain attack? It doesn't look like any other nodes are getting that error. Seems like your node is behaving pretty weirdly, maybe try resyncing or something.

See this wiki page:
http://cryptonite.info/wiki/index.php?title=Cryptonite_API

To start solo mining you need to use the setgenerate command.

No this is the real thing. Testing is over.