• v0.1.32 821e8d2890

    WarpAxe v0.1.32
    All checks were successful
    CI / Rust checks (push) Successful in 55s
    CI / Regulator scenarios (push) Successful in 1m0s
    Stable

    dvb-projekt released this 2026-10-20 08:47:51 +00:00 | 268 commits to main since this release

    Overheat stops at the stock firmware's lines. Up to v0.1.31 a Bitaxe and the BitForge Nano stopped at 90 °C on the chips and 145 °C on the regulator: values we had taken from two ESP-Miner constants that ESP-Miner itself never uses. AxeOS stops at 75 °C and 105 °C, and so does WarpAxe now. Every board profile was checked against its stock firmware's source (the details are in docs/08): the NerdQAxe++, NerdOctaxe and NerdQX stay at NerdOS's 70 / 70, the NerdQAxe++ Rev 7's regulator now stops at 70 °C as on NerdOS, and the NerdAxe Gamma and Gaia keep a 105 °C regulator stop that NerdOS does not have on these one-fan boards. You can lower the chip limit in the settings; on the Nerd boards you can also raise it up to 90 °C, as NerdOS allows, on a Bitaxe not above its default (a higher value stored earlier now counts as 75 °C). Thanks to the user on our Discord who pushed on the 145 °C.

    Saved pools. Pool → Saved pools keeps up to eight pools, each with a name and the coin it mines. "Save current pool" stores the main pool as it is set now, "Use" makes a saved one the main pool, and the miner reconnects at once, no restart. Passwords stay on the miner. Coming from AxeOS 2.15, the pools it had saved are taken over on the first start.

    Solo mining another SHA-256 coin. "Payout if you find a block" decodes the address in your worker name (base58, bech32/bech32m and CashAddr) and matches it against the coinbase outputs, so solo mining Bitcoin Cash, eCash, DigiByte, FixedCoin or another fork shows your real share instead of 0 %. The other outputs are written the way that coin writes addresses. A new Coin field in the pool settings sets the unit of the amounts (default BTC). A worker name that is a pool account and not an address now reads "paid by the pool".

    Error rate on the dashboard. The chips' error rate over the last minute sits next to the expected hashrate, as AxeOS shows it (green below 1 %, yellow from 1 %, red from 5 %). A rising error rate is the first sign of a core voltage too low for the clock. The per-chip hash counters stay optional.

    Fixes

    • The Avalon card on the swarm page showed "not reachable" on a miner whose internal memory was fragmented: the read now runs on a PSRAM stack, as the network search does.
    • A pool change made while the miner was still connecting, or waiting after failed attempts, applied only minutes later; it now applies at once.

    Updates always find room. After a long uptime the internal memory of a miner can be too fragmented for the 16 KB the update writer needs; up to v0.1.31 the update then said "not enough internal memory" and nothing happened until the miner was restarted. From v0.1.32 the writer runs on the firmware's main task, whose stack is set aside at boot and was idle after start-up, so neither the click update nor an uploaded image depends on free memory any more (tested on a NerdQAxe++ with the internal heap cut into 8 KB pieces). Restart and download mode go the same way, so the chips are always switched off before the reset. Details: docs/09.

    Updating to v0.1.32 itself still runs the old code. If the update says "not enough internal memory", restart the miner (System → Restart) and start the update right after.

    New strings in eight languages, translated by native speakers. Details: docs/08-Temperature-stop-limits-against-the-stock-firmware.md, docs/09-Update-with-a-fragmented-heap.md.

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