-
WarpAxe v0.1.27
Stablereleased this
2026-10-13 09:50:35 +00:00 | 325 commits to main since this releaseA small follow-up to v0.1.26.
Several miners on one power supply. The hint under Settings → Power supply now says what to enter when one supply feeds several miners: split its rating between them so the parts add up to no more than the rating (for example 600 W → 240 + 150 + 100 W). WarpTune then keeps each miner below 80 % of its part. In eight languages, reviewed by native speakers.
Tidier settings. The power supply field sits in the form grid next to its neighbours, with the same spacing, instead of across the full width directly under them.
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). -
WarpAxe v0.1.26
Stablereleased this
2026-10-12 16:23:17 +00:00 | 330 commits to main since this releaseWhat does your power supply deliver? Settings has a new field for the power supply's rating in watts (optional, on boards with a regulator). The dashboard asks for it until it is set; the notice links to the field and can be dismissed. The API gives it as
psuWatts, so a tuner can stay below it: WarpTune from v1.39.3 takes its 80 % limit from there when its own configuration sets none, and searches for a higher clock only with a limit known. The stock firmware has a fixed maximum per board instead, which says nothing about the supply that is actually plugged in.Input and core on rows of their own. The dashboard's power card shows the input voltage, the core voltage and the core current each on its own row. The input current appears only where the board measures it, and as an estimate (≈) on the NerdAxe. A Bitaxe's 40 A no longer read as if they came from the power supply.
Also in this release:
- README: the comparison with the stock firmware checked again against AxeOS v2.15.3 and NerdOS v1.1.0.1, with new rows for rollback, pool changes without a restart, chips off and on, the clock and the power supply's rating; new screenshots.
docs/04states its result at the top.- New UI strings reviewed by native speakers.
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). -
WarpAxe v0.1.25
Stablereleased this
2026-10-11 06:51:13 +00:00 | 335 commits to main since this releaseIs the clock set? TLS connections and a Stratum V2 pool with authentication wait for the time, so a blocked or wrong NTP server used to show only as a failed pool connection. The Network tab now says whether the time is synchronised, through which server and how long ago, and how far the miner's clock is from the browser's. The dashboard shows a notice only where it matters: when the clock is not set while a pool needs it, or when it is more than five minutes off. The new API field
ntpLastSyncgives the time of the last sync. Thanks to John11 for the idea.Calmer hash counters. A domain bar turns yellow below 80 % of its chip's mean and red below half (before: 90 % and 80 %). Even the 30-second means of healthy domains spread by about ±10 %, so on a board with many domains one was almost always yellow. A dead domain sits near 0 and still shows red at once.
Also in this release:
docs/05: the BM1373 init of NerdOS against ESP-Miner's, and an A/B on the NerdAxe Gaia. Both give the same rate and the same error count, so the Gaia keeps NerdOS's init, which is also its stock firmware's.- README: the comparison now lists what the stock firmware offers in addition.
- New UI strings reviewed by native speakers.
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). -
WarpAxe v0.1.24
Stablereleased this
2026-10-09 15:17:56 +00:00 | 344 commits to main since this releaseNerdOS's chip init on the Nerd boards. On a NerdOctaxe-γ at 700 MHz, one hash domain of a chip sometimes stayed at about 3 % of its rate after a start, so the miner lost about 3 % until a power cycle. The cause was a single core-clock trim: ESP-Miner changed it in August 2026 (0x0C to 0x10, plus two new writes for its new boards), and WarpAxe took its init from there. NerdOS, which the Nerd boards were built and tuned with, keeps 0x0C. The BM1370 on the NerdQAxe++, NerdOctaxe and NerdQX now gets NerdOS's init. Bitaxe boards keep ESP-Miner's. On the bench the Octaxe came up with all 32 domains in 6 of 6 starts (restarts and chips off/on), against 2 of 6 with the old init.
Chips off as the stock firmware does it. On the NerdQAxe++ Rev 6, NerdOctaxe and NerdQX, "chips off" now follows NerdOS's shutdown, whether by hand, by an overheat stop or before a restart: the chain held in reset, the core rail off, the chips' I/O supply off half a second later, and the data line to the chips held low meanwhile. "On" follows NerdOS's bring-up order.
Also in this release:
- After a restart that was not a power-on, the chip supplies stay off at least five seconds before they come back.
docs/04describes the search step by step, with both bench rounds.
The API is unchanged.
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). -
WarpAxe v0.1.23
Stablereleased this
2026-10-09 10:02:03 +00:00 | 350 commits to main since this releaseBest difficulty since the start and all-time. The dashboard now shows the best difficulty since the last start in large, with the all-time best (kept across restarts) beneath it, labelled "since start · all-time" on every board, as the T-Display-S3 already did.
NerdNOS device page. On a board without regulator or fan the display's device page shows what the board has instead of dashes: the ESP32-S3's temperature, the effective rate against the nominal one, the Wi-Fi signal, the clock it returns to after a restart, and the shutdown temperature. The new labels are reviewed by native speakers.
Smaller image. The Bitcoin whitepaper is no longer built into the image; the web UI links to the copy next to the installer at warppool.org/warpaxe/bitcoin.pdf. The image is about 180 KB smaller, which keeps room below the 3 MB limit that lets a NerdMiner's settings survive the first install on a T-Display-S3.
Also in this release:
- The README records WantClue's consent for the NerdNOS lettering on the boot screen.
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). -
WarpAxe v0.1.22
Stablereleased this
2026-10-08 14:56:29 +00:00 | 357 commits to main since this releaseNew board: the NerdNOS (BM1397). WarpAxe now runs on the NerdNOS, the BM1397 carrier for the T-Display-S3 (rev 1.3), and with it on a third ASIC family: the BM1397 does not roll the version itself, so the ESP32-S3 computes four midstates per job. Against its stock firmware at 300 MHz the pool counted about 190 GH/s with WarpAxe and about 180 GH/s with the stock firmware, one hour each. The first start recognises the carrier by its thermistor and its 1.4 V core rail and takes over the NerdMiner wallet and Wi-Fi. Temperature comes from the thermistor, the power is an estimate (shown with "~"), and the clock is set by hand. After an overheat stop the chip comes back one clock step lower, until the next restart. Thanks to WantClue and Benjamin Wilson for the board and its firmware.
Rollback of an update that does not start. A new image now boots on trial and marks itself good once the chips run, at the latest after three minutes. If the miner resets before that (a crash, the watchdog, a power cut), it goes back to the previous version, and the System page says so. This needs the new bootloader, which only a USB install writes: reinstall once with the web flasher (your settings are kept). Without it, everything works as before.
Pool changes apply at once. A change to the main or fallback pool, the worker or the suggested difficulty now reconnects right away, no restart needed.
Also in this release:
- An open web UI tab reloads itself when the miner comes back on new firmware, wherever the update came from.
- Every settings change is logged with the address it came from.
- USB: the status shows "not connected" when the cable is pulled; the USB serial number is the device's MAC; a second WarpAxe on the same computer can get its own USB address (Network → USB address).
- The chip difficulty starts at the profile's value and follows a lower pool difficulty only once that has settled, so a fresh connection does not flood the chips' answers.
- T-Display-S3: the best difficulty keeps its decimals and survives restarts.
- Settings on boards without a regulator or fan show only what is there; below 1 TH/s rates are shown in GH/s with two decimals.
- New API fields:
otaState,dieTempC,yieldPercent,clockStep,hasFan,hasVr,powerEstimated,usbSubnet.
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). -
WarpAxe v0.1.21
Stablereleased this
2026-10-07 16:54:04 +00:00 | 411 commits to main since this releaseHash counter total. On boards with several chips the hash counter card (Settings → Dashboard, off by default) now ends with a total line: all chips' counted hash rate together and their errors. Suggested by John11.
T-Display-S3: Stratum V2 again. The experimental T-Display-S3 shows the Stratum V2 fields on its Pool page again (protocol, the pool's authority key, "require authentication"). WarpPool from v1.37.1 recognises the board as NerdMiner-class and opens its Sv2 channel at the same small difficulty as on V1; in our test all shares were valid. Other Sv2 pools may start a channel far too high for a few hundred kH/s, so that no share ever arrives: stay on V1 there. Before the first 10-minute average the board now reports 290 kH/s to the pool instead of 230.
⚠️ The T-Display-S3 gets to about 60 °C on its back while it hashes: put it in a case, and don't hold it in your hand while it mines.
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). -
WarpAxe v0.1.20
Stablereleased this
2026-10-07 08:45:33 +00:00 | 414 commits to main since this releaseT-Display-S3: about 290 kH/s instead of 230. WarpAxe ran every ESP32-S3 at 160 MHz, while the T-Display-S3's display and API claimed 240 MHz. The experimental T-Display-S3 now really runs its CPU at 240 MHz and shows the clock it runs at. On our board the hash rate went from about 237 to 293 kH/s (+24 %) and the chip temperature from 57 to 60 °C, far below its 85 °C pause. Boards with chips are unchanged.
⚠️ The T-Display-S3 gets to about 60 °C on its back while it hashes: put it in a case, and don't hold it in your hand while it mines.
Also in this release:
- The System page showed the running partition as "?" when it was first asked right after a start; it now shows the slot.
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). -
WarpAxe v0.1.19
Stablereleased this
2026-10-07 07:17:32 +00:00 | 418 commits to main since this releaseThe T-Display-S3 takes online updates. The experimental T-Display-S3 (NerdMiner hardware, hashing on the ESP32-S3) now updates itself like every other board, with the same signed online update. It is only offered releases that ran on a T-Display-S3 before they were published: each release lists the boards it was tested on in a new asset,
tested-on.txt. On a T-Display-S3, a newer release without it shows as "not yet released for this board" and is not installed. Boards with chips are offered every release, as before. A T-Display-S3 on v0.1.18 cannot update itself yet: install v0.1.19 once with the web flasher (settings are kept), and online updates work from then on.NerdOS's dashboard numbers.
GET /api/v2/dashboardnow answers with NerdOS'sperformanceobject (as in NerdOS v1.1.1-alpha4): the hash rate now, over a minute, ten minutes and an hour, and per chip the hash rate and the error hash rate in GH/s, from the chips' own counters. A tool that reads NerdOS reads WarpAxe the same way, and a weak chip shows without waiting for pool rejects. (Thanks shufps for the pointer.)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). -
WarpAxe v0.1.18
Stablereleased this
2026-10-07 05:20:25 +00:00 | 426 commits to main since this releaseExperimental: the T-Display-S3 without an ASIC. The LilyGO T-Display-S3, the board NerdMiner runs on, now runs WarpAxe too, from the same image as every other board. It hashes on the ESP32-S3 itself: the chip's SHA unit on one core with a precomputed midstate, as NerdMiner v2 does, and a software loop on the other, together about 230 kH/s on USB power. That is a lottery ticket, not a miner. Thanks to BitMaker for the go-ahead.
- Installed with the web flasher only, and it stays at the version it was installed with: no online update, no upload. The flasher's full backup is the way back to NerdMiner.
- On the first start, a board on which nothing answers on the I²C bus and that still holds NerdMiner's settings becomes the T-Display-S3. It takes over Wi-Fi and wallet (worker
<wallet>.WarpMiner) and mines on WarpPool. Without NerdMiner's settings it is only offered in the board choice, never taken on its own. - The web UI and the display show kH/s, the ESP32-S3's temperature, shares per hour and the uptime. Hashing pauses at 85 °C and resumes at 75 °C.
- Nothing changes on boards with chips.
The update bar finishes on every network. After an online update the bar could stay at "Writing 100 %" although the miner had already restarted on the new version: a status request sent just before the restart could hang instead of failing, so the restart went unnoticed. Requests now give up after 4 s, and a miner that comes back with a new version counts as done. Since the bar runs in the page of the version you update from, this shows from the update after this one. Until then, a reload clears it. (Thanks John11.)
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).