Updated

Updates & Feature Releases 🚀


Install OCEAN's DATUM Gateway from Foreman

You can now install OCEAN's DATUM Gateway from your Pickaxe page. DATUM lets your site build its own block templates while still mining in OCEAN's pool. Click Install DATUM on a supported Linux machine already running Pickaxe, and Foreman sets up a Bitcoin Core node and the gateway alongside your existing setup, with no extra device to buy. The option is unavailable on Windows Pickaxes.

  • Half the pool fee. Miners building their own templates pay OCEAN's 1% fee instead of the standard 2%.
  • Fewer stale shares. Work is handed out across your local network, so miners spend less time waiting on new jobs from a remote pool.
  • Encrypted pool traffic. Traffic between your site and OCEAN is encrypted with no firmware changes. Pair it with Trusted Pools and Pool Change Approval to catch unapproved pool changes.
  • Transparent rewards. OCEAN's TIDES accounting lets you verify how block rewards are paid out.
  • Learn more in the announcement, OBM and OCEAN Bring DATUM to Foreman, on the DATUM on Foreman page, or in the Quick Guide: OCEAN's DATUM Gateway.

Estimated Miner Load as an Adaptive Dispatch trigger

Adaptive Dispatch rules can now trigger off Foreman's own estimate of your site's miner load. Until now, rules could only react to metrics reported by infrastructure devices. Sites that want to respond to how much load their miners are drawing, without a dedicated metering device, can now build that directly into a rule.

When creating or editing an Adaptive Dispatch rule, choose Estimated Miner Load (Foreman) from the trigger metric dropdown. Its current value is shown alongside it, and thresholds and comparison operators work the same way they do for any other numeric metric.
The estimate refreshes roughly every five minutes.

If Foreman can't calculate the estimate for a cycle, the rule simply does not fire, so it never acts on stale data.
 

Fixes & Improvements 🛠️


Site Load chart no longer shows cancelled dispatches

  • On the Command Center, the Site Load chart was drawing cancelled dispatches as if they were still running, stretching a dispatch band across the whole chart. That made it look like a site was being curtailed when nothing was dispatching it, even though the Events table below correctly showed no active events. Cancelled dispatches no longer appear on the chart, while a dispatch that is still running continues to display through to the present as before.

Global filters banner on the Command Center

  • When global filters are applied, the Command Center now shows the same filter banner you see on pages like Pools and Security. You can tell at a glance that the data on the page is filtered, and clear the filters directly from the banner.

More actions available in the audit log Action filter

  • Several actions were being recorded in the audit log but could not be selected in its Action filter. You can now filter the audit log to Restart Miners, Fan Mode, Advanced Thermal Management, and No PIC Protection Mode events, which makes it much easier to trace when those commands were run and by whom.
     

API reliability fixes

For teams that work with Foreman through the API, several requests that previously returned a server error now respond correctly.

  • Listing HiveOS, CPower, and CSD integration keys without specifying a client now returns the keys for your accounts.
  • Saving a miner edit that leaves out the power override count now saves the rest of the changes instead of failing.
  • Requesting the miner issues list without a client ID now returns a clear "method not allowed" response, so scripts can see they need to include the client ID.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Can't find what you're looking for?

Our support team can help with setup, hardware and billing questions.

Contact Support