Can't help but think there are either some huge cpu farms working this now, or it's being gpu mined now.

Probably a mix of both. I was stuck in "newbie jail" so I couldn't weigh in earlier (this was the first thread I thought worth actually registering to post in). I got a late start, about 8 hours after the coin was released. I commenced mining with 800 servers with 2x Xeon E5450's (rows and rows of IBM BladeCenters) when difficulty was reaching 0.008. Shortly after, I provisioned an additional 760 Amazon c1.xlarge instances, starting when difficulty was reaching 0.020. I shut everything down when difficulty reached 0.1 last night.

Observations, orphan rate was about 20% across all 1560 servers, with an average of ~60 connections (modified outbound connection count in the client). At the time I shut everything down with difficulty at 0.1, I was solving roughly 15% of the blocks. Hash rate on the 2x E5450 servers averaged about 300kH/sec, and the Amazon c1.xlarge instances averaged about 200kH/sec, so I was mining with apprx 392,000kH/sec. Based on that, I estimate the network hash rate was actually about 2,613,333kH/sec at that time. Yeah, I know I could probably calculate a better figure from the block spacing vs. difficulty, but I didn't feel like digging into the source to determine the exact relationship between hash rate, difficulty and block solving rate. And I know from trying to estimate block solving rate with litecoinpool's calculator that Yacoin's difficulty calculation differs significantly from LTC. It's entirely possible that a large number of people also had the same bright idea to spin up a huge number of Amazon EC2 instances and that could possibly account for the hash rate, but I suspect the reality is that GPU farms were crunching Yacoin based on my observations. Either that, or Amazon was the party that profited the most from Yacoin (so far). :-)

Just for kicks, I fired 100 servers back up a bit ago to mine for a while starting when difficulty was 0.3, just to see how things compare. I see 0% orphan rate now over the last couple hours and I'm definitely still solving blocks..

Quote

People trying linux for the first time, you need to run this command before you can make it with QTcreator

I really like that people here were all raving about the lack of a premine. Apparently you've all been had if you've been running the Windows binaries of the program that were released at launch, because my Linux binaries are about 10x faster. OP on linux probably had 10,000 blocks before anyone else.

Good call though for OP, release a Windows version that 95% of people on here will use that mines 10 times as slow, and it doesn't look like you've got an actual premine but you yourself are mining an order of magnitude faster than everyone else. He'll probably be walking away with bags full of money.

tl;dr pretty much everyone running the Windows binaries from the onset was screwed.

Also adding the addnode part from the first post on the official thread limited my connections to 8, and I didn't solve any blocks or get above 8 connections until I removed that code (after wasting 8 hours).

Also adding the addnode part from the first post on the official thread limited my connections to 8, and I didn't solve any blocks or get above 8 connections until I removed that code (after wasting 8 hours).

tl;dr pretty much everyone running the Windows binaries from the onset was screwed.

Makes sense now you've collated those posts.. Feel foolish as I was one of those defending the lack of premine. The relatively small handful I've accumulated, due to lack of linux knowledge, now seems like an absolute pittance. I wondered why you'd taken an interest in the thread, but now I see you were trying to figure out the OP's game..

Let's make no mistake: some things are seriously wrong with the windows client...So wrong, in fact, I see no way it cannot have been intentional. As I see it, there are 3 specific issues that cannot be easily explained by 'oops'.

Anyways, it's a short amount of time (I would bet it has already been done) until the scrypt kernel is ready to roll out the (n,1,1). I will say this: at least the dev isn't foolish enough to pretend it cannot be done.

^^It's funny when some of the most outspoken linux users show their complete lack of understanding. Thanks for the contribution, buddy.