-
WarpAxe v0.1.42
Stablereleased this
2026-11-11 08:34:56 +00:00 | 129 commits to main since this releaseASICs off while no pool answers, a lower voltage waits for the clock, and a found block shows its status. A healthy miner mines as before. When neither the main pool nor the fallback answers, WarpAxe now switches its ASICs off and switches them back on with the first job. A lower core voltage now waits until the clock has come down. A found block keeps its hash and shows whether the chain built on it. The Bitaxe Naja Duo and Gamma Turbo now read both chips' temperatures. A hash domain that is dead right after the chain starts is healed after about three minutes.
What is new.
- ASICs off while no pool answers. Until now a miner without a pool hashed for nothing at full power. When the main pool and the fallback pool (where one is set) have both failed, with at least two attempts on each and at least 60 seconds since the first failure, the core voltage goes off, the ASICs are held in reset and the fans go to their lowest duty. A short Wi-Fi or pool blip switches nothing. Both pools are then probed in turn every 30 seconds, and the first job from either brings the ASICs back with the same clock and voltage. The same applies when no pool or no worker is set up. API:
poolsUnavailable(the name AxeOS and ForgeOS use),chainStopped,chainPhaseNOPOOL; the dashboard shows a notice, the display shows "NO POOL", and the event log has one entry for going off and one for coming back. Nothing is written to flash per attempt. This does not apply while a self-test runs or during the first start of a newly chosen board. Tested on a Bitaxe Gamma: with both pools gone the ASICs went off after about 110 seconds and the miner drew 5 W; when a pool came back, it was mining again on its own within about 10 seconds. The README comparison table now lists this row as "yes" for WarpAxe, next to AxeOS and ForgeOS. - Changed pool behaviour. A pool session that never sends a job now counts as a failed attempt, however long it stays open; this also counts toward the switch to the fallback. After two failures on the fallback, the miner now tries both pools in turn instead of staying on the fallback.
- A lower voltage waits for the clock. A
PATCH /api/systemwith a lower clock and a lower core voltage used to set the voltage within a tenth of a second while the clock came down in steps (625 to 425 MHz takes 3.2 s), so the chips ran at the old clock on the new voltage for those seconds. The voltage drop now waits until the chips run at the new clock (30 s at most). A higher voltage is set at once, as before. The API now refuses a clock below 50 MHz and one the PLL has no setting for; a stored clock of that kind is replaced by the board's default at boot. Seen on a NerdAxe Gaia going from 380 MHz / 960 mV to 350 MHz / 950 mV: the voltage stayed up (955 mV read) until the chips were at 350 MHz, then went down, as the log lines show. WarpTune v1.48.0 already sends the clock first and the voltage after it. - Found-block status. A found block is now stored with its hash. Its status is
pendingat the find,confirmedonce the pool's next work builds on it,orphanedwhen the work for the next height builds on another block, andunknownwhen the miner was offline or without a pool for more than one block. The banner shows the status and the shortened hash, for Bitcoin with a mempool.space link, and shows again when the status changes; the event log has an entry for each status. API:lastBlock.hash,lastBlock.status(null for a block found before v0.1.42). The find itself is now checked against the exact target of the block header. The block count is kept in the form older versions read, with hash and status in a second record, so a downgrade keeps the count. On a test chain at minimum difficulty, where every nonce meets the target, a block is stored once instead of hundreds of times a second. Not tested live, since that needs a found block; covered by unit tests with real block headers. - Both chips' temperatures on the Naja Duo and the Gamma Turbo. These boards have a diode per chip on the EMC2103, and only the first was read, so the second chip had neither a fan control nor an overheat stop. Fans and the overheat stop now follow the hotter chip, as ESP-Miner does. API:
tempis the hotter chip,temp2the second chip's own (-1 without a reading, as on AxeOS),asicTempsboth. A diode that read before and fails counts as unknown, never as cool: fans at full and the lost-sensor stop after a minute. A diode that never reads after boot sets the fans to 100 % after a minute and shows a notice; the chips keep running. We have not run this on such a board yet. If you have a Gamma Turbo, please send ustemp2andasicTempsfrom/api/system/info. - Faster heal for a domain that is dead from the start. v0.1.41 heals a hash domain that stays under 25 % of its sibling domains for ten minutes. A domain under 5 % of its siblings in the chain's first window is now healed after about three minutes. A domain between 5 and 25 %, or one that dies later, still has the ten minutes. The other rules stay: at most one intervention an hour, given up after three resets that do not hold. On a user's Bitaxe Gamma the ten-minute heal of v0.1.41 has worked twice: a domain at 0 % right after an update was healed, and all four domains were fine after. In both cases the clock was well above stock. The three-minute case is tested in the chip simulator.
- Self-test without pool work. Without work from a pool the self-test now marks the hash checks (hashrate, domains, error rate) as skipped with the note "no work from the pool", not failed, and checks the rest: chip count, voltages, regulator, fan, temperatures. The self-test may switch the ASICs on while no pool answers, so a bench test works before a pool is set up.
- The board in the Stratum V1 user agent.
mining.subscribenow sendswarpaxe/0.1.42 (nerdaxe-gaia): the board's profile name in brackets, the same name a Stratum V2 connection already sends, so a pool can tell your boards apart. Until a board is settled (first start not yet confirmed) the agent stayswarpaxe/0.1.42. A pool that sorts miners by user agent may now place a WarpAxe board in its Bitaxe or NerdNOS class. - Diagnostics file. A worker's bare address is now masked too; it showed in the coinbase outputs. A numeric pool password such as "1000" no longer drops the whole info section.
- Fixed during testing. With the ASICs off on purpose (no pool, or switched off by hand), a temperature diode that gives no reading no longer trips the overheat stop. After a real overheat stop the miner restarts once the regulator has cooled and a minute has passed, as AxeOS does.
- Web interface.
- The footer under the swarm list now says what your browser asks for and what your WarpAxe reads itself (an Avalon over the cgminer API, port 4028), and that only addresses are stored.
- A device found in the network search counts as a miner only when it reports a numeric
hashRate. - "Chips off" now reads "ASICs off" wherever the hash chips as a group are meant; the rest of the board keeps running.
- Event log entries added since v0.1.40 are now translated in all languages; they showed in English before.
- WarpTune. WarpTune v1.48.0 reads
poolsUnavailableand neither heals nor steps down while no pool answers.
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
- ASICs off while no pool answers. Until now a miner without a pool hashed for nothing at full power. When the main pool and the fallback pool (where one is set) have both failed, with at least two attempts on each and at least 60 seconds since the first failure, the core voltage goes off, the ASICs are held in reset and the fans go to their lowest duty. A short Wi-Fi or pool blip switches nothing. Both pools are then probed in turn every 30 seconds, and the first job from either brings the ASICs back with the same clock and voltage. The same applies when no pool or no worker is set up. API: