pull down to refresh
I have not compared expected vs actual hashrate . I will put that on my todo list.
I am not running Datum but maybe I should bite the bullet and set it up.
ya id open the bitaxe OS page via the IP address for the machine, let the page build up some data on the hashrate (if you close the page, you'll lose the trending data). Then, compare it to what you are seeing on Ocean's page. 24 hour trend would be interesting to see and probably insightful.
As for DATUM, its not too hard with a start9 (ive done it a few times now so happy to help if you go that route).
Update: The Bitaxe OS page is showing the correct hashrate but Ocean is showing 1/10th of the hash rate.
Looks like a great reason for me to setup Datum. :)
hmm, dang i have not run into the same issues mining with my bitaxe on Ocean (DATUM or not) :(
When you look at the log in bitaxe what is the difficult being reported as?
Example: "diff 300.1 of 1024."
Here is an example:
diff 269.9 of 262144
at the moment, this is using Ocean pool's stratum address ; i am 'in between nodes' right now so not using DATUM
DATUM is back online, so now looks like this for the same miner:
diff 559.6 of 131072
30% is quite high. I know rejected shares aren't necessarily a sign of a problem (https://plebsource.com/blogs/plebsource-blog/understanding-vardiff-why-your-bitaxe-s-rejected-shares-are-normal-and-how-it-s-helping-you-mine-smarter) but I dunno...
I know if you use DATUM to mine to Ocean pool, you can personally adjust the difficulty floor as you can configure how the miner works (whereas if you mine to Ocean's stratum address, they are configuring the work). Is your 24 hour hashrate as reported by Ocean about what you expect ?