-
Notifications
You must be signed in to change notification settings - Fork 182
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
Better readable network difficulty + correct readable hash rate calculation #43
base: master
Are you sure you want to change the base?
Conversation
When difficulty is 1598298868 (for example) it's not readable. 1.49 GH is much better to read.
The denomination of hash rates follows the International System of Units (SI) https://bitcoin.stackexchange.com/a/21498
The denomination of hash rates follows the International System of Units (SI) https://bitcoin.stackexchange.com/a/21498
Created function to get readable difficulty string
Sorry for errors. Now it's must be correct. Tested on my own pool. |
Are you sure this is correct? Doesn't it still need to be represented with the H, eg. GH. Its great the extra units are added and the K-k is corrected though :) |
It was the first thing I did - started to use getReadableHashRateString for difficulty. Then I've made some research and find out that difficulty should be without H, so I created a separate function. |
When difficulty is 1598298868 (for example) it's not readable. 1.60 G is much better to read.
The denomination of hash rates follows the International System of Units (SI)
https://bitcoin.stackexchange.com/a/21498