Skip to content
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

Open
wants to merge 15 commits into
base: master
Choose a base branch
from
Open

Conversation

Anton-Beresansky
Copy link

@Anton-Beresansky Anton-Beresansky commented Nov 20, 2017

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

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
@Anton-Beresansky Anton-Beresansky changed the title Better readable network difficulty Better readable network difficulty + correct readable hash rate calculation Nov 22, 2017
@Anton-Beresansky
Copy link
Author

Sorry for errors. Now it's must be correct. Tested on my own pool.

@DiscoTim
Copy link

DiscoTim commented Dec 1, 2017

Are you sure this is correct? Doesn't it still need to be represented with the H, eg. GH.
If that is true, it could just use getReadableHashRateString instead of the new function.
I could be wrong :D

Its great the extra units are added and the K-k is corrected though :)

@Anton-Beresansky
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants