-
WarpAxe v0.1.36
Stablereleased this
2026-10-23 12:16:13 +00:00 | 208 commits to main since this releaseOnly the BitForge Nano gets new limits and a new temperature scale; every other board keeps its temperatures and limits. The Nano's stock firmware, ForgeOS, is open source, and this release brings WarpAxe in line with what it does on the board it was made for (ForgeOS v1.7, read from its source; details in
docs/08).The Nano's temperatures on the maker's scale. The chip temperature sensor reads the BM1370's diode through an ideality setting. ESP-Miner tunes it to 0x24 on the Bitaxe Gamma boards; ForgeOS has tuned the Nano to 0x37 since its first release. Measured back to back on the same chips, 0x24 reads 8.2 °C higher. WarpAxe now uses 0x37 on the Nano, so its 75 °C chip stop applies where ForgeOS applies it (the 105 °C regulator stop reads the regulator's own sensor and is unchanged). After the update a Nano shows about 8 °C less at the same point. The fan target moves with the scale to 52 °C, so the chips stay at the same real temperature as under v0.1.35 and the fans run as before (a first candidate kept 60 °C on the new scale, and the Nano's error rate rose from about 1.5 % to 6 % at 425 MHz / 1000 mV). If the miner has the old default of 60 °C stored (an earlier save of the settings page stores it even if you never changed it), it is reset once to 52 °C on the first start; a different value you chose stays and now counts on the new scale (about 8 °C lower gives the chip temperature it held before). The same goes for a chip stop you set yourself below 75 °C: it is not moved, so lower it by about 8 °C if you want it to stop at the same real temperature. If you tune the Nano with WarpTune, the WarpTune card shows a yellow hint after the update that the fan target has changed since the calibration. That is expected and needs no action; it goes away after the next calibration. A new calibration is optional and only worth it to get the Max preset back to a full clock under WarpTune's limits.
The Nano's regulator limits as ForgeOS sets them. The regulator now warns at 38 A and shuts down at 40 A (before: 45 / 52 A; the part is rated for 40 A), and the input over-voltage limit is 13.5 V (before: 14.8 V). The 625 MHz / 1160 mV choice stays: measured on our Nano at 37.1 A on average and 37.6 A at most, it runs close to the warning line; ForgeOS offers its own 636 MHz / 1160 mV preset under the same 40 A limit. If it ever trips the limit, WarpAxe handles it like an overheat stop: chips off for at least a minute, then back on; the third stop within an hour keeps them off and shows why.
A pool's extranonce size is checked. A pool that asks for an extranonce2 size outside 1–16 bytes (Stratum V2: 1–32) is refused instead of trusted. Before, a broken or hostile pool could make the miner reserve as much memory as it named.
Moving from the stock firmware.
- A pool the previous firmware ran on TLS with your own certificate now stays on TLS, with the built-in certificate bundle, instead of being switched to plain text as before. WarpAxe has no place for your own certificate, so a pool on a private certificate fails visibly; switch TLS off for it on purpose if you trust the network.
- If the previous firmware was in its overheat mode (ForgeOS and older AxeOS versions leave 1000 mV, 50 MHz and fans at 100 % behind), WarpAxe does not take over clock, voltage and fans; the board's own defaults apply.
Tested on 2026-10-23 on the BitForge Nano: both diode settings read back to back on each chip (106 pairs, warm at 525 MHz / 1150 mV), error rate unchanged, regulator limits in place.
One image for every supported board:
warpaxe.bin,warpaxe.bin.sha256,warpaxe.bin.sig,tested-on.txt; for the first installwarpaxe-factory.binandweb-flasher.tar.gz(checksums ininstall.sha256).