Net hash rate and your stats hash rate showing 4x higher. Pool hash rate OK. about node-cryptonote-pool HOT 5 OPEN

The pool code is specifically written for Monero, but since Monero is a Cryptonote coin the code works with pretty much all other Cryptonote, but you have to understand the coins and there metrics such as block target times.

Changing Block Target Times:
To adjust the block target time in the code, if you are setting up a pool for a coin other than Monero, you need to edit the index.html file located in the website_example directory.

In the home.html file, "website_example/pages/home.html", line # 207 reads
updateText('networkHashrate', getReadableHashRateString(lastStats.network.difficulty / 60) + '/sec');

The "60" value is the coins block target time. This will need to be updated to represent the target time of whatever coin you are trying to setup a pool for.

Also, to setup a functioning pool for coins other than Monero, you will need to modify the coinunits.
And for the calculator to work you will need to modify line 336 of the home.html file.

from node-cryptonote-pool.

It appears that after some time, the your hast does come in line. The network hash always remains 4x higher though. Left it on for 24 hours +

from node-cryptonote-pool.

this is not a problem with the pool, this is because you have incorrect target time for XDN.

from node-cryptonote-pool.

Makes sense, considering Ducknote has four times the target time of Monero. Which file do you edit for that? Ive changed the target time in the config.json many times finding optimal settings for my pool and its had no effect on the net hash (as expected). You help is appreciated!

from node-cryptonote-pool.

What did you modify within index.html to correct poolhashrate?

from node-cryptonote-pool.