Market snapshot · Bitcoin price$77,735Network hashrate936 EH/sDifficulty127.45 T

AI & infrastructure

Braiins Toolbox 26.09: automatic ASIC list refresh and CLI fixes

Source report: 2026-09-14 · Editorial analysis published: 2026-09-18

The September 14 release refreshes known miners automatically. We explain the difference between refreshing data and discovering devices, plus checks for farm operators.

Network switches and cables; archive illustration, not a Toolbox screenshot
Illustrative archive photograph; not the specific product or facility described in the news. Converted to WebP; resized where needed. Yann · CC BY-SA 3.0

Analysis and practical implications

This section is our analysis and illustrative calculations, separate from the source report.

What is actually new

Braiins dated Toolbox 26.09 September 14, 2026. Auto Refresh periodically re-queries known devices; its configurable interval is 30 seconds to one hour, and cycles do not overlap. The release also fixes an empty filtered list on later pages and extends -y/--yes confirmation bypass to update, advanced set and advanced reset. Our analysis below concerns operations, not a measured increase in ASIC performance.

Rack-mounted switches; archival network infrastructure illustration
Illustrative archive photograph; not the specific product or facility described in the news. Converted to WebP; resized where needed. Parkis · CC BY-SA 3.0

Refresh is different from discovery

A farmer adding a miner should maintain two separate tasks: find its address and then keep its readings current. A list of previously known addresses cannot establish that no additional machine exists. After a network or DHCP change, compare router leases with the physical inventory and explicitly perform discovery when appropriate. Auto-refreshing an old row is not proof that its address still belongs to the same serial-numbered device.

Choose an interval for your network

Our suggested rollout starts on one rack with a conservative interval. Record completion time, timeouts and responsiveness before shortening it. A theoretical minute interval suggests sixty starts per hour only if each operation completes immediately; actual scheduling must be observed. More frequent polling is useful only if an operator can distinguish fresh results from delayed or failed queries. Keep control traffic away from a public network.

An empty table is not a dead fleet

When results disappear after a search, first clear the query, remove filters and return to the first page. Compare the visible count with a small set of known devices before rebooting equipment. This isolates a presentation problem from connectivity or mining failure. In an incident note, preserve the query and pagination state; a screenshot without that context can make a healthy fleet look unavailable.

Non-interactive does not mean unchecked

A confirmation bypass is permission to execute, not evidence that the selected targets are correct. Before a scheduled job, make the address list explicit, review the intended action and test on one device. Preserve exit status and results rather than treating the absence of a prompt as success. Avoid showing credentials in logs. Our recommendation is to separate inventory checks from commands that change firmware or settings.

Stale readings and stopped mining are different

For incident triage, compare the observation time, local interface and pool-side shares. An unreachable management service can coexist with ongoing mining; a reachable interface can also report no effective output. A useful operator worksheet keeps address, identity, last successful observation and independent production evidence separate. Auto-refresh improves the opportunity to observe changes, but does not replace these checks or guarantee alert delivery.

A practical acceptance test

Our test plan uses a small mixed sample. Verify that an ordinary reading changes, that a deliberately unavailable test endpoint is distinguished from an old reading, and that filtering from a later page still returns expected rows. Then run an approved non-interactive action only on a spare device and inspect its result. Record both failures and successes; this article does not claim that ASIC.Tools has tested every supported control board.

What to record after upgrading

Keep the installed Toolbox version, operating system, discovery scope, refresh interval and sample outcomes with your inventory. Compare before and after using the same devices and conditions. For readers selecting an ASIC, this software release is management context rather than a new miner specification: use model pages for electrical and algorithm data, and the calculator for your own inputs. The official release notes remain the authority for the confirmed changes.

Source: Braiins Academy ↗

Mining calculator ↗

More in this section