Quote from: poolwaffle on February 26, 2014, 10:46:44 PM

Hey guys, payment update. Our withdrawals from last night and this morning went through a bit ago, but we have the same problem as a few days ago. Essentially the amount withdrawn doesn't cover all of the new earnings since the withdrawal started. So I've got another withdrawal pending now (I'm expecting it to take the normal 6-12 hours cryptsy is taking), and for now I'll do what I did last time, which is run payouts in order of longest time since payout. I think this is probably going to become more of a standard thing due to the delays at cryptsy. I know there was a bit of dislike to it last time, as it brings up the question "why did half the users get paid", but at least for the immediate future while we figure out how to get these withdrawals processed faster (I'll look into their new auto-withdrawal API), it does at least let us get some of the payments out to miners. And as long as its done in a consistent manner, I don't think its a huge issue.

So the current plan, for the next few days (at least) is to pay out users as we have the funds. Anyone over the threshold (0.01btc) will be eligible for payouts, and we'll select users who haven't been paid in the longest time first. We'll pay out all of the funds we have at the time, and run another set of payouts every time a cryptsy deposit clears. We'll likely be running them twice a day (we'll see).

This method will work nicely in the future as well assuming constant delays from cryptsy (I'm doubtful of them getting fixed), so we can make multiple requests throughout the day, and payouts as they come in.

Proposal: If Cryptsy pendings cause you to only have XX% of the BTC owed to pool members, then pay each pool member XX% of what is owed. I think this is much fairer than paying some and not paying others.