Fuse, hasn't this pool been paid for by the creators of TAG?
Mark funded the loss of coins from when the pool was tanked by fork chain payouts back when the orphan issues and forks were going on. MPOS at the time paid out on confirmed blocks with the pool balance, even if the blocks were building on a fork. It was around 2000TAG at the time which went right back to the miners to cover their losses. However, I've been paying the server costs since day 1.
In the recent past, Mark and I discussed his team taking over the pool and domain name, but we never really finalized anything.
Not sure if this is related but I had payout issues with one of my user. Turns out when he enabled worker and payout notifications, it broke payouts (auto and manual) only to him. So for 4 days, I had to send him payouts from the commandline. It was not until he disabled notification that payouts work again.
On an MPOS front end though right? There aren't any notifications on the nomp/unomp pools that this could be related to. I really think this is either a valid share exploit or a bug in the code. If it is a bug in the code, I would guess you would see a lot more people shouting on other coin threads about payouts. Essentially, what happens is a single address will show a huge amount for payout, which the system then tries to payout but gives an error based on the available balance. So it retries with a percentage decrease in payouts. And it will fail. And then again and again. I have to go into the DB and remove the erroneous payout, then the regular payouts get processed. Not that any of that solves the underlying issue, but just trying to be transparent about what's going on.
-Fuse
