• v0.1.12 e76e9df7c1

    WarpAxe v0.1.12
    All checks were successful
    CI / Rust checks (push) Successful in 44s
    CI / Regulator scenarios (push) Successful in 47s
    Stable

    dvb-projekt released this 2026-10-01 06:41:17 +00:00 | 503 commits to main since this release

    Hash counters: a restarted counter no longer spikes the error rate. In v0.1.11 a chip that restarted its counters — on a NerdOctaxe it happened during a core-voltage step — produced one reading with a huge delta, and errorPercentage jumped to 92 % for a second (the shares were fine). A delta larger than any chip can hash in a second now only resets the baseline, so a restart or a garbled reading costs one second instead of a spike. Update from v0.1.11 recommended if a tool or tuner acts on these values.

    Error rate over a minute. New errorPercentage1m in /api/system/info (and miner.error_percent_1m in /api/v1/state): the error rate over the last full minute of counter deltas, 0 until the first minute is complete. errorPercentage stays AxeOS's per-second value, now clamped. Tuners should read the one-minute value.

    Hash counters card and the BM1373. The BM1373 fills only two of its four domain counters (AxeOS scales them by two). The card now hides a domain that stays at 0 on that chip instead of marking it red, and shows its error rate without a colour: on a NerdAxe Gaia it runs at 5–8 %, against 0.4–1.5 % on a BM1370, and there is no known baseline for this chip yet. The card's header shows the one-minute error rate.

    AxeOS's 0/1 switches. isUsingFallbackStratum, useFallbackStratum, useNTP and autofanspeed are now numbers 0/1 as in AxeOS (they were true/false, which some dashboards showed as blank), and a PATCH with 0/1 for an on/off setting is accepted instead of rejected. Reported by John11, who also runs WarpAxe on a Bitaxe Gamma Turbo now — the second profile to run on hardware for the first time at a user's.

    NerdOctaxe v2.2 and the board choice. A user's NerdOctaxe-γ v2.2 stopped within a minute on v0.1.11 with both Nerd profiles. Most likely cause: WarpAxe stopped the chips after 60 s without a chip temperature, and that board's chip sensor may never answer. The 60-s guard now applies only once a chip temperature has been read; a board whose chip sensor never answers runs as on NerdOS — on the regulator's limit with the fans at full — and says so in the log. The v2.2's 4-phase regulator path is still untested; please keep a way back to NerdOS. Also: while a Nerd board waits to be chosen, the display now runs, so the setup hotspot's name and password show (before, the screen stayed dark and the hotspot could not be joined).

    One image for every supported board: warpaxe.bin, warpaxe.bin.sha256, warpaxe.bin.sig; for the first install warpaxe-factory.bin and web-flasher.tar.gz (checksums in install.sha256).