• v0.1.13 b0fe512dd3

    WarpAxe v0.1.13
    All checks were successful
    CI / Rust checks (push) Successful in 44s
    CI / Regulator scenarios (push) Successful in 46s
    Stable

    dvb-projekt released this 2026-10-01 12:06:37 +00:00 | 294 commits to main since this release

    No more lost chip replies. When WarpAxe read several chip registers in a row — the once-a-second hash-counter round, eight registers per chip — the replies came back faster than the receive buffer was drained, and some were cut off. That is where the empty domains came from, and a cut-off burst could also take a nonce with it, more likely on boards with many chips such as the NerdOctaxe. The reads now go out one per pass and the receive buffer is 16 times larger. On a NerdAxe Gaia: 0 dropped bytes, CRC failures and desyncs, and a 64-register scan answered in full (before: about half). Recommended for every board.

    The BM1373 has eight hash domains. Solo Satoshi describes the BM1373 as eight hashing domains; no firmware read them. AxeOS reads four domain counters and doubles them. A register scan on our Gaia found the other four at 0xAC–0xAF, each counting an eighth of the total. WarpAxe now reads all eight; hashrateMonitor lists eight domains for a BM1373 (four for the BM1370), and the dashboard card shows them in two rows of four.

    Naja Duo: overclock up to 600 MHz. The preset list stays AxeOS's (327–410 MHz); with ?oc free values now go up to 600 MHz, the maker's documented overclock (600 MHz / 1120 mV, about 8 TH/s and 92 W). Untested by us — the Naja Duo has not run WarpAxe here.

    Your miner's name in the browser tab. "NerdAxe Gaia · WarpAxe" instead of "WarpAxe", with the hostname in brackets where it differs ("Bitaxe Gamma (bitaxe602) · WarpAxe"), so several open tabs tell their miners apart.

    Also in this release:

    • For diagnosis, read-only: GET /api/v1/chip/regs?chip=0&from=0x80&to=0xbf reads a range of chip registers, GET /api/v1/chip/cores counts the nonces per core.
    • Measured on the Gaia (BM1373) at 380 MHz: the one-minute error rate is 16.9 % at 930 mV, 6.1 % at 950 mV and 2.5 % at 970 mV, while the chip's own hash counter stays the same — real timing errors that fall steeply with voltage, so the error rate is a usable voltage signal on this chip too.

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

    Downloads