-
WarpAxe v0.1.40
Stablereleased this
2026-11-04 12:16:33 +00:00 | 181 commits to main since this releaseOne silent chip no longer stays dark until the next restart, and TLS trusts a pinned certificate store. This release changes nothing in how a healthy miner mines. It brings a chip back that stops answering mid-run, and it checks every TLS connection against a fresh certificate store after the eMudhra incident.
What is new.
- A chip that stops answering is brought back. Until now the miner restarted its chips only when all of them had gone silent for a minute. One chip that dropped out while the others kept hashing stayed dark until the next restart: on our NerdOCTAXE-γ one of eight chips stopped after five days at a steady clock, and the miner ran at 7/8 for almost two days. Now a chip silent for ten minutes while work goes out makes the miner start its chips over, which takes a few seconds. At most one such restart per hour. A chip that goes silent again within an hour of each of three restarts is left alone until the next boot or until the clock or voltage changes. A pool outage stops both timers, so it never counts. The event log shows each restart, and the API reports
chipSilentRestarts,lastChipSilentRestart(chip from 0, mV, uptime) andchipsGivenUpin/api/system/info;chainSilentRestartskeeps counting only the all-chips case. WarpTune v1.47.0 reads these: it judges the hashrate on the chips that run instead of turning the clock down, and settles afresh after such a restart. - A pinned certificate store for TLS. After the eMudhra incident (intermediate CA keys compromised, October 2026), the Mozilla root store dropped the eMudhra root
emSign ECC Root CA - G3and no longer includesAAA Certificate Services; the lists built into ESP-IDF v5.3.3 still carry both. WarpAxe now checks every TLS connection — Stratum V1 over TLS, the online update, the BTC price — against curl's extract of the Mozilla store of 20 October 2026 (118 roots) and nothing else. A root of that store that a server sends along, cross-signed by an older root the store no longer has, counts as that root, so such chains keep working (ESP-IDF's verifier alone rejects them; api.coingecko.com is one). If you mine over TLS: a pool whose only certificate chain runs to one of the removed roots no longer connects, and its operator has to serve a chain to a remaining root. Stratum V2 is not affected (it checks the pool's authority key, not a CA).
One image for every supported board:
warpaxe.bin,warpaxe.bin.sha256,warpaxe.bin.sig; for the first installwarpaxe-factory.binandweb-flasher.tar.gz(checksums ininstall.sha256).Downloads
- A chip that stops answering is brought back. Until now the miner restarted its chips only when all of them had gone silent for a minute. One chip that dropped out while the others kept hashing stayed dark until the next restart: on our NerdOCTAXE-γ one of eight chips stopped after five days at a steady clock, and the miner ran at 7/8 for almost two days. Now a chip silent for ten minutes while work goes out makes the miner start its chips over, which takes a few seconds. At most one such restart per hour. A chip that goes silent again within an hour of each of three restarts is left alone until the next boot or until the clock or voltage changes. A pool outage stops both timers, so it never counts. The event log shows each restart, and the API reports