dvb-projekt/dvb-WarpPool
dvb-projekt/dvb-WarpPool
1
0
Fork 0
Code Issues Pull requests Projects Releases 45 Packages 1 Wiki Activity Actions
45 releases 94 tags
  • v1.39.1 1fc4c2d65d

    v1.39.1
    All checks were successful
    CI / Rust clippy (push) Successful in 2m6s
    Details
    CI / Rust fmt (push) Successful in 1m14s
    Details
    CI / Rust test (push) Successful in 7m17s
    Details
    CI / UI (SvelteKit) (push) Successful in 1m19s
    Details
    CI / Security Audit (push) Successful in 1m19s
    Details
    docs / build (push) Successful in 34s
    Details
    Release / Docker Multi-Arch (push) Successful in 27m43s
    Details
    Release / Binary aarch64-unknown-linux-gnu (push) Successful in 12m55s
    Details
    Release / Binary x86_64-unknown-linux-gnu (push) Successful in 12m10s
    Details
    Release / Linux .deb + .rpm (amd64) (push) Successful in 2m10s
    Details
    Release / Linux .deb + .rpm (arm64) (push) Successful in 2m0s
    Details
    Release / Linux AppImage (aarch64) (push) Successful in 24s
    Details
    Release / Linux AppImage (x86_64) (push) Successful in 26s
    Details
    Release / Cosign sign artifacts (push) Successful in 27s
    Details
    Release / Forgejo Release (push) Successful in 35s
    Details
    Stable

    dvb-projekt released this 2026-10-11 10:22:56 +00:00 | 5 commits to main since this release

    Added

    • WarpTune: built-in core-current lines per board when neither the
      firmware nor warptune.toml names one. Stock ESP-Miner and NerdOS report
      no coreCurrentWarnA, so the core current on them ran unchecked. A table
      from the reference firmwares (ESP-Miner device_config.h / TPS546.c,
      NerdOS board classes via WarpAxe's profiles) now supplies the warn and
      fault lines and the board's power limit — Bitaxe Gamma, Gamma Duo, Supra
      and Ultra (TPS546 revisions), Hex, Supra Hex, Gamma Turbo, Naja Duo, Gamma
      Hex, BitForge Nano, NerdAxe Gamma, NerdAxe Gaia, NerdQAxe++, NerdOctaxe-γ,
      Q1370, Q1373. On those boards the firmware's current is the regulator's
      output and serves as the core current. Every line from the table is marked
      "board default" in decisions, the journal and on the card; the config's
      line beats it and the firmware's fault line beats everything. Nothing
      raises a line the firmware or the config reports.
    • Devices: the WarpTune card shows the core current against its line
      (tooltip) and says so when it sits at or over the share a step up may use
      ("near the warn line"). A Bitaxe GT at 44.8 A under a 50 A warning was
      formally fine and worth a word.
    • Devices: the card says when the hand point draws more than the board
      limit or max_watts       allows, and the sidecar warns at start.
    • WarpTune: per-miner board_limit_w replaces the board power limit the
      firmware reports (and the table's) where that figure is not the board's —
      a NerdQAxe++ on WarpAxe still reports NerdOS's 100 W and runs 110 W on a
      124 W supply; without the key every restore would be held under 100 W.
    • Release: WarpTune on its own — every release now carries
      dvb-warppool-tune-<tag>-<target>.tar.gz for Linux (x86_64, aarch64) and
      macOS (Apple silicon, Intel) with just the tuner binary, its guide and the
      licence, for running WarpTune next to a pool on Umbrel or Docker. Until now
      the binary was only inside the full pool packages.

    Changed

    • WarpTune: a restore never goes above the power limit. The restore
      target (after a reboot, on shutdown, after a trip or a latch) was held
      under the core current bar only; a Bitaxe GT whose hand point 850 MHz @
      1221 mV drew 64.5 W on a 60 W board got it written back after every reboot
      and was pulled down "urgent" afterwards. The target is now held under the
      lower of max_watts and the board limit as well, on the hand point's
      measured watts (the journal's windows, kept across restarts) or, without a
      measurement there, scaled f·V² from the last running sample: the highest
      ladder step under the limit at or under the hand voltage, with the reason
      in the decision and the journal. With no power data at all the restore
      goes as before and the decision says it went unchecked. The hand point
      itself stays the reference of the savings tile.
    • Devices: the WarpTune vs. hand points tile leaves work-mode miners (the
      Avalon Q) out altogether — not in the sums, the percentages or the miner
      count; their kilowatt and their Super mode would make the tile theirs. The
      tile names them ("Without … (work modes): its figures are on its own
      card."). When every Max point runs at its hand clock, Max adds no hashrate
      by construction, so the "Max adds" figure shows the watts saved instead
      ("less power at the same hashrate (N miners at their hand clock)").

    dvb-WarpPool v1.39.1 — Downloads

    Docker

    git.warppool.org/dvb-projekt/dvb-warppool:v1.39.1 (multi-arch amd64+arm64, ohne v-Präfix)

    Native packages

    • Linux .deb: amd64 + arm64 → apt install ./dvb-warppool_*.deb
    • Linux .rpm: amd64 + arm64 → dnf install ./dvb-warppool-*.rpm
    • Linux AppImage: x86_64 + aarch64 portable
    • Linux tarballs: x86_64 + aarch64 for manual installs
    • WarpTune only: dvb-warppool-tune-<tag>-<target>.tar.gz (Linux x86_64 + aarch64; macOS added with the .dmg) for running the tuner next to a pool on Umbrel or Docker — see the README inside
    • macOS .dmg: added shortly after publish (built separately) — or build from source
    • Windows .msi: paused since the forge migration (no Windows runner yet)

    Signatures

    • SHA256SUMS + cosign bundle (SHA256SUMS.bundle, project key)
    • SBOM (SPDX) for all dependencies

    Verify (project public key cosign.pub in the repo root):

    cosign verify-blob \
  --key cosign.pub \
  --bundle SHA256SUMS.bundle \
  SHA256SUMS
sha256sum --check SHA256SUMS

    First-time setup: run dvb-warppool-setup for the first-run wizard.

    Downloads