Prohashing Mining Pool Forums

My miners were offline for about a week, and (one of them) just got back online. It's been back up and running since the 6th, but the last payout to CoinBase was on 2016.03.30. My Coinbase account looks fine, and it shows as connected on my settings page.

Thanks for the report. Chris will investigate this tonight and get back to you.

This is caused by the changes the Core is pushing in the latest version of bitcoin that rejects transactions with more than eight decimal places.

I fixed the code and the payouts will be fixed from tonight on. Thanks for your patience.

That's perfect, thanks! This is why you guys have the best Scrypt mining pool, period.

Sorry to say that he payouts have not resumed yet. Is there any new info?

Hi Kires. Coinbase payouts are working for other users, whereas your payment is getting rejected for an "unauthorized token" error. I need you to disconnect and then reconnect your Coinbase account through our site. I think that will fix the issue. Let me know when you have done that and I will try to send the payment.

Well that's weird. Maybe it times out after being inactive for a week? Anyway, I've gone ahead and re-linked the CB account. Would it be possible (or practical) to have errors like that piped to the Account Activity section of the earnings page?

I've never considered putting errors in the account activity section because this is the first time in the history of the pool that we have had a payout error caused by a user's configuration. Every other payout error was caused by an issue in our code or our wallets, so there would be nothing a user could do to fix it. I'd like to only display errors if a user can actually take action to fix them.

I'm going to talk with Steve and see if we can implement a private announcement system on the website. If we need to contact a user, for example to reauthenticate a Coinbase account, we would put a banner at the top of that user's account page with the message. That would get around the issue of contacting users when we don't store their email addresses. It wouldn't automate error reporting like the Coinbase error you experienced, but considering how rarely user-addressable errors occur, I don't think it is worth the effort to implement an automated system.

It would be cool, but I would absolutely understand if building in new functionality to handle edge cases turned out to not be worth it. Stupid Cost-Benefit analysis! Now that I think on it, it might actually be more efficient to handle these case the same way this one was handled, via the message board.