where link announcment thread
or where you need to translate pinkcoin
bounty only translation dev, without signature campaign, facebook campaign and twitter campaign

I feel as though I'm not receiving my payment per round. I've been mining for roughly around 6 hours, and I've seen at least 4 separate rounds of shares (500,000) and my balance has yet to be updated. I feel as though the balance updates were quicker 2 weeks ago, and even though each "estimate" changes per round, my balance doesn't change even after 6 hours. Has anyone else noticed this is true for them as well?

This is what would happen:

http://www.youtube.com/watch?v=Ze3hthGRbRo

Ultimately, for the network to survive, there has to be mass adoption and near insurmountable hashpower to secure it. ASIC represents the coming of age for Bitcoin. Why would anyone who is not hoping for a pump and dump not wish the same for Litecoin?

Edit: I don't know if this really means much; but, I notice something today when I was monitoring the situation. When I went to the My Stats tab it seemed to hang up. While it was hanging I checked one of my rigs and the unknown work rejects we're happening. I had been running at below 0.5 percent stales up to that point (suddenly I was at 20 percent; although my miner calls them unknown work). The My Stats tab has to access the database to display. Interesting coincidence?

You're definitely right, there is another ongoing issue.  That is that pushpool gets overloaded periodically.  (a few seconds every few minutes.)  I've expanded file descriptors and every single restriction I can think of to work around this, but have been unsuccessful.

So, unable to expand pushpool I ended up spinning up two pushpools and load balance them using nginx.  I made that change ~6 months ago.  Now we're back to one pushpool or the other getting overloaded periodically, and with the load balancing what happens is the overloaded pushpool gets removed from the balancing and you get sent to the pushpool that is still answering.  If you're making a request to submit work, and that work came from the other pushpool, then the current pushpool doesn't recognize it and it gets flagged as invalid.

Oddly enough, pushpool has memcache functionality and both pushpools are pointed at the same memcache.  I thought initially this was so that you could run a bunch of them and have them share the work between them, but clearly that is not the case.  I'm not really sure what pushpool is using memcache for.

As you digest all this you're probably wondering why then can't I just add a third pushpool to the balancing.  The problem is that in order to make sure that you always get sent to the same backend pushpool (because of the issue where your work is invalid if you don't) I had to configure the balancing to be by IP address.  And, naturally, since we're behind a DDoS service, 80% of our traffic comes from... the same IP address.  Ugh.  So even with the two pushpools, one takes like 80% of the traffic and I have no way to split it out beyond that.  I need like 3 DDoS services with each one running a pushpool behind 'em. 

Scrypt Kids