Quote from: nanona on January 26, 2018, 07:52:40 PM

@IRD-PoolOperator: Your pool still shows the wrong global hashrate (calculated from the correct difficulty) because you have a wrong block time (240s) specified (or just forgot to change a default value). Should be 175s.

Mentioned two months ago: https://bitcointalk.org/index.php?topic=2150442.msg25586036#msg25586036

Reading that I see that your pool used 120s back then. Now 240s. So I guess you simply kept the default from github both times.

I see other pools too have the global hashrate in error, but only slightly. It seems they use 180s instead of the correct 175s for the estimate.

To all pool operators: Use 175s as block time to get correct global hashrate estimates.

It's fixed now, that change didn't make it over when I was vimdiffing the configs during testing.

Quote from: stevebrush on January 26, 2018, 09:53:31 PM

Quote from: nanona on January 26, 2018, 07:52:40 PM

@IRD-PoolOperator: Your pool still shows the wrong global hashrate (calculated from the correct difficulty) because you have a wrong block time (240s) specified (or just forgot to change a default value). Should be 175s.
Mentioned two months ago: https://bitcointalk.org/index.php?topic=2150442.msg25586036#msg25586036
Reading that I see that your pool used 120s back then. Now 240s. So I guess you simply kept the default from github both times.
I see other pools too have the global hashrate in error, but only slightly. It seems they use 180s instead of the correct 175s for the estimate.
To all pool operators: Use 175s as block time to get correct global hashrate estimates.

Yes! Already did it since weeks. For quick copy/pasters (no offense, no conspiracy) search for 175 in the source of the main page of my pool.
https://cdn.discordapp.com/attachments/369381308583116800/406566963037339648/Sans_titre.jpeg

And global hashrate is in the top of the wallet too.

Modifying the website would have done nothing, this is a pool configuration issue.