Trippy Salmon
Aug 24, 2017 · 2 min read

Hi Rafael, creator of fork.lol here.

I think I understand where the confusion comes from. The reason the “blocks/hr” better reflects reality than the other charts is because the blocks are something we can actually measure in real time. Once a block is found we know for sure that it will never leave the chain.

With hashrate it’s different story. We can only calculate the hashrate over a certain time period. The site uses the last 24 hours to calculate the hashrate because this will result in the least “noise” on the chart. You are correct that the table underneath the chart does show the right number for the 3h and 12h period. In the table it doesn’t really matter if the hashrate jumps around a lot. If we would use the 3h average for the chart the lines would jump like crazy, that’s not a very useful chart.

Even the 24h averages are already pushing it. The best way is to use at least a 3 day average to be sure. But here lies another problem, because of the EDA issues Bitcoin Cash experiences, the hashrate sometimes becomes literally 0 for the 3h and 12h charts. You can imagine how the chart will look like.. chaos.

If you think my site is biased against Bitcoin Cash, then it’s also biased against Bitcoin if the hashrate distrubution was opposite of what it is now.

But rest assured, I’m planning to open source everything this weekend so you can check for yourself if I implemented any “trickery”.

Cheers.

(I hope you will update the article with your newly gained knowledge of how the site works, if you have any questions feel free to contact me. Contact details:http://fork.lol/contact)

)

    Trippy Salmon

    Written by