Re: Current known system issues
Posted: Sat Dec 09, 2017 12:41 am
Ive had a ltc payout stuck for 5 whole days. Could you respond to my email chris and push it through its not very large... but enough to obviously care about..
Professional cryptocurrency mining made simple
Please submit a support ticket. E-Mails are often not responded to because they are directed to the wrong person to answer your question. The only way to guarantee a response is to submit a support ticket to https://support.prohashing.com/.waynesworld wrote:Ive had a ltc payout stuck for 5 whole days. Could you respond to my email chris and push it through its not very large... but enough to obviously care about..
All shares are being credited. We haven't been able to reproduce the issue of worker statuses disappearing, so we don't have any ETA on a solution for the issue. However, in the meantime, the system is paying miners as expected.GNaps11 wrote:I'm showing no live worker status (sometimes they come on and off) but 100% avg. mining efficiency. Is that a bug in the new software or my miners dropping or hashing for free?
Steve, you guys must have made improvements. I have about 30 miners switched over now and they have been stable.Steve Sokolowski wrote:I thought I would publish a few of the current known system issues caused by yesterday's major release so that people are aware and don't submit support tickets for them.
- The live data loading when you initially visit the forums or website can be slow. We're working on that. Profitability is not affected.
- There is a crash bug that is caused by a race condition in the share inserters. It's been fixed and changes will be deployed later today.
- The hashrate charts from this morning are inaccurate due to the crash bug. Balances may be a few percentage points lower, as well. No money was lost and Chris will correct the data later today.
- Some users are reporting that miners are not displaying in the "live coin status" portion of the "earnings" page. We have not been able to reproduce this issue, but we were able to confirm that no money is being lost because of it. As soon as we can figure out a reproducible test case, we'll look into it.
- An issue that is not a bug is that the initial difficulty for scrypt is high, at 65536. If you have slow miners, you will see "no valid shares yet" until the difficulty automatically adjusts downwards low enough for you to find a share. This is not an indication you are making no money, as difficulty does not affect profits.
- The bitconnect network is under attack and all payouts in that coin are unable to be sent. We do not know if we will ever be able to send those payments to customers, and it is possible the money may be permanently lost if the attack continues indefinitely, as the attacker is not including transactions. As stated in another thread, if we achieve 12 TH/s, we may attempt to reverse the attacker's blockchain.
- Profitability has declined because the LTC difficulty jumped 25% yesterday and will jump more at the next adjustment.