reply on: Bit Axe and Suggested Difficulty Setting - Ocean.xyz Pool \ stacker news ~bitcoin

pull down to refresh

10 sats \ 7 replies \ @ThatWhichisNotSeen 22 Sep \ parent \ on: Bit Axe and Suggested Difficulty Setting - Ocean.xyz Pool bitcoin_Mining

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).

55 sats \ 6 replies \ @Wumbo OP 24 Sep

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. :)

10 sats \ 5 replies \ @ThatWhichisNotSeen 24 Sep

hmm, dang i have not run into the same issues mining with my bitaxe on Ocean (DATUM or not) :(

0 sats \ 4 replies \ @Wumbo OP 24 Sep

When you look at the log in bitaxe what is the difficult being reported as?

Example: "diff 300.1 of 1024."

20 sats \ 3 replies \ @ThatWhichisNotSeen 24 Sep

Here is an example:

diff 269.9 of 262144

0 sats \ 2 replies \ @ThatWhichisNotSeen 24 Sep

at the moment, this is using Ocean pool's stratum address ; i am 'in between nodes' right now so not using DATUM

10 sats \ 1 reply \ @ThatWhichisNotSeen 24 Sep

DATUM is back online, so now looks like this for the same miner:

diff 559.6 of 131072

55 sats \ 0 replies \ @Wumbo OP 24 Sep

Thanks for the info. I am going to spin up DATUM myself and see how it goes