Status as of Saturday, October 13, 2018

[Steve Sokolowski]

Good afternoon! Our focus on stability has moved on from low-level monitoring of servers and services to beginning to identify hard-to-find bugs in the website, mining servers, and other components. Here's a description of some of the improvements that have been made since the last update.

• Constance resolved a number of issues with saving payout proportions and payout addresses. It turns out that static coin miners can earn coins without being required to enter a payout address before earning them, a situation that was not accounted for earlier. In some cases, there would be no place for the wallet address to be entered for those coins, so customers couldn't bypass the error caused by not having a payout address available for a coin. Chris wrote a program to check the database every hour for new statically mined coins, and to add payout address rows to the database so that customers can enter the addresses and resolve the error.
• Constance also resolved an issue with logins and E-Mail addresses where customers' usernames containing non-alphanumeric characters tripping security checks that caused them to be unable to login. Both website fixes were released yesterday evening.
• I finally discovered the cause of many network connectivity issues. The mining servers publish data to the WAMP server every time a worker connects or receives a new coin, but most channels for workers have no subscribers. In those cases, the WAMP server just discards the information, causing its CPU usage to reach 100%. After the next mining server release this afternoon, the mining servers will track which channels have subscribers, and only generate updates for those channels, so that no CPU usage is wasted on the WAMP server discarding these updates to channels that have no subscribers.
• An issue was discovered with the share inserters that affected customers who had two charities or a charity and Coinbase payouts enabled, and those two things paid the organization receiving the money (Coinbase or the charity) in the same coin. The share inserters would fail to insert any shares for that customer. The issue was resolved two days ago and released successfully.
• Chris discovered that 75 coins had wallet.dat files larger than 250MB, which caused orphaned blocks and failed payouts. These files become large because every transaction to our address gets permanently stored in them. The solution is to generate a new wallet and move all the money to the new wallet, which Chris completed successfully for all these coins last night.

Some support tickets relating to these issues have not yet been replied to, and we plan to perform a complete audit of all 94 open tickets tomorrow. After writing this post, I'm going to start compiling another post about Coinbase's customer service to try to resolve the Coinbase payouts issue through the use of publicity. That one will be published tomorrow morning.

[dahchael]

Hi, there’s now an issue where you can’t reduce payout minimums nor add additional payout currencies. I’m sure the team is on top of it & it’s temporary but thought it worth mentioning in case it’s not on the list.

Thanks!

[dahchael]

Also, several payout coins have been delisted from exchanges & backup wallets unavailable. Batcoin (BAT) for example is one of a few that no longer comply, others I think may be temporary due to the recent dive.