• v0.1.47 635639a292

    WarpAxe v0.1.47
    All checks were successful
    CI / Rust checks (push) Successful in 2m4s
    CI / Regulator scenarios (push) Successful in 1m3s
    Stable

    dvb-projekt released this 2026-11-19 13:00:23 +00:00 | 1 commits to main since this release

    Clock per chip on the dashboard, Bitaxes WarpAxe cannot run are named before anything gets power, and a silent pool no longer costs minutes. On boards where WarpTune or the owner slows a single chip, the dashboard now shows each chip's clock, and who set the offsets and when. A Bitaxe on another chip (Max, Ultra, Hex, Supra, Supra Hex) or a TinyChipHub Zyber is recognised from the settings its stock firmware left behind, by the firmware and by the installer page, and nothing is switched on or written. A pool that accepts the connection and then sends nothing now costs 30 seconds instead of three minutes per attempt. The image is about 34 KB smaller than v0.1.46. A miner that runs without trouble mines as before.

    New.

    • Clock per chip on the dashboard. Since v0.1.44 the chips of a BM1370 or BM1373 board with several chips can run at their own clocks (WarpTune uses this to slow down a chip that makes errors before the whole chain has to). Until now that was only visible in the folded "Clock per chip" fields on the settings page. While at least one chip has an offset, the dashboard's power card now reads "Clock (base)" and lists each chip with its clock, the offset in yellow and, where the board measures one per chip (the Naja Duo and the Gamma Turbo), its temperature, together with who set the offsets (by hand, WarpTune or the API) and how long ago. The hash counters show each chip's clock under its name, and "Clock per chip" in the settings opens by itself. With every chip at the chain's clock the pages look as before. API: chipFreqOffsetsBy, chipFreqOffsetsAt. A change by hand or through the API also goes into the event log. Details in docs/18.

    Changed.

    • Bitaxes on other chips are named, not started. A Bitaxe Max (BM1397), Ultra or Hex (BM1366), Supra or Supra Hex (BM1368) cannot run WarpAxe. Until now a Supra Hex was offered the Gamma Turbo on its first start, and a Supra or an Ultra was taken for a Gamma, with its chip switched on until the chip's ID refused it. WarpAxe now reads the board model the stock firmware (AxeOS) left behind, before any chip gets power, and the web UI shows "Recognised: Bitaxe Supra Hex (6× BM1368)" with "WarpAxe cannot run this board yet, so its ASICs stay off." If the recognition is wrong, a board can still be chosen by hand. The chip name alone is enough, so a board version AxeOS added later (a Supra Hex 703) is caught as well and shown as "Bitaxe (BM1368)". TinyChipHub's Zyber boards (Zyber8S, 8G, 8G+, 12G), which run an AxeOS fork and look like a Supra Hex on the bus, are named and stopped the same way, by the model their factory settings store.
    • The installer page checks the board first. Before the backup and before anything is written, the browser installer reads the same AxeOS settings from the miner. On one of these boards it stops with "This miner is a Bitaxe Supra Hex (6× BM1368), which WarpAxe cannot run. Nothing was written; its firmware stays as it was." and restarts the miner into its own firmware. A miner without such settings installs as before. If reading the flash fails, the install stops before anything is written.

    What is fixed.

    • A pool that accepts the connection and then says nothing no longer holds the miner. Until now such a pool (a proxy whose backend is gone, or the IPv6 side of a pool that only works over IPv4) kept each attempt for three minutes, three times before the fallback took over. Until the first job arrives, a connection now ends after 30 seconds without data from the pool; once work arrives, quiet periods of up to three minutes are fine as before.
    • IPv4 first after a silent IPv6 connection. A pool that sent no work over IPv6 is tried over IPv4 first for the next hour, with IPv6 still in the race behind it in case IPv4 does not answer. Changing the pool settings resets this.
    • The fallback is kept while the main pool sends no work. While the miner is on the fallback, a main pool that accepts the connection but sends no work no longer pulls it away every five minutes. It gets one try (a second one at once over IPv4 if IPv6 stayed silent), then the miner goes back to the fallback and waits twice as long before the next check: 10, 20, then 40 minutes. Work from the main pool sets the wait back to five minutes.
    • A readable timeout in the log. When a pool goes quiet, the log now says "no data from the pool for 30 s" (or 180 s) instead of "No more processes (os error 11)".

    For developers.

    • Smaller formatting code. The firmware now formats text through newlib's nano printf (CONFIG_NEWLIB_NANO_FORMAT), 44.8 KB less flash; the stacks that ESP-IDF and the Wi-Fi library shrink with that option are kept at their old sizes. A few ESP-IDF and Wi-Fi log lines with 64-bit or size_t values (%llu, %zu) now print letters such as lu instead of the number; floating-point numbers still print. WarpAxe's own log lines and every value in the API are unaffected. The list is in docs/16.
    • Installer: ?backuponly (backup only, nothing written) now says so when it finishes, and the browser console logs the board check with what it read.

    Image. About 34 KB smaller than v0.1.46 (34,368 bytes): 44.8 KB less for nano printf; the board recognition, the clock per chip and the silent-pool handling take about 10 KB of that back.

    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).

    Source: git.warppool.org/dvb-projekt/dvb-WarpAxe · Mirror: github.com/dvb-projekt/dvb-WarpAxe

    Downloads