Braiins OS API 1.15.0 adds a tag to mining pause requests
Source report: 2026-09-16 · Editorial analysis published: 2026-09-18
The September 16 API update adds an optional pause tag and corrects license comments. We examine integration checks without claiming changes to fees or automatic recovery.
Analysis and practical implications
This section is our analysis and illustrative calculations, separate from the source report.
The confirmed API change
Braiins lists Public API 1.15.0 on September 16, 2026. PauseMiningRequest receives an optional tag: an opaque value associated with a pause action. The release also corrects comments on four license messages concerning restricted mode and developer fees. These are documentation comments, not an announced fee change. API version numbering is distinct from a miner’s installed firmware version.
A tag is an identifier, not a control policy
An integration can choose a local incident or maintenance identifier for its own records, but should not infer any extra behavior from its spelling. A label saying energy-window does not itself define a tariff, a duration or a restart condition. Our recommendation is to store those operational decisions in a separate controller configuration. The release notes do not establish tag persistence, response echo, idempotency or automatic resumption.
Keep a separate local action journal
Our proposed journal records target identity, request time, intended action, the locally chosen tag and the actual response. Record failures as well as successful submissions. Keeping this local association works without assuming that a later device query will reproduce the tag. Exclude passwords and access tokens. For a batch operation, preserve per-device outcomes so that one successful request cannot hide other failed targets.
A reply and a physical pause are different evidence
After an approved pause request, independently inspect miner state and a suitable production observation window. Pool data may lag, and ventilation or other auxiliary loads may continue. A request response alone cannot establish zero site consumption. Avoid repeating an uncertain action blindly: first inspect the device and your controller’s state. This is our verification method, not a new transaction guarantee provided by the tag.
License comments are not a new fee schedule
Do not alter a profitability spreadsheet merely because license explanations were edited. Our suggested review compares the actual commercial terms, installed configuration and measured billed or deducted amounts. A developer fee, a pool fee and a hosting charge describe different cost categories. If a user-facing explanation changes, keep it consistent with the operative agreement; the API changelog alone is not proof of a revised percentage.
Check client and installed firmware compatibility
A regenerated API client does not automatically update the service on a miner. Our rollout uses a spare device with recorded firmware and control-board identity. Test an ordinary pause without the new field, then the optional field where supported, and inspect errors. Preserve a path for older devices rather than assuming every catalogue model implements this API. Do not flash an unrelated image merely to obtain a newer schema.
Measure energy effects separately
Our hypothetical example uses two devices drawing 3 kW each for a half-hour window: gross device energy is 2 × 3 × 0.5 = 3 kWh. This is not a measured saving or Olenox/Braiins operating figure. Remaining auxiliaries, transition time and foregone production change the actual outcome. A controller should verify when the approved pause ends and who authorizes resumption rather than deriving either from a tag.
What farm software maintainers should do next
Review the official schema, update the local journal design and test a small approved sample before fleet rollout. Keep the request, response and final state as separate records. If there is no operational need for a tag, its optional nature allows a deliberately simpler integration. This article explains the API announcement; it is not a firmware download or proof of support for all ASICs. Use the exact model’s firmware page to check available files and compatibility.
Source: Braiins Academy ↗
Mining calculator ↗
