We're currently investigating a hashrate issue that affects a limited number of customers. These customers have a small decline of about 10% of hashrate. We think that the issue is caused by rejected shares that aren't recorded in the database. The issue only seems to occur with SHA-256 and scrypt. ...

This release has been completed. Feel free to submit a support ticket if you have any issues. We have been seeing increases in luck that appear to be related to some of the bugfixes. Over the next 30 days, as the average luck increases, profitability will continue to increase - it has already gone u...

As part of our continuing cost-cutting initiatives in this bear market, we'll be restarting servers this week. We found that Debian 11 significantly reduces power consumption compared to Debian 10, because it is based on a new version of the Linux kernel. Newer versions of Linux include Intel-specif...

Today's release failed. There was a problem with RandomX duplicate shares. The error is accurate and the shares are duplicates, and they were being erroneously credited to customers. The fixes revealed this bug. For now, we reverted and will continue to pay customers who submit these duplicate share...

I looked into the issue of website bans more closely today. It turns out that many of the banned IP addresses are from people who are using VPNs. While there are some improvements that can be made for home addresses, it's not possible to remove VPN addresses that get banned because they end up being...

The bans are already limited to 5 minutes. They'll just apply to IP addresses now instead of to worker_names. I think that all of the complaints that Paula received had to do with website bans. A third party program is used to handle website bans right now. There's a ticket for Michael to improve we...

Chris is going to release some bugfixes to the mining servers, which may cause some brief downtime, with additional downtime if the releases fail and a revert is required. This, and the other releases recently, have been focused on edge cases. In this particular release: Bans due to a large number o...

As part of my effort to simplify the codebase and eliminate edge case bugs that could cause lower profitability, I was considering removing the "a=" password argument. Customers would instead be required to connect to an algorithm-specific port. Additionally, the port 443 proxy server woul...

Paula answered this in Discord: "Ethash is now hardcoded at 0.25 difficulty due to technical limitations for the foreseeable future" Our implementation of ethash mining turned out to be incorrect. It isn't possible with currently implemented workers to have different difficulties assigned...

Could you submit a support ticket with your username? We can look at logs to investigate.