-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong accepted hash for lyra2rev2 #62
Comments
I will need the log file with a DEBUG level to check what happens. |
Hare is a log file over 10 minutes. In this time the Accepted Difficulty raised up until 2362. Thanks! |
modify the Hashrate estimation for algo other than SHA-256 an Scrypt.
Could you try the new beta-release (0.8.1-SNAPSHOT) adn configure the option "hashesPerShareDiff1Divider" with a value of 256 ? |
The hashrate seems ok (67,109 MH/s in proxy, 66.2140 in nicehash) I put the option inside the proxy configuration, not inside the pool configuration. Correct? |
Yes, correct. For the difficulty, unfortunately I do not see any problem in your log file.
You see 20278476 in the Web client of the proxy and 128 on the Nicehash website, right ? What is the difficulty reported by your miner ? |
At this very moment: Proxy says: Miner says: Nicehash says: The difficulty seems to add up over time... Regards Am 18. Dezember 2015 23:49:00 MEZ, schrieb Stratehm
|
I see... The Accepted difficulty field is not the actual pool difficulty. It is the cumulated difficulty accepted by the pool (so it indeed increases over time, each time you submit a valid share). The current pool difficulty is displayed in the Pools page by the Difficulty field. |
Ok, my fault! Thanks for fixing the hashrate display, very appreciated! Wish you a good time and a happy new year! |
When using lyra2rev2 to nicehash the accepted hashrate is way off. It shows about 50G when it is only 190M. Also the difficulty is way off. Real 128 shown 20278476.371434607.
Am I missing some configuration setting?
Keep up the great work!
The text was updated successfully, but these errors were encountered: