I just finished correcting the bug -  I definitely was able to identify it and it was located in some code that dealt with really really short blocks, so it didn't get tested much.  The test suite I had run on it did not include a very specific set of variables that would trigger the bug.  Ugh...

I am very sorry guys.  Payouts should not be affected at all, and block processing should return to normal now.  There is about 4 million shares backed up in the database, so it's going to take several hours at least to work through them and get them credited properly.  No shares are lost since the bug started, but the stats won't show up in your account for several hours.  The pool stats are probably going to go wonky now that processing has started again as well.

I had to roll back the user accounts about 8 hours give or take a couple hours... so any payouts you did during that time are gone.  Really, this only means you either received funds that are not accounted for, or any payouts you initiated that did not complete are also gone.  So basically, some people ended up with a lot more BTC than they should have.

I would like to thank beekeeper for returning 97.7 BTC so far.  That helps!  I am kind of sick at losing over 1000 BTC to a bug like this, I thought I had the code tested properly, but apparently I missed that one spot.  It was some newer code that I had put in a couple months ago, which is why it's only cropping up just now.  I normally keep the hot wallet a little lighter than 1000 BTC, but I had let it get a bit fatter than usual while I've been traveling... Well, it's thin now!  

So again, I would kindly request that anyone who has received extra funds erroneously return them to: 1hK7oeDzHTYwSG2BXhfzaucJXenHfTTkL

Obviously, I can't force anyone to do that.  I will be looking through the accounts and seeing who got paid what that they shouldn't have and see if there's anything to be done about it... but I suspect a lot of the people who got illicit funds were on auto-pay, so when their balance suddenly went way positive, it just initiated auto-payouts and they didn't do anything explicitly on purpose.  I know some people have, though... I see a lot of manual payouts happening in the timeframe that the bug was happening.  So we'll see how many honest folks we have here!

Thanks for the understanding guys and I apologize again.  Share processing is working and will be catching up as fast as it can.