Hello all,
I verified all my settings and connectivity. On the Ocean page I see the following states increasing: Shares, Estimated rewards, earnings, and hashrate.
I am not sure why the Workers section was showing my worker “Online”. It is now showing my workers as “Offline”.
Note: I did shut down all services and rebooted the Start9 server last night and re-verified settings.
Any suggestions would be greatly appreciated.
What hashrate are you running at? I have seen on a couple of my lower-hashrate devices that the shares difficulty is set high enough that they often find shares at a slower rate than the liveness checks (so between shares, it looks like they are offline). If that were the case, you would still see a graph of hash rate over time, though (if it is flat-lined, then that is definitely not the issue).
Could you check the logs for Datum Gateway and see if there is anything in there that indicates a problem? When working, you should mainly see lots of messages like this:
2025-06-09T10:54:29-05:00 2025-06-09 15:54:29.387 [ main] INFO: Server stats: 2 clients / 93.81 Th/s
2025-06-09T10:55:02-05:00 2025-06-09 15:55:02.942 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.13009458 BTC, 311 txns, 297148 bytes (Sent to 2 stratum clients)
2025-06-09T10:55:44-05:00 2025-06-09 15:55:44.878 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.13205710 BTC, 517 txns, 391052 bytes (Sent to 2 stratum clients)
2025-06-09T10:56:26-05:00 2025-06-09 15:56:26.866 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.13702214 BTC, 740 txns, 579773 bytes (Sent to 2 stratum clients)
2025-06-09T10:57:08-05:00 2025-06-09 15:57:08.775 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.13849485 BTC, 911 txns, 653775 bytes (Sent to 2 stratum clients)
2025-06-09T10:57:50-05:00 2025-06-09 15:57:50.670 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.13977375 BTC, 1101 txns, 722962 bytes (Sent to 2 stratum clients)
2025-06-09T10:58:32-05:00 2025-06-09 15:58:32.687 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.14237185 BTC, 1290 txns, 916663 bytes (Sent to 2 stratum clients)
2025-06-09T10:59:14-05:00 2025-06-09 15:59:14.643 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.14340439 BTC, 1429 txns, 961955 bytes (Sent to 2 stratum clients)
2025-06-09T10:59:29-05:00 2025-06-09 15:59:29.456 [ main] INFO: Server stats: 2 clients / 73.70 Th/s
2025-06-09T10:59:56-05:00 2025-06-09 15:59:56.661 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.14482274 BTC, 1630 txns, 1036775 bytes (Sent to 2 stratum clients)
2025-06-09T11:00:38-05:00 2025-06-09 16:00:38.660 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.14926586 BTC, 1822 txns, 1212580 bytes (Sent to 2 stratum clients)
2025-06-09T11:01:20-05:00 2025-06-09 16:01:20.351 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.15075667 BTC, 2008 txns, 1288502 bytes (Sent to 2 stratum clients)
2025-06-09T11:02:01-05:00 2025-06-09 16:02:01.828 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.15242953 BTC, 2181 txns, 1380932 bytes (Sent to 2 stratum clients)
2025-06-09T11:02:43-05:00 2025-06-09 16:02:43.511 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.15468415 BTC, 2364 txns, 1481515 bytes (Sent to 2 stratum clients)
2025-06-09T11:03:25-05:00 2025-06-09 16:03:25.492 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.15634122 BTC, 2502 txns, 1542715 bytes (Sent to 2 stratum clients)
2025-06-09T11:04:07-05:00 2025-06-09 16:04:07.554 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.15853517 BTC, 2506 txns, 1541183 bytes (Sent to 2 stratum clients)
2025-06-09T11:04:29-05:00 2025-06-09 16:04:29.519 [ main] INFO: Server stats: 2 clients / 87.12 Th/s
2025-06-09T11:04:49-05:00 2025-06-09 16:04:49.553 [ datum_gateway_template_thread] INFO: Updating standard stratum job for block 900500: 3.15971960 BTC, 2611 txns, 1556281 bytes (Sent to 2 stratum clients)
Plus some additional messages every 10 minutes or so when new blocks come in:
2025-06-09T10:54:20-05:00 2025-06-09 15:54:20.739 [ datum_gateway_template_thread] INFO: NEW NETWORK BLOCK NOTIFICATION RECEIVED
2025-06-09T10:54:20-05:00 2025-06-09 15:54:20.752 [ datum_gateway_template_thread] INFO: NEW NETWORK BLOCK: 000000000000000000008738c71fea046df3301bd45a4efdc1fd9a4da4e81710 (900500)
2025-06-09T10:54:20-05:00 2025-06-09 15:54:20.762 [ datum_stratum_v1_socket_server] INFO: Empty work send completed. Sent to 2 clients across 8 threads
2025-06-09T10:54:20-05:00 2025-06-09 15:54:20.763 [ datum_gateway_template_thread] INFO: Updating priority stratum job for block 900500: 3.12720949 BTC, 129 txns, 127313 bytes (Sent to 2 stratum clients)
2025-06-09T10:54:21-05:00 2025-06-09 15:54:21.036 [ datum_gateway_template_thread] INFO: NEW NETWORK BLOCK NOTIFICATION RECEIVED
If you see something different that looks suspicious, let me know. Feel free to DM me if you see something in your log that appears sensitive that you don’t want to post here publicly.
Ok, cool. Looks like it is working fine. I think 1 TH/s is low enough that your worker will appear offline periodically when it happens to take a while to find a share. That period of being “offline” will be compensated for by the subsequent spikes above 1 TH/s when it does find a share.
Shares use a proof of work process that is very similar to how the main blockchain works – they have a difficulty factor (much lower than the main difficulty factor of course) and are found randomly just like blocks. The minimum difficulty that Ocean supports is set such that a slower ASIC like yours may take some time to find a share, and while it is hashing away to find one, it can appear to be offline when the pool doesn’t see any shares coming in from it in the mean time.
My 1 TH/s device often says offline in the Ocean dashboard but its hashing away and the shares are counted by Ocean. My 6 TH/s never appears as offline. Both devices always show as connected in the Datum Gateway.
Thanks. Yea, it looks like it’s working and Datum shows it on-line so it’s all connected.
I noticed in the Datum Gateway that under Coinbase the BitAxes’s are listed as “Respect” while the Cannon Nano S3 are listed as “Default” .
I did notice this because the two Bitaxe’s (with different names) shows up as one worker and usually show as offline while the S3’s (6/THs+) show up as individual worker. I hadn’t thought about the low TH/s as a factor. Glad I saw this post.
BTW- Thanks for the approval Paul. 
