Hey Steve,
as I changed difficulty from 32768 to 65536 the "Current Mining" tachometer does not show my current hash rate, but last shares are displayed probably as i can see.
Can you please have closer look at it? Thank you.
King regards
difficulty 65536 = causes problems at "Current Mining"-tacho
Forum rules
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.
Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.
We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Welcome to the System Support forum! Encounter a problem related to the pool? Post your issue here and we will help you out.
Keep in mind that the forums are monitored by PROHASHING less closely than the official support channels, so if you have a pressing issue, please submit an official support ticket so that our Support Analyst can look into your issue in a timely manner.
We cannot answer financial questions related to your account on a public forum, so those questions should always be submitted through the orange Support button on prohashing.com/about.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: difficulty 65536 = causes problems at "Current Mining"-t
I'll get right on it.
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: difficulty 65536 = causes problems at "Current Mining"-t
I resolved this issue. It turns out that, when a miner has such a high difficulty, its shares can overflow the database and cause an error, which causes hashrates to not be inserted.
Mining itself, and payouts, are not affected, so I'll hold this change until the end of the day so that I don't have to disrupt miners again - but you can expect the chart to start working by the end of the day. Thanks for the report!
Mining itself, and payouts, are not affected, so I'll hold this change until the end of the day so that I don't have to disrupt miners again - but you can expect the chart to start working by the end of the day. Thanks for the report!
Re: difficulty 65536 = causes problems at "Current Mining"-t
Im very happy with what miningrigrentals shows me using d=65536 on prohashing 
-
Steve Sokolowski
- Posts: 4585
- Joined: Wed Aug 27, 2014 3:27 pm
- Location: State College, PA
Re: difficulty 65536 = causes problems at "Current Mining"-t
What are they showing you? Is it higher than what we are reporting in our own statistics?
Re: difficulty 65536 = causes problems at "Current Mining"-t
no i guess not, well sometimes I have an average of 100+ mh/s over a duration of 1 hour (using d=65536) which is a difference comparing to other pools i used to hash at with same difficulty. I cannot explain thats just my feeling telling me though... The better average hash rate makes me get renter more often as it was in the past with clever mining for instance